AzPolicyAdvertizer

last sync: 2025-Apr-29 17:16:02 UTC

Microsoft Managed Control 1062 - Remote Access | Protection Of Confidentiality / Integrity Using Encryption | Regulatory Compliance - Access Control

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1062 - Remote Access | Protection Of Confidentiality / Integrity Using Encryption
Id 4708723f-e099-4af1-bbf9-b6df7642e444
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 Access Control 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 4708723f-e099-4af1-bbf9-b6df7642e444
Additional metadata Name/Id: ACF1062 / Microsoft Managed Control 1062
Category: Access Control
Title: Remote Access | Protection Of Confidentiality / Integrity Using Encryption
Ownership: Customer, Microsoft
Description: The information system implements cryptographic mechanisms to protect the confidentiality and integrity of remote access sessions.
Requirements: For all asset types, Azure uses cryptographic controls to protect the confidentiality, authenticity and integrity of sensitive data while in transit or at rest. To ensure confidentiality, Azure uses both symmetric and asymmetric keys for encrypting sensitive data to prevent access from unauthorized parties. For example, secrets such as the Storage Key are encrypted using the receiving component’s public key prior to transmission. As part of the component’s deployment, the private key is installed into the runtime environment by leveraging the Azure Certificate Store (WACS) functionality provided by the Fabric. The component uses the private key installed into the WACS to decrypt the secret. To ensure integrity, Azure uses asymmetric keys to protect unauthorized modification to sensitive data during transmission across components. For example, a component might generate a file then compute a cryptographic checksum over that file’s contents, then sign that checksum via its private key. Upon subsequent access of that file, the component first validates that the file’s contents had not been modified by recomputing the checksum over the current file contents then verifying the signature, which only requires the public key. Azure uses FIPS 140-2 validated cryptography for access. Azure Remote Desktop Protocol (RDP) and SSL VPN services are configured to use FIPS 140-2 validated TLS 1.2 encryption for access. Encryption is required for all connections. PKI certificates are utilized within Azure on the internal RD gateways and are obtained through the Azure PKI, and SSL certificates utilized by access solutions.
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 1 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1062 - Remote Access | Protection Of Confidentiality / Integrity Using Encryption' (4708723f-e099-4af1-bbf9-b6df7642e444)
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
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type polSet in AzUSGov
[Preview]: NIS2 32ff9e30-4725-4ca7-ba3a-904a7721ee87 Regulatory Compliance Preview BuiltIn unknown
History none
JSON compare n/a
JSON
api-version=2021-06-01
EPAC