Microsoft Defender for Cloud
Cloud and workloads

Kubernetes misconfiguration enforcement

In brief

The documentation now adds prerequisite and permissions guidance, an OCI artifact reference for the policy bundle, and clearer instructions for setting the Helm value that enables misconfiguration enforcement. It also explains the admission controller’s Audit-mode behavior.

What Defender admins need to know

Administrators performing manual Helm deployments should follow the revised instructions and verify the listed prerequisites and permissions.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Manually enable misconfiguration enforcement with Helm

Before you start, make sure you completed the prerequisites, including enabling Defender for Containers and verifying your permissions.

To manually enable misconfiguarion enforcement with Helm:

  1. Follow the Helm installation guide for the Defender for Containers sensor for your environment.

  2. During Helm chart installation, use the latest supported chart tag fromtag. Use the following Helm repository:OCI artifact reference to select the Microsoft Defender for Containers policy bundle during gated deployment configuration:

    oci://mcr.microsoft.com/azuredefender-preview/microsoft-defender-for-containers
    
  3. IncludeSet the following value:Helm value to enable misconfiguration policies in the Defender admission controller so that policy enforcement is applied to your cluster:

    defender-admission-controller.enableMisconfigurationPolicies=true
    

Create a misconfiguration enforcement policy

By default, Defender for Containers creates the Default K8s misconfiguration rule in Audit mode, scoped to all resources. While in Audit mode, the admission controller (the Kubernetes component that evaluates resources against your policies before they're admitted into the cluster) logs violations but allows deployments to continue. You can create custom policies scoped to specific subscriptions, clusters, or namespaces.

  1. Sign in to the Azure portal.