Leadership Framework for Building Elite Teams
Four Reasons Why You Need a Third-Party Security Assessment
Information Security Against Cyber Attacks
The Technology Project Life Cycle: Lessons Learned
Implementing a Cybersecurity Program - The Journey of True...
Maurice Edwards, Senior Vice-President Enterprise Risk, Mattress Firm
Information Governance = Data Governance + Disclosure
Tera Ladner, Director, Information Governance, Aflac
For DDoS-Hope is NOT a Strategy!
Jon Murphy, GVP-IT Security, Ocwen Financial Corporation
Do You Suffer from Cloud Strategy Deficiency (CSD)?
Hiba S. Sharief, Vice President, IT, Oportun
Thank you for Subscribing to CIO Applications Weekly Brief
Key Cloud-Native Security Challenges to Know
Microservices are used by DevOps and infrastructure teams to run cloud-native applications.
FREMONT, CA: Organizations all over the world are rapidly adopting cloud-native applications built on new types of infrastructure like containers and serverless platforms. While cloud-native applications provide benefits such as elastic scalability, unparalleled resilience, as well as rapid development velocity, they also introduce new challenges.
Cloud-native applications have a lot of moving parts and rely on fleeting infrastructure elements that are here one minute and gone the next. This creates operational and maintenance issues, but most importantly, it raises security concerns. Cloud-native security necessitates the development of new approaches, strategies, and tools. In this article, we are jotting down a few tips for improving security for an organization's cloud-native portfolio.
Cloud-Native Security Challenges
Multiple Entities to Secure
Microservices are used by DevOps and infrastructure teams to run cloud-native applications. Previously, multiple processes or software functions would run on a single virtual machine. Each processor capability is now packaged as its own container or serverless function. Each entity is susceptible to compromise and must be safeguarded throughout the development lifecycle.
Various Architecture Patterns
Cloud-native systems can include both public and private clouds, as well as cloud services and application architectures. Each architectural pattern may have unique vulnerabilities and security needs. Security teams must comprehend this complex attack surface and devise solutions for securing each architecture.
Environments in Flux
The public and private cloud environments are always changing. Because of the rapid software release cycles, every component of a microservices application may be updated on a daily basis. Furthermore, the adoption of practices such as immutability and infrastructure as code (IaC) means that applications are constantly being disassembled and rebuilt. It can be difficult for security teams to secure these deployments without slowing down the release cycle.