| Source | Azure Portal | ||
| Display name | Microsoft Managed Control 1665 - Process Isolation | ||
| Id | 5df3a55c-8456-44d4-941e-175f79332512 | ||
| 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 5df3a55c-8456-44d4-941e-175f79332512 |
||
| Additional metadata |
Name/Id: ACF1665 / Microsoft Managed Control 1665 Category: System and Communications Protection Title: Process Isolation Ownership: Customer, Microsoft Description: The information system maintains a separate execution domain for each executing process. Requirements: All Azure servers run operating systems that maintain separate execution domains for each executing process by assigning a private virtual address space to each process. In addition, all operating systems used in the Azure environment employ multi-thread processing, which is consistent with modern operating systems. Multi-thread processing allows for multiple processes to be executed concurrently and in isolation. See the following TechNet article for more information: |
||
| Mode | Indexed | ||
| Type | Static | ||
| Preview | False | ||
| Deprecated | False | ||
| Effect | Fixed audit |
||
| RBAC role(s) | none | ||
| Rule aliases | none | ||
| Rule resource types | IF (2) |
||
| Compliance | Not a Compliance control | ||
| Initiatives usage | none | ||
| History | none | ||
| JSON compare | n/a | ||
| JSON |
|