Jaa

Azure security baseline for Azure Policy

  • Artikkeli

This security baseline applies guidance from the Microsoft cloud security benchmark version 1.0 to Azure Policy. The Microsoft cloud security benchmark provides recommendations on how you can secure your cloud solutions on Azure. The content is grouped by the security controls defined by the Microsoft cloud security benchmark and the related guidance applicable to Azure Policy.

You can monitor this security baseline and its recommendations using Microsoft Defender for Cloud. Azure Policy definitions will be listed in the Regulatory Compliance section of the Microsoft Defender for Cloud portal page.

When a feature has relevant Azure Policy Definitions, they are listed in this baseline to help you measure compliance with the Microsoft cloud security benchmark controls and recommendations. Some recommendations may require a paid Microsoft Defender plan to enable certain security scenarios.

Note

Features not applicable to Azure Policy have been excluded. To see how Azure Policy completely maps to the Microsoft cloud security benchmark, see the full Azure Policy security baseline mapping file.

Security profile

The security profile summarizes high-impact behaviors of Azure Policy, which may result in increased security considerations.

Service Behavior Attribute Value
Product Category MGMT/Governance
Customer can access HOST / OS No Access
Service can be deployed into customer's virtual network False
Stores customer content at rest False

Identity management

For more information, see the Microsoft cloud security benchmark: Identity management.

IM-3: Manage application identities securely and automatically

Features

Managed Identities

Description: Data plane actions support authentication using managed identities. Learn more.

Supported Enabled By Default Configuration Responsibility
True False Customer

Feature notes: Azure Policy uses a managed identity for the remediation of non-compliant resources.

Configuration Guidance: Each Azure Policy assignment can be associated with only one managed identity. However, the managed identity can be assigned multiple roles. Configuration occurs in two steps: first create either a system-assigned or user-assigned managed identity, then grant it the necessary roles.

Reference: Remediate non-compliant resources with Azure Policy

Data protection

For more information, see the Microsoft cloud security benchmark: Data protection.

DP-3: Encrypt sensitive data in transit

Features

Data in Transit Encryption

Description: Service supports data in-transit encryption for data plane. Learn more.

Supported Enabled By Default Configuration Responsibility
True True Microsoft

Feature notes: Azure Policy leverages Microsoft's default encryption for data in transit.

Configuration Guidance: No additional configurations are required as this is enabled on a default deployment.

Reference: Double encryption

Microsoft Defender for Cloud monitoring

Azure Policy built-in definitions - Microsoft.GuestConfiguration:

Name
(Azure portal)		 Description Effect(s) Version
(GitHub)
Windows machines should be configured to use secure communication protocols To protect the privacy of information communicated over the Internet, your machines should use the latest version of the industry-standard cryptographic protocol, Transport Layer Security (TLS). TLS secures communications over a network by encrypting a connection between machines. AuditIfNotExists, Disabled 4.1.1

DP-4: Enable data at rest encryption by default

Features

Data at Rest Encryption Using Platform Keys

Description: Data at-rest encryption using platform keys is supported, any customer content at rest is encrypted with these Microsoft managed keys. Learn more.

Supported Enabled By Default Configuration Responsibility
True True Microsoft

Feature notes: Azure Policy leverages Microsoft's default encryption for data at rest.

Configuration Guidance: No additional configurations are required as this is enabled on a default deployment.

Reference: Double encryption

Next steps