AzPolicyAdvertizer

last sync: 2025-Oct-31 18:22:59 UTC

Microsoft Managed Control 1645 - Cryptographic Key Establishment And Management | Symmetric Keys | Regulatory Compliance - System and Communications Protection

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1645 - Cryptographic Key Establishment And Management | Symmetric Keys
Id afbd0baf-ff1a-4447-a86f-088a97347c0c
Version 1.0.0
Details on versioning
Versioning Versions supported for Versioning: 0
Built-in Versioning [Preview]
Category Regulatory Compliance
Microsoft Learn
Description Microsoft implements this System and Communications Protection control
Cloud environments AzureCloud = true
AzureUSGovernment = true
AzureChinaCloud = unknown
Available in AzUSGov The Policy is available in AzureUSGovernment cloud. Version: '1.0.0'
Repository: Azure-Policy afbd0baf-ff1a-4447-a86f-088a97347c0c
Additional metadata Name/Id: ACF1645 / Microsoft Managed Control 1645
Category: System and Communications Protection
Title: Cryptographic Key Establishment And Management | Symmetric Keys
Ownership: Customer, Microsoft
Description: The organization produces, controls, and distributes symmetric cryptographic keys using NIST FIPS-compliant key management technology and processes.
Requirements: Azure encrypts storage keys using symmetric cryptography and follows the below defined key management process: * Key Generation: RDFE generates keys using Random Generator Algorithm. * Key Distribution: Storage keys are distributed over TLS encrypted communication channel. * Key Storage: Storage keys are stored in an encrypted format using AES 256 algorithm. * Key Recovery: In case of a key compromise, lost or stolen, a new key is generated and replaced in the Storage account. There is a backup key that is stored in Storage used for operation while the new key is generated.
Mode Indexed
Type Static
Preview False
Deprecated False
Effect Fixed
audit
RBAC role(s) none
Rule aliases none
Rule resource types IF (2)
Compliance
The following 2 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1645 - Cryptographic Key Establishment And Management | Symmetric Keys' (afbd0baf-ff1a-4447-a86f-088a97347c0c)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
NIS2 DP._Data_Protection_8 NIS2_DP._Data_Protection_8 NIS2_DP._Data_Protection_8 DP. Data Protection Policies and procedures regarding the use of cryptography and, where appropriate, encryption n/a In order to safeguard the security of public electronic communications networks and publicly available electronic communications services, the use of encryption technologies, in particular end-to-end encryption as well as data-centric security concepts, such as cartography, segmentation, tagging, access policy and access management, and automated access decisions, should be promoted. Where necessary, the use of encryption, in particular end-to-end encryption should be mandatory for providers of public electronic communications networks or of publicly available electronic communications services in accordance with the principles of security and privacy by default and by design for the purposes of this Directive. The use of end-to-end encryption should be reconciled with the Member States’ powers to ensure the protection of their essential security interests and public security, and to allow for the prevention, investigation, detection and prosecution of criminal offences in accordance with Union law. However, this should not weaken end-to-end encryption, which is a critical technology for the effective protection of data and privacy and the security of communications. 32
op.exp.10 Cryptographic key protection op.exp.10 Cryptographic key protection 404 not found n/a n/a 50
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type polSet in AzUSGov
NIS2 32ff9e30-4725-4ca7-ba3a-904a7721ee87 Regulatory Compliance GA BuiltIn unknown
Spain ENS 175daf90-21e1-4fec-b745-7b4c909aa94c Regulatory Compliance GA BuiltIn unknown
History none
JSON compare n/a
JSON
api-version=2021-06-01
EPAC