| Source | Azure Portal | ||
| Display name | Microsoft Managed Control 1616 - System And Communications Protection Policy And Procedures | ||
| Id | 2006457a-48b3-4f7b-8d2e-1532287f9929 | ||
| Version | 1.0.0 Details on versioning |
||
| Category | Regulatory Compliance Microsoft Learn |
||
| Description | Microsoft implements this System and Communications Protection control | ||
| Additional metadata |
Name/Id: ACF1616 / Microsoft Managed Control 1616 Category: System and Communications Protection Title: System And Communications Protection Policy And Procedures - Reviewing Policy And Procedures Ownership: Customer, Microsoft Description: The organization: Reviews and updates the current: System and communications protection policy at least annually; and System and communications protection 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 team updates the Azure SOPs at least annually through a formal review process. If needed, the Azure team updates the SOP after a significant change affecting policy execution as well. If established, service-team-specific procedures are updated by their respective teams. The individual service teams review and update their respective SOPs at least annually and when required by a significant change. The Azure team updates the Security Standards at least annually through a formal review process. If needed, the Azure team updates the Standards after a significant change affecting policy execution as well. If established, service-team-specific procedures are updated by their respective teams. The individual service teams review and update their respective SOPs at least annually and when required by a significant change. |
||
| 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 | none | ||
| JSON compare | n/a | ||
| JSON |
|