What is CNAPP? Components, agents and when you need one

What is a CNAPP: the platform that joins CSPM, CWPP, CIEM and DSPM for cloud security. Components, agents or API, how it differs from a SIEM, when you need one.

10 min read
What is CNAPP? Components, agents and when you need one

Key takeaways

  • A CNAPP (cloud-native application protection platform) brings the cloud security controls into one product: configuration posture (CSPM), workloads (CWPP), permissions (CIEM), data (DSPM), Kubernetes (KSPM), code and runtime detection (CDR).
  • The value is not the sum of the modules but the single data model: a graph that links exposure, vulnerabilities, permissions and data, and derives the attack paths that can actually be exploited.
  • Inventory is read via API with read permissions; disks are analysed from temporary snapshots. No agents, but not all read-only. A runtime sensor is added only where it is needed.
  • It does not replace a SIEM or a SOC: the CNAPP works on cloud posture, the SIEM correlates everything else, the SOC investigates and responds. Someone still has to clear the queue of fixes.
  • It earns its place with real workloads on IaaS or PaaS, several accounts or clouds, Kubernetes or frequent releases. It produces evidence for NIS2 Article 21(2) and for the asset mapping in DORA Article 8(4).

The short answer: a CNAPP (cloud-native application protection platform) is a single platform that brings together the cloud security controls that used to be bought separately: configuration posture (CSPM), workload security (CWPP), permissions (CIEM), data (DSPM), Kubernetes, code and runtime threat detection. Its value is not the sum of the modules but the context that links them: it shows which risks are actually exploitable, and in what order to fix them.

This guide covers where the category comes from, what each component does, how a CNAPP connects to your cloud, what it does not do, and when it makes sense for a mid-market organisation.

Where does the term CNAPP come from?

According to Wiz, the term was coined by Gartner, the analyst firm, to name a convergence the market was already going through. In the Gartner definition that Wiz reports in its Academy, a CNAPP is a unified and tightly integrated set of security and compliance capabilities for securing cloud-native applications from development through to production (our paraphrase).

Two ideas carry the weight. Integrated: not a suite of products under one logo, but one data model that every control works on. From development to production: the same platform looks at code and templates before release, and at the resources that actually run afterwards.

There is no official list of modules, and each vendor draws the category in its own way. Microsoft, for example, describes Defender for Cloud in its documentation as a CNAPP with three core components: CSPM, DevSecOps and CWPP. Wiz also lists CIEM, KSPM, DSPM, code security and CDR. When you compare two offers, compare capabilities, not acronyms.

What problem does a CNAPP address?

The cloud changed who creates infrastructure. A server used to be bought, installed and added to an inventory. Today a developer can open a storage bucket, a serverless function or a Kubernetes cluster in minutes, and the security of that resource depends on how a template was filled in.

The shared responsibility model sets out who looks after what. The provider covers the underlying infrastructure and physical facilities; the customer keeps configurations, identities and data, with a split that shifts between IaaS, PaaS and SaaS. Google Cloud's Architecture Framework, in its page on this model, puts it plainly: many cloud security breaches are the direct result of misconfiguration.

For years the answer was one tool per problem: a vulnerability scanner, a configuration checker, a permissions tool, a container scanner. Each produces its own list, and none sees the whole picture. The scanner knows a machine has a known vulnerability, but not that the machine is exposed to the internet and runs under a role that can read the customer database. Taken one by one, these are three medium-severity findings. Together, they are an open road to your data.

A CNAPP exists to make that connection. It is the same problem as alert overload in a SOC, moved to cloud posture: too many findings without context, and the real risk buried among them. For how the same logic applies to vulnerability scanning across the rest of the estate, see our guide to vulnerability management tools.

What are the components of a CNAPP?

The acronyms are many and they overlap. Here is what each piece does, in plain terms.

CSPM: configuration posture

Cloud security posture management compares the configuration of every resource against a set of rules: public storage, ports open to the internet, logging switched off, missing encryption, accounts without multi-factor authentication. The rules come from provider recommendations and public standards such as the CIS Benchmarks, and the results map onto compliance frameworks. This is where the category started.

CWPP: workloads

The cloud workload protection platform looks inside what runs: virtual machines, containers, serverless functions. It searches installed packages for vulnerabilities, malware, secrets left on disk (keys, tokens, passwords) and weak operating system settings. It can work without agents, by analysing disks from the outside, or with a lightweight sensor that sees what happens in real time.

CIEM: identities and permissions

Cloud infrastructure entitlement management deals with who can do what. In the cloud, identities are not only people: they are service accounts, roles attached to machines, application access keys. CIEM calculates the effective permissions of each identity, finds those granted and never used, and helps apply least privilege.

DSPM: data

