Skip to content

Cloud Native Security

What is Cloud Native Security?

Security practices and tools designed specifically for cloud-native architectures including containers, microservices, and serverless computing. Cloud native security shifts protection closer to the workload and incorporates security into the CI/CD pipeline.

Cloud

Each of these is named in at least one of the same controls as cloud native security. The number is how many controls name both.

What the standards actually require on cloud native security

Requirements naming cloud native security across 5 standards, quoted from the control text.

Apply cloud-native security principles: defense in depth, least privilege, zero trust, immutability, and secure-by-default across the 4C layers and lifecycle.

CNCF-SA-PRINCIPLES · Security Principles

HKMA C-RAF Domain 3 PROTECTION + Domain 4 DETECTION. DOMAIN 3 PROTECTION (6 sub-areas): (1) ACCESS CONTROL - identity + access management + privileged access (PAM) + MFA + zero trust + just-in-time access + role-based access + access reviews + offboarding;

HKMA-CRAF-Domain3-4-Protection-Detection · HKMA C-RAF Domain 3 (Protection) + Domain 4 (Detection) - Access, Data, Infrastructure, Application, Monitoring, Testing, Threat Intel
HKMA TM-G-11 control

HKMA TM-G-1 IT Strategy + Policies + Risk + Development + Change. (1) IT STRATEGY AND PLANNING (TM-G-1.3.1) - documented + Board-approved IT strategy aligned with business strategy + risk appetite + technology innovation + customer experience + investment plan...

HKMA-TMG1-Strategy-Policies-RiskAssessment-Dev-Change · TM-G-1 IT Strategy + Policies + Risk Assessment + Project Management + System Development + Change Management
ISMAP (Japan)1 control

ISMAP Cloud Infrastructure controls cover the underlying compute + network + storage + management plane. (1) Virtual Network Segmentation: VPC Virtual Private Cloud isolation + subnets + security groups + NACLs + microsegmentation + service mesh (Istio + Linke...

ISMAP-CloudInfrastructure-NetworkSegmentation-Container-Serverless-WorkloadProtection-Hardening-ConfigManagement · ISMAP Cloud Infrastructure - VPC Network Segmentation + Container/Serverless Security + Cloud Workload Protection (CWPP) + Image/Template Hardening + CIS Benchmarks + Configuration Management + IaC

Implement Acquisition Development Maintenance + Supplier Relationships + Vulnerability Management per MTCS SS 584. Acquisition Development and Maintenance (ISO 27001 Annex A.14) - secure coding standards (OWASP Top 10 + OWASP ASVS + CWE Top 25 + CERT Secure Co...

MTCS-Acquisition-Development-Maintenance-Supplier-Vulnerability-DevSecOps-SBOM-SDLC-SCA-API-Container · MTCS Acquisition + Development + Maintenance + Supplier + Vulnerability + DevSecOps + SBOM + SDLC + SCA

Questions people ask about cloud native security

What is Cloud Native Security?
Security practices and tools designed specifically for cloud-native architectures including containers, microservices, and serverless computing. Cloud native security shifts protection closer to the workload and incorporates security into the CI/CD pipeline.
Why is Cloud Native Security important for compliance?
Cloud Native Security is a key concept in Cloud. Understanding cloud native security helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 686 frameworks with 311K cross-framework control mappings.
Which compliance frameworks address Cloud Native Security?
Cloud Native Security appears in the requirement text of CNCF Security Technical Advisory Group (TAG), HKMA Cyber Resilience Assessment Framework (C-RAF), HKMA TM-G-1, ISMAP (Japan), MTCS (Singapore). Across these standards we have identified 7 controls that name it directly, each linked to the control text on the compliance platform.
Where can I learn more about Cloud Native Security?
Explore our compliance framework pages to see how cloud native security applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 686 frameworks.

See how Cloud Native Security applies across compliance frameworks

Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.