| Source | Azure Portal | ||||||||||||||||||||||
| Display name | Microsoft Managed Control 1641 - Transmission Confidentiality And Integrity | Cryptographic Or Alternate Physical Protection | ||||||||||||||||||||||
| Id | d39d4f68-7346-4133-8841-15318a714a24 | ||||||||||||||||||||||
| 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 | ||||||||||||||||||||||
| Additional metadata |
Name/Id: ACF1641 / Microsoft Managed Control 1641 Category: System and Communications Protection Title: Transmission Confidentiality And Integrity | Cryptographic Or Alternate Physical Protection Ownership: Customer, Microsoft Description: The information system implements cryptographic mechanisms to Prevent unauthorized disclosure of information and detect changes to information during transmission unless otherwise protected by A hardened or alarmed carrier Protective Distribution System (PDS). Requirements: Azure uses encryption to prevent unauthorized disclosure of information and detect changes to information during transmission. Specifically, Azure provides FIPS 140-2 compliant ciphers that include integrity validation for customer connections, interconnected system connections, and remote access connections. For connections to customers, Azure is configured to negotiate FIPS compliant TLS protocols with supported client browsers, though non-FIPS compliant protocols are supported for legacy browser support. Connections within the accreditation boundary occur within Azure facilities. Since Azure owns and controls access to these connections, they do not require FIPS 140-2 encryption. However, service-to-service communications occur over TLS 1.2, and internal communication between Azure datacenters is transmitted over FIPS 140-2 compliant AES 256 link encryptors to the ensure confidentiality of data. |
||||||||||||||||||||||
| Mode | Indexed | ||||||||||||||||||||||
| Type | Static | ||||||||||||||||||||||
| Preview | False | ||||||||||||||||||||||
| Deprecated | False | ||||||||||||||||||||||
| Effect | Fixed audit |
||||||||||||||||||||||
| RBAC role(s) | none | ||||||||||||||||||||||
| Rule aliases | none | ||||||||||||||||||||||
| Rule resource types | IF (2) Microsoft.Resources/subscriptions Microsoft.Resources/subscriptions/resourceGroups |
||||||||||||||||||||||
| Compliance |
The following 1 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1641 - Transmission Confidentiality And Integrity | Cryptographic Or Alternate Physical Protection' (d39d4f68-7346-4133-8841-15318a714a24)
| ||||||||||||||||||||||
| Initiatives usage |
|
||||||||||||||||||||||
| History | none | ||||||||||||||||||||||
| JSON compare | n/a | ||||||||||||||||||||||
| JSON |
|