Cloud Native Security
Cloud native security protects containerized applications and their orchestration infrastructure. It addresses image supply chain integrity, runtime isolation, network segmentation, secrets management, and policy enforcement across dynamic, ephemeral workloads.
itCloud native tools and technologies | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don’t Panic — Cloud Native Security
Cloud native security is the habit of protecting software while it moves from source code to a running workload, which is less a castle wall and more a busy railway junction. Containers start, stop, and acquire new neighbours. Releases arrive by automated pipeline. A fixed network edge still helps, but it cannot be asked to recognise every artifact, workload, and action. That is not a criticism of walls. Walls have had a difficult century.
The useful map has four stops: develop, distribute, deploy, and runtime. In develop, protect source, dependencies, and build identities. In distribute, preserve evidence about the artifact: its digest, signature, provenance, and scan result. In deploy, use admission policy, a rule checked before a workload enters an environment, to decide whether that evidence and configuration are acceptable. In runtime, protect access, compute, storage, networks, and the records needed to investigate. Each handoff needs evidence because a useful control cannot telepathically report what happened before it arrived.
The surprise is that evidence is not a verdict. A signature binds an identity to data. A provenance statement describes origin and build process. A scan reports what it noticed at one time. None of them proves safe code, safe permissions, or safe behaviour forever. Workload identity, an authenticated identity for running software, matters because a changing network address is not a durable answer to who is asking. Network controls still reduce reachable paths; they merely do not become an identity card by wearing a lanyard.
Begin with one important service. Map its data, dependencies, identities, and trust boundaries. Trace its journey through the four stages. Then name the owner and evidence for each control, and test the less glamorous actions: revoking a credential, isolating a workload, preserving evidence, and recovering. The Intro supplies the full map and glossary. Slides compress the relationships. Cheatsheet is the decision reference. Field Notes focuses on where the operating costs hide. The quiz checks the distinctions that security tools cheerfully blur.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://tag-security.cncf.io/community/resources/security-whitepaper/v2/cloud-native-security-whitepaper/
Supports
- Cloud native security across develop, distribute, deploy, and runtime stages
- Cloud native layers and the dependence between lifecycle controls and runtime foundations
- Security automation close to dynamic workloads and throughout delivery
- Cross-functional ownership among development, operations, and security roles
- https://kubernetes.io/docs/concepts/security/cloud-native-security/
Supports
- Develop, distribute, deploy, and runtime control examples
- Runtime protection across access, compute, storage, networking, and observability
- Deployment restrictions, artifact verification, workload privilege, and isolation choices
- Detection, trustworthy telemetry, and infrastructure protections below orchestration
- https://kubernetes.io/docs/concepts/security/security-checklist/
Supports
- Baseline review areas for authentication, authorization, network policy, pod security, secrets, images, and audit
- Checklists as a starting point rather than sufficient proof of security
- https://csrc.nist.gov/pubs/sp/800/190/final
Supports
- Containers as operating-system virtualization combined with application packaging
- Container risk areas across images, registries, orchestrators, containers, and hosts
- Recommendations for image, registry, orchestrator, runtime, and host security
- The shared host operating-system kernel as part of the container security boundary
- https://slsa.dev/spec/v1.2/
Supports
- SLSA version 1.2 tracks, levels, requirements, and attestation formats
- Increasing supply-chain guarantees and artifact provenance
- Producer and consumer uses of verifiable supply-chain evidence
- https://slsa.dev/spec/v1.2/about
Supports
- SLSA limits regarding code quality, malicious producers, and transitive dependency trust
- Tradeoffs between stronger guarantees and implementation cost
- https://spiffe.io/docs/latest/spiffe-about/overview/
Supports
- Workload identity for dynamic and heterogeneous environments
- Short-lived cryptographic identity documents and automatic rotation
- Limits of static network identifiers for workload authentication
- https://kubernetes.io/blog/2015/07/kubernetes-1-0-released/
Supports
- Kubernetes 1.0 release in July 2015 and the start of its production-oriented project history
- https://www.cncf.io/projects/kubernetes/
Supports
- Kubernetes acceptance into CNCF in 2016 and graduation in 2018
- https://csrc.nist.gov/pubs/sp/800/190/final
Supports
- NIST SP 800-190 publication in 2017 and its container security guidance
- https://spiffe.io/blog/2020/05/14/spiffe-spire-v1.0/
Supports
- SPIFFE and SPIRE 1.0 milestone for workload identity
- https://slsa.dev/blog/2021/06/introducing-slsa/
Supports
- SLSA introduction in 2021 as a framework for software supply-chain integrity
- https://kubernetes.io/blog/2022/08/25/pod-security-admission-stable/
Supports
- Pod Security Admission reaching stable status in Kubernetes 1.25
- https://www.wiz.io/
Supports
- Wiz as a commercial cloud security platform used for cloud and Kubernetes posture and workload visibility
- https://www.paloaltonetworks.com/prisma/cloud
Supports
- Prisma Cloud as a commercial cloud native application protection platform
- https://www.aquasec.com/
Supports
- Aqua Security commercial cloud native security platform
- https://sysdig.com/
Supports
- Sysdig commercial cloud and runtime security platform
- https://www.chainguard.dev/
Supports
- Chainguard commercial software supply-chain and container-image offering
- https://snyk.io/product/container/
Supports
- Snyk Container as a commercial container image security product
