| Source | Azure Portal | ||||||
| Display name | Microsoft Managed Control 1001 - Access Control Policy And Procedures Requirements | ||||||
| Id | 4e26f8c3-4bf3-4191-b8fc-d888805101b7 | ||||||
| Version | 1.0.1 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 | ||||||
| Additional metadata |
Name/Id: ACF1001 / Microsoft Managed Control 1001 Category: Access Control Title: Access Control Policy And Procedures - Reviewing Policy And Procedures Ownership: Customer, Microsoft Description: The organization: Reviews and updates the current: Access control policy at least annually; and Access control procedures at least annually or whenever a significant change occurs. Requirements: The Microsoft Information Risk Management Council (IRMC) organization is the governance body with approval responsibility for the Microsoft Security Policy (MSP) and Microsoft Security Program Policy (MSPP). The IRMC consists of representatives from security and risk management teams across Microsoft including Core Services Engineering and Operations (CSEO), Azure, and Global Security. The Customer Security and Trust: Security Engineering (CST-SE) organization manages the review and approval process and maintains the policies. On an annual basis, the CST-SE conducts a line-by-line review of the MSP and MSPP. The Microsoft Security Policy Governance SOP describes each member’s role, types and frequency of review, escalation paths, approval process, and formal publishing procedures of the security policy. Throughout the year, if necessary, CST-SE may convene with the IRMC to conduct reviews after a significant review or change request. The approved policy update is published within the relevant tool on the Microsoft intranet. If service teams establish service-specific or team-specific policies, the respective service teams update the necessary policies at least annually. The Azure SOP team updates the Azure SOPs at least annually through a formal review process. If needed, the Azure SOP team makes updates after a significant change affecting policy or procedure execution as well. Certain service teams may also establish their own procedures, SOPs, or runbooks. If established, service-team-specific procedures are reviewed and updated by their respective teams as needed. |
||||||
| 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 | Not a Compliance control | ||||||
| Initiatives usage | none | ||||||
| History |
|
||||||
| JSON compare |
compare mode:
version left:
version right:
|
||||||
| JSON |
|