Data security posture management finds where sensitive data lives (buckets, volumes, managed and self-hosted databases) and cross-references it with everything else. A database holding personal data is a different problem if it is reachable from the internet or if an over-broad role can read it. For organisations accountable under the GDPR, this is the part that links the record of processing activities to what is actually in the cloud.

KSPM: Kubernetes

Kubernetes security posture management applies the same reasoning to clusters: configuration, permissions, secrets, network exposure, container and host vulnerabilities. It matters if you run Kubernetes, managed or not. If you do not, it is a module you can ignore.

Code and infrastructure as code security

Here the CNAPP moves upstream, into the development pipeline. It analyses infrastructure as code templates (Terraform, CloudFormation, Kubernetes manifests), source code and pipelines before release, so that a bad configuration is stopped in the pull request instead of being found in production. The jargon for this is shift left.

CDR: cloud detection and response

Cloud detection and response looks at what is happening now: cloud activity, audit logs and runtime signals from workloads. It looks for behaviour such as privilege escalation, lateral movement, cryptomining, container escape and remote code execution. This is where the CNAPP meets the work of the SOC.

One more direction is emerging. According to the Wiz Academy, CNAPPs are absorbing AI security posture management (AI-SPM), so that training data, model endpoints, permissions and AI service configurations become part of the same workflow. Microsoft's documentation for Defender for Cloud also lists AI security posture management among its capabilities. It is the same logic applied to a new surface.

What makes a CNAPP more than a bundle of tools?

If a CNAPP were only seven modules in one console, it would be a commercial bundle. The difference lies in the data model underneath.

  • One inventory. Every resource in every account and every cloud in one place, updated continuously. Everything else builds on it.
  • A graph of relationships. Each resource is a node, each relationship a link: this machine uses this role, this role reads this bucket, this bucket holds personal data. On a graph you can ask questions a list cannot answer.
  • Attack paths. The graph surfaces the combination that matters: internet exposure, plus an exploitable vulnerability, plus a permission that leads to data. This is what turns thousands of findings into a handful of priorities.
  • One queue. Risks arrive already ranked by impact, with the resource, its owner and the fix, instead of five lists to reconcile by hand.

Does a CNAPP need agents?

It depends on what you want it to do. It is worth being precise, because it is one of the first questions from whoever runs the cloud accounts.

  • Inventory and configuration via API. The platform connects to the cloud with a dedicated role holding read permissions, and reads resources, configurations, network settings and permissions from the provider's APIs. No software on the machines.
  • Disk analysis from snapshots. To look inside workloads (packages, vulnerabilities, secrets), the agentless approach creates temporary, encrypted snapshots of disks and analyses them in a separate, isolated environment, away from production. That means it also needs permissions to create and delete those snapshots: it is not all read-only, and it is better to know that before you talk to your cloud administrators.
  • Runtime sensor, where it is needed. To see processes and behaviour in real time, a lightweight agent is added on the most critical workloads. It is an extra layer, not a precondition for starting.

Wiz's page on agentless scanning describes exactly this two-step pattern: read-only API permissions for the inventory, temporary snapshots for deep analysis, with the snapshot permissions listed for AWS and Google Cloud. It also notes that most organisations use agentless scanning and agents together. The practical benefit is that a first picture of your cloud comes without installing anything and without touching production systems.

CNAPP, SIEM and SOC: who does what?

A CNAPP does not replace a SIEM and is not a SOC. They are three different things that work well together.

  • The CNAPP works mainly on prevention: it shrinks the cloud attack surface before someone uses it and, through CDR, flags suspicious activity inside the cloud.
  • The SIEM collects and correlates events from everything else: endpoints, identities, email, network, applications. An attack rarely stays within one domain, and correlation is what follows it as it moves. Our overview of SIEM tools covers how they differ.
  • The SOC is the people and processes that read the signals, investigate and respond, around the clock. If you are weighing an in-house team against a provider, see what an MSSP does.

The link between the three is what Google put at the centre when it completed the acquisition of Wiz. In a post dated 11 March 2026, Thomas Kurian, CEO of Google Cloud, lists among the announced benefits a security platform combining Wiz with Google Security Operations to secure cloud-native applications at every stage: development, build and runtime. For the SIEM side of that picture, see our comparison of Microsoft Sentinel and Google SecOps.

There is also a practical limit. A CNAPP finds and ranks problems, but people do the fixing. Someone has to take the priority queue, route it to the teams that own the resources and check that the fix holds over time. Without that work, even a good platform becomes another dashboard.

When do you need a CNAPP?

Not everyone needs one, and not all at once. These are the signals that usually make it worthwhile.

  • You run real workloads on IaaS or PaaS (virtual machines, containers, managed databases, functions) on AWS, Google Cloud or Azure, not only SaaS applications.
  • Your cloud has grown faster than your team: many accounts or projects, several teams creating resources, an inventory nobody can vouch for.
  • You use Kubernetes or release often, and configurations change every week.
  • You work across more than one cloud: each provider has its own security console, and none of them gives you the overall view.
  • Customers, auditors or investors ask for evidence: security questionnaires, technical due diligence, ISO 27001 or SOC 2 audits that reach into the cloud environment.

What NIS2 and DORA expect

Neither law names a product, but both describe outcomes that a CNAPP documents on the cloud perimeter.

  • NIS2. Article 21(2) of Directive (EU) 2022/2555 lists the minimum cybersecurity risk-management measures. Among them: supply chain security (point d), security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure (point e), and human resources security, access control policies and asset management (point i). Inventory, vulnerabilities and permissions in the cloud are the evidence those measures rest on. Our guide to the NIS2 Directive covers the full set of obligations.
  • DORA. Article 8(4) of Regulation (EU) 2022/2554 asks financial entities to identify all information and ICT assets, map those considered critical, and map their configuration and the links and interdependencies between them. A CNAPP's inventory and relationship graph produce that map for cloud resources. More on what DORA asks in our DORA services page.

When it can wait

If your cloud is almost entirely SaaS (Microsoft 365, Google Workspace, a CRM) and you have a few stable virtual machines, the main risk lies in identities, email and tenant configuration. There, periodic vulnerability assessment and well-run access management do more than a new platform.

How do you evaluate a CNAPP?

Product sheets all look alike. These are the questions that separate platforms when you test them on your own environment.

  1. Coverage. Does it read all your clouds and the services you actually use, including managed Kubernetes, serverless and managed databases?
  2. Time to first picture. How long does it take to connect and see the full inventory, and with exactly which permissions?
  3. Quality of priorities. On one of your real accounts, how many of the top ten findings would you fix straight away? This test tells you the most.
  4. Explained attack paths. For each critical risk, does it show the chain (exposure, vulnerability, permission, data) and which link to break?
  5. Integrations. Does it send risks into your development teams' tickets and events into the SIEM, or does it stay an island?
  6. Who works the queue. Do you have the people to clear it, or do you need a partner to run it with you?

The most honest test is a proof of value on a real environment: a few weeks connected to your accounts tell you more than any demo on sample data.

Wiz, a concrete example of a CNAPP

Wiz is a CNAPP: it connects to cloud environments via API, without agents, builds a map of resources, permissions and data flows, and ranks the attack paths that can be exploited. In its announcement, Google describes Wiz as building a real-time map of application architecture, permissions, data flows and runtime behaviour, and using that context to identify exposure and exploitable attack paths.

Google completed its acquisition of Wiz on 11 March 2026. The Wiz team joined Google Cloud, the Wiz brand is retained and, according to the same announcement, Wiz products continue to work and be available across major clouds, including Amazon Web Services, Microsoft Azure and Oracle.

AmagisTech is a Wiz partner. We use it to take the picture of the cloud described above: connect to an organisation's accounts, see what is actually exposed and put the fixes in order.

In summary

A CNAPP brings configuration posture, workloads, permissions, data, Kubernetes, code and runtime detection into one data model, and its value lies in turning those signals into a few attack paths to close. It does not replace a SIEM or a SOC, and it earns its place when the cloud runs real workloads and has grown faster than the people who govern it. If you want to see what it would find in yours, start with our managed cloud security with Wiz: via API, without agents, with risks ranked by priority.

Frequently asked questions

CNAPP stands for cloud-native application protection platform. It is a cloud security platform that brings into one data model capabilities that used to be separate products: configuration posture (CSPM), workload security (CWPP), permissions (CIEM), sensitive data (DSPM), Kubernetes (KSPM), code security and runtime detection (CDR). According to Wiz, the term was coined by Gartner.
CSPM is one component of a CNAPP: it checks that cloud resource configurations follow rules and standards. A CNAPP adds analysis of workloads, permissions, data and code, and above all links these signals together, so it can show which combinations of issues open a real attack path.
No. A CNAPP works on posture and threats inside the cloud. A SIEM collects and correlates events from endpoints, identities, email, network and applications, and the SOC is the people who investigate and respond. They work best together: the CNAPP brings cloud context to the SIEM.
Not to get started. Many CNAPPs read inventory and configuration from the cloud provider's APIs with read permissions, and analyse disks from temporary snapshots, without installing anything. The snapshots need create and delete permissions, though, so it is not all read-only. A lightweight agent is needed only for real-time detection on critical workloads.
When real workloads run in the cloud (virtual machines, containers, managed databases), there is more than one account or cloud, Kubernetes is in use or releases are frequent, and customers or auditors ask for evidence. If your cloud is mostly SaaS, start with identities, email and tenant configuration.

Let's talk about your security.

A 30-minute call to understand where you stand today and tell you, with no commitment, where it pays to start.

Book a call