Microsoft has stopped treating Defender for Cloud as an Azure-only product. Over July and August 2026, the company shipped two updates that push its cloud security posture management (CSPM) tooling directly into Amazon Web Services and Google Cloud territory: general availability for serverless container posture scanning, and a preview expansion of Kubernetes node vulnerability assessment to Amazon EKS and Google GKE. Both moves land at a moment when independent research keeps finding the same uncomfortable number: the vast majority of organizations running containers have already had a security incident tied to them.
The timing is not a coincidence. Red Hat’s State of Kubernetes Security research, still being cited across 2026 industry reports, found that 89% of organizations had at least one container or Kubernetes-related security incident in the prior 12 months, with 45% of those incidents traced directly to misconfiguration. A separate 2026 survey from ActiveState found 82% of DevSecOps leaders believe their organization has likely suffered a container-related breach in the same window, even though 100% of those same leaders called containerization critical to their production strategy. Microsoft’s answer is to fold AWS and GCP workloads into a single posture graph instead of asking security teams to stitch together three separate consoles.
What Microsoft Just Shipped: Defender for Cloud’s Cross-Cloud Push
Two distinct capabilities moved forward in the same release cycle. On July 1, 2026, Microsoft announced that serverless posture coverage in Microsoft Defender CSPM had reached general availability, according to the official Microsoft Learn documentation. Then, in release notes dated August 18, 2026, Microsoft confirmed that Kubernetes node vulnerability assessment, previously limited to Azure Kubernetes Service (AKS), now extends to Amazon EKS and Google GKE nodes, per the Defender for Cloud release notes.
The two features solve different problems. Node vulnerability assessment scans the underlying virtual machines that host Kubernetes worker nodes for operating-system-level flaws, then surfaces an “Upgrade Kubernetes nodes” recommendation pointing to a patched node image or Kubernetes version. Serverless posture management instead treats things like Azure Container Apps, Azure Container Instances, and Amazon ECS tasks running on AWS Fargate as first-class inventory items, something CSPM tools have historically struggled with because serverless containers spin up and disappear faster than traditional agent-based scanners can track them.
Put together, the two updates mean a security team running Defender for Cloud can now pull vulnerability, exposure, identity, and configuration signals from Azure, AWS, and Google Cloud container workloads into one attack-path graph, rather than exporting findings from three native tools and manually correlating them in a spreadsheet.
Kubernetes Node Vulnerability Assessment Reaches EKS and GKE
Node vulnerability assessment is not new to Defender for Cloud, it has covered AKS nodes for years as a generally available capability. What changed in August 2026 is the extension to EKS and GKE, and it currently ships as a preview feature rather than GA, according to the Defender for Containers support matrix. The scan targets the operating system and installed software packages on the VMs backing each node pool, flags known CVEs, and links back to a specific remediation path, according to Microsoft’s node vulnerability remediation guide.
Turning the feature on is not free of prerequisites. Node VA for EKS and GKE requires Agentless scanning for machines to already be enabled, and access to the capability comes bundled through one of three Defender plans: Defender for Containers, Defender CSPM, or Defender for Servers Plan 2. Microsoft has not published a standalone price for the EKS/GKE expansion itself, so the practical cost depends on which of those three plans a given organization is already licensed for.
The expansion arrived alongside a broader bundle of container security features that reached general availability on August 3, 2026: container-level misconfiguration recommendations for Kubernetes, an “Upgrade AKS version” recommendation, vulnerability assessment for runtime-discovered container images on EKS and GKE, and scanning support for Docker Hardened Images in supported registries. Taken together, it is the most aggressive cross-cloud push Defender for Cloud’s container team has made in a single summer.
Serverless Posture Management Goes GA
Serverless containers have been a blind spot for most CSPM tools because there is no persistent VM to scan and no long-lived node to agent-scan. Microsoft’s answer, now generally available, discovers Azure Container Apps, Azure Container Instances, and AWS ECS tasks running on Fargate as first-class assets inside a unified cloud inventory, then assesses workload-specific vulnerabilities, insecure dependencies, and risky configurations. According to Microsoft’s own GA announcement, the feature surfaces exposure, identity, permission, and configuration context to help security teams prioritize which attack paths actually matter, rather than drowning them in a flat list of findings.
Google Cloud has not stayed still either. Security Command Center recently added “Malicious Skill” runtime threat detectors covering GKE, Cloud Run, and Google’s Agent Platform, plus dedicated threat detection for Cloud Run worker pools, based on Google’s own Cloud Threat Horizons report. That report also shows a genuine improvement on one front: initial access via cloud misconfiguration dropped from 29.4% of incidents in the first half of 2025 to 21% in the second half, and exposure of sensitive UIs or APIs fell from 11.8% to 4.9% over the same window. Progress is real, but the baseline it is falling from was extremely high.
The Misconfiguration Numbers Driving the Urgency
The stats behind this release cycle are hard to ignore. Beyond the Red Hat and ActiveState figures already cited, an academic analysis of large public container image repositories found that 98.0% of scanned images carried at least one misconfiguration, 96.3% shipped with at least one known package vulnerability, and 93.4% included a critical-severity vulnerability. Separately, Verizon’s 2026 Data Breach Investigations Report data, as summarized by cloud researchers, found cloud misconfiguration accounted for 14% of all global breaches in the first quarter of 2026, up from 9% in 2024.
Vulnerability volume is climbing too. Veracode’s Cyber Risk Intelligence report tracked roughly 7,454 CVEs published in June 2026 alone, a 14.5% month-over-month jump. Kubernetes itself has not been exempt: independent tracking put the count at eight published Kubernetes CVEs by spring 2026, averaging a CVSS score of 7.5, a figure that continued climbing through the summer as the runc container escape class of bugs kept researchers busy.
| Metric | Figure | Source / Period |
|---|---|---|
| Organizations with a container/Kubernetes incident in 12 months | 89% | Red Hat State of Kubernetes Security, cited in 2026 reports |
| Kubernetes incidents caused by misconfiguration | 45% | Red Hat State of Kubernetes Security |
| DevSecOps leaders suspecting a container-related breach | 82% | ActiveState, 2026 State of Vulnerability Management report |
| Scanned container images with at least one misconfiguration | 98.0% | 2026 academic image-corpus analysis |
| Scanned images with a critical-severity vulnerability | 93.4% | 2026 academic image-corpus analysis |
| Global breaches attributed to cloud misconfiguration, Q1 2026 | 14% | Verizon DBIR 2026, up from 9% in 2024 |
| Cloud misconfiguration-driven initial access, H2 2025 | 21% | Google Cloud Threat Horizons H1 2026, down from 29.4% |
| CVEs published, June 2026 | ~7,454 | Veracode Cyber Risk Intelligence |
GA vs. Preview: What’s Actually Shipping Today
Status matters here because preview features carry different SLAs, support commitments, and, in some organizations, different procurement approval paths than GA features. Anyone rolling this out across a production fleet needs to know exactly which piece is still preview and which piece Microsoft stands behind as generally available.
| Feature | Cloud Coverage | Status | Shipped | Requires |
|---|---|---|---|---|
| Kubernetes node vulnerability assessment | AKS | GA | Prior to 2026 | Defender for Containers, CSPM, or Servers Plan 2 |
| Kubernetes node vulnerability assessment | Amazon EKS, Google GKE | Preview | August 18, 2026 | Agentless scanning for machines |
| Serverless container posture management | Azure Container Apps, ACI, AWS ECS on Fargate | GA | July 1, 2026 | Defender CSPM |
| Container-level misconfiguration recommendations | AKS, EKS, GKE | GA | August 3, 2026 | Defender for Containers |
| Docker Hardened Images scanning | Supported registries | GA | August 2026 | Defender for Containers |
How This Compares to AWS Security Hub
AWS has not ignored the cross-cloud pressure. In June 2026, AWS extended Security Hub to monitor Microsoft Azure resources, covering VMs, container images, Function Apps, and identities, according to the official AWS announcement. Security Hub also picked up blast radius mapping and attack chain graphs, features that echo the attack-path prioritization Microsoft is now applying to serverless containers. AWS additionally shipped five new Security Hub controls for the AWS Foundational Security Best Practices standard in April 2026, covering API Gateway, EC2, EKS, and SageMaker resources, per AWS Security Hub documentation.
What AWS has not published, at least not in a form comparable to Microsoft’s announcement, is a dedicated node-level vulnerability assessment feature for EKS that mirrors what Defender for Cloud now offers. Security Hub’s EKS coverage today leans on hardening controls and CSPM checks rather than the OS-level node scanning Microsoft is rolling out. That gap is exactly the kind of feature parity race that tends to close within one or two release cycles once a competitor draws attention to it publicly.
Where Wiz, Google, and Palo Alto Fit
The broader cloud-native application protection platform (CNAPP) market has already been consolidating around the same premise Microsoft is now chasing: one console, every cloud. Wiz built its reputation on agentless, API-based scanning across AWS, Azure, GCP, Oracle Cloud, Alibaba Cloud, Kubernetes, and OpenShift, and its position in the market shifted further after reports of a roughly $32 billion acquisition by Google. Palo Alto’s Prisma Cloud, meanwhile, markets itself as carrying the broadest workload coverage of any CNAPP, spanning containers, VMs, serverless, and infrastructure-as-code, and it ships with FedRAMP High authorization, a detail that matters for government and regulated-industry buyers Microsoft and AWS are also chasing.
Google’s own Security Command Center Premium continues to serve as its native CSPM layer, with attack-path simulation and posture-as-code features defined through YAML policy files. What Microsoft’s July-August push adds to this landscape is not a new category, cross-cloud CNAPP already existed, but a hyperscaler-native option that does not require a third-party vendor relationship at all if a customer is already standardized on Azure licensing and Microsoft security tooling.
Market Impact: Why This Matters for Multi-Cloud Budgets
For security teams, the practical effect is a new decision point: keep paying for a dedicated CNAPP vendor like Wiz or Prisma Cloud, or consolidate posture management into whichever hyperscaler’s native tooling already covers the most ground. Microsoft’s bet is that enterprises running mixed Azure-AWS-GCP environments will prefer a single Defender for Cloud bill and a single pane of glass over managing three native consoles plus a fourth third-party layer on top.
That bet has real budget implications. FinOps teams have spent the last two years pushing back on tool sprawl, and every redundant security product is a line item that gets scrutinized during renewal season. A native Defender for Cloud feature that covers EKS and GKE, even in preview, gives procurement teams leverage to ask whether a standalone CNAPP subscription is still justified, particularly for organizations where Azure is already the primary identity and licensing anchor through Entra ID and Microsoft 365 E5 security bundles.
At the same time, the preview status of EKS/GKE node VA means most large enterprises will not rip out an existing CNAPP contract based on this alone. Preview features lack the support SLAs procurement teams typically require before signing off on removing a production security tool, so the near-term effect looks more like added leverage in negotiations than outright vendor displacement.
Historical Context: From Azure Security Center to Cross-Cloud CSPM
Defender for Cloud did not start as a multi-cloud product. It grew out of Azure Security Center, a tool built for a single-cloud world where Azure resources were the only thing that mattered. Microsoft added native AWS and GCP connectors over the following years, but for a long time those connectors offered shallower coverage than the deep, agent-based scanning available for Azure-native resources. The July-August 2026 releases mark one of the clearest signs yet that Microsoft is closing that coverage gap rather than treating AWS and GCP support as a secondary feature.
That trajectory mirrors what happened industry-wide as Kubernetes itself became the default container orchestrator across all three hyperscalers. Once EKS, AKS, and GKE all ran the same open-source control plane, the case for cloud-specific security tooling weakened, and vendors on all sides, hyperscaler and independent alike, started building toward cross-cloud parity rather than deep single-cloud specialization.
The Kubernetes CVE Backdrop Behind the Timing
None of this is happening in a vacuum. Container escape vulnerabilities tied to runc, the low-level runtime underneath most container platforms including Docker and Kubernetes, drew heavy researcher attention through 2026. Combined with the roughly 7,454 CVEs published in June 2026 alone across the broader software ecosystem, security teams running Kubernetes clusters across multiple clouds have had little room to treat vulnerability management as a quarterly task. Node-level scanning that used to be an AKS-only capability now needs to cover EKS and GKE simply because attackers do not care which cloud a vulnerable node happens to run on.
What Security Teams Should Actually Do Next
Teams already licensed for Defender for Containers, Defender CSPM, or Defender for Servers Plan 2 can enable EKS and GKE node vulnerability assessment today by turning on Agentless scanning for machines and connecting their AWS and GCP accounts through Defender for Cloud’s environment settings. Because the feature is still preview, it is worth testing against a non-production cluster first and comparing its findings against whatever tool, whether that is Wiz, Prisma Cloud, or native AWS/GCP scanning, is currently in place before making any procurement decisions.
For teams running serverless containers on Azure Container Apps, Azure Container Instances, or AWS Fargate-backed ECS, the GA serverless posture feature is a lower-risk starting point since it already carries Microsoft’s full support commitment. Given that 98.0% of scanned images in 2026 research carried at least one misconfiguration, simply turning on discovery for serverless workloads that were previously invisible to CSPM tooling is likely to surface real findings almost immediately.
Predictions: Where Cross-Cloud Container Security Goes From Here
- Kubernetes node vulnerability assessment for EKS and GKE will likely reach general availability within two to three release cycles, following the same preview-to-GA pattern serverless posture management just completed.
- AWS Security Hub will probably respond with a dedicated node-level vulnerability assessment feature for EKS rather than continuing to rely solely on hardening controls, given the direct comparison Microsoft’s release now invites.
- Expect continued CNAPP market consolidation, with hyperscaler-native tools increasingly used as a baseline layer and specialist vendors like Wiz and Prisma Cloud pushed toward differentiating on depth, remediation automation, and multi-cloud identity correlation rather than basic coverage.
- Misconfiguration-driven breach numbers will stay stubbornly high through 2027 unless remediation tooling closes the gap between detection and fix, since detection alone has not moved the 89% incident rate in recent years.
- More enterprises with genuine multi-cloud Kubernetes footprints will consolidate around a single CSPM or CNAPP vendor during 2027 renewal cycles, using tool-sprawl reduction as a FinOps talking point rather than a pure security decision.
The Bigger Picture for DevSecOps Teams
The real story behind Defender for Cloud’s EKS and GKE expansion is not the feature list, it is what the feature list says about where hyperscalers think the competition actually is. Microsoft, AWS, and Google are no longer just competing for cloud compute and storage spend, they are competing for the security console that sits on top of workloads regardless of which cloud those workloads run on. Whichever vendor’s posture management tool becomes the default correlation layer across a customer’s entire multi-cloud footprint gains outsized influence over renewal conversations for everything else that vendor sells, from identity to AI infrastructure.
That dynamic explains why Microsoft is willing to ship a preview feature that actively helps customers secure workloads running on a rival’s cloud. It is a land grab for the security console seat, not just a container-scanning feature update, and the 89% incident rate cited by Red Hat’s research gives every hyperscaler and CNAPP vendor a shared talking point to justify the investment.
Frequently Asked Questions
What is Microsoft Defender for Cloud’s Kubernetes node vulnerability assessment for EKS and GKE?
It is a scanning capability that checks the virtual machines hosting Amazon EKS and Google GKE Kubernetes nodes for operating-system-level vulnerabilities, then recommends specific node or Kubernetes version upgrades to fix what it finds. It extends a capability that already existed for Azure Kubernetes Service (AKS) nodes.
Is EKS and GKE node vulnerability assessment generally available yet?
No. As of the August 18, 2026 release notes, the feature is in preview for EKS and GKE nodes, while the same capability remains generally available for AKS. Preview status typically means reduced support commitments compared to GA features.
What is serverless container posture management and what does it cover?
It is a Defender CSPM capability that discovers serverless container workloads, specifically Azure Container Apps, Azure Container Instances, and Amazon ECS tasks running on AWS Fargate, as first-class assets, then assesses their vulnerabilities, insecure dependencies, and misconfigurations. It reached general availability on July 1, 2026.
How much does Microsoft Defender for Cloud’s container security cost?
Microsoft has not published a standalone price for the EKS/GKE node VA expansion or serverless posture management. Access depends on existing licensing for Defender for Containers, Defender CSPM, or Defender for Servers Plan 2, and node VA additionally requires Agentless scanning for machines to be enabled.
How does this compare to AWS Security Hub’s cross-cloud features?
AWS Security Hub added Azure resource monitoring in June 2026, covering VMs, container images, Function Apps, and identities, plus blast radius mapping and attack chain graphs. However, AWS has not published a dedicated EKS node-level vulnerability assessment feature comparable to what Defender for Cloud now offers.
What is causing most container security incidents in 2026?
Misconfiguration remains the dominant cause. Red Hat research found 45% of Kubernetes security incidents trace back to misconfiguration, and separate 2026 image-scanning research found 98.0% of scanned container images carried at least one misconfiguration.
Do I need Defender for Containers or Defender CSPM to use these new features?
Yes, one of the three plans is required: Defender for Containers, Defender CSPM, or Defender for Servers Plan 2, depending on which feature and workload type is being enabled. Node vulnerability assessment additionally requires Agentless scanning for machines.
Is Wiz still an independent CNAPP vendor after the reported Google deal?
Wiz has been widely reported as being acquired by Google in a deal valued at roughly $32 billion. Its product continues to be positioned as a broad, agentless CNAPP covering AWS, Azure, GCP, Oracle Cloud, Alibaba Cloud, Kubernetes, and OpenShift.
