A CNAPP (Cloud-Native Application Protection Platform) is a unified security suite that consolidates CSPM, CWPP, CIEM, KSPM, DSPM, ASPM, and CDR into a single integrated platform, covering cloud-native applications from code commit through production runtime. Coined by Gartner in the 2021 Hype Cycle for Cloud Security, the term captures a deliberate shift away from point-tool sprawl toward a cohesive risk engine that connects posture, identity, workload, data, and runtime signals into one prioritized view. The critical insight driving adoption is that cloud breaches rarely stem from a single finding — they emerge from toxic combinations: a misconfigured storage bucket combined with an over-permissioned IAM role combined with an internet-exposed workload, each individually medium-risk but collectively critical. CNAPP platforms address this by modeling every cloud resource and relationship in a security graph, surfacing the attack paths that matter rather than the theoretical noise that doesn't.
What This Cheat Sheet Covers
This topic spans 17 focused tables and 142 indexed concepts, 126 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: CNAPP Architecture and Core Components
Every CNAPP is built on the convergence of several formerly standalone cloud security disciplines into a single data model and policy engine. Understanding what each pillar does — and how they reinforce each other — is the foundation for evaluating and operating any CNAPP product.
| Concept | Example | Description | |
|---|---|---|---|
S3 bucket has PublicAccessBlock disabled → flagged critical | Continuously monitors cloud resource configurations via provider APIs (AWS Config, Azure Resource Graph, GCP Cloud Asset Inventory), identifying misconfigurations against benchmarks such as CIS, NIST, PCI DSS, and SOC 2. | ||
Falco rule fires when execve is called inside a running container | Provides vulnerability scanning, malware detection, and behavioral runtime monitoring for VMs, containers, and serverless functions, using agents or agentless snapshot scanning. | ||
IAM role with AdministratorAccess has not been used in 90 days | Discovers and governs human and machine identity permissions across cloud environments, enforcing least-privilege by revoking stale or excessive entitlements. | ||
kube-bench CIS check: API server flag --anonymous-auth=true | Automates security assessment of Kubernetes cluster configurations, RBAC policies, network policies, and pod security settings against CIS Benchmarks and custom policies. | ||
S3 bucket tagged env:prod contains unencrypted PHI records | Discovers, classifies, and monitors sensitive data (PII, PHI, PCI) across multi-cloud storage, building exposure graphs that show who can reach what data through which configuration path. | ||
CloudTrail shows IMDS probe → then credentialed S3 ListBuckets → then bulk export | Monitors control-plane logs (CloudTrail, Azure Activity, GCP Audit), VPC flow logs, and workload eBPF telemetry in real time to detect active attacks including lateral movement and data exfiltration. | ||
SAST finding severity up-scored after runtime confirms code path is reachable | Aggregates and correlates findings from SAST, DAST, and SCA tools into a unified application-layer risk view, prioritizing by business impact and runtime exploitability. | ||
Amazon Bedrock model endpoint exposed publicly; service account has s3:* on training bucket | Discovers and secures AI models, pipelines, and datasets by detecting misconfigured endpoints, over-permissioned AI service accounts, exposed model weights, and supply chain risks in public model repos. | ||
Node: EC2 instance → Edge: "has public IP" → Edge: "assumes IAM role with AdministratorAccess" | Graph database that models every cloud resource as a node and every configuration relationship as an edge, enabling attack path traversal to identify exploitable chains across isolated findings. | ||
Terraform plan shows S3 bucket with acl = "public-read" blocked at CI PR stage | Scans Terraform, CloudFormation, ARM, Helm, and Kubernetes YAML templates for misconfigurations and policy violations before infrastructure is provisioned (shift-left). |