| Source | Azure Portal | ||
| Display name | Microsoft Managed Control 1242 - Contingency Planning Policy And Procedures | ||
| Id | cf3b3293-667a-445e-a722-fa0b0afc0958 | ||
| Version | 1.0.0 Details on versioning |
||
| Category | Regulatory Compliance Microsoft Learn |
||
| Description | Microsoft implements this Contingency Planning control | ||
| Additional metadata |
Name/Id: ACF1242 / Microsoft Managed Control 1242 Category: Contingency Planning Title: Contingency Planning Policy And Procedures - Creating Policy And Procedures Ownership: Customer, Microsoft Description: The organization: Develops, documents, and disseminates to personnel with contingency planning roles and responsibilities: A contingency planning policy that addresses purpose, scope, roles, responsibilities, management commitment, coordination among organizational entities, and compliance; and Procedures to facilitate the implementation of the contingency planning policy and associated contingency planning controls; and Requirements: Azure addresses the contingency planning policy as part of the Microsoft security policies, of which there are two sets: the Microsoft Security Policy (MSP) that is applicable to all personnel, and the Microsoft Security Program Policy (MSPP), which is applicable to all personnel that have a responsibility for security. The Microsoft Information Risk Management Council (IRMC) is the governance body with review and approval responsibility for the MSP and MSPP. Within Azure, the MSPP specifically applies to all personnel involved in designing, building, and operating Azure and across all information and processes used in the conduct of Microsoft business. All Azure personnel are accountable and responsible for complying with these guiding principles within their designated roles. The policy addresses the following: * Business continuity process * Alternate systems facilities * Service resiliency Additionally, the policy addresses the purpose, scope, roles, responsibilities, compliance requirements, and required coordination among the various Microsoft organizations that provide some level of support to all services. The policies indicate Microsoft management’s commitment and are a component of the risk management strategy which provides Azure personnel with a current set of clear and concise information security requirements. The Azure Business Continuity and Disaster Recovery SOP implements the contingency planning policy and associated controls. Azure also implements policy and procedures through the Business Continuity Management (BCM) System Manual managed by the C+AI Azure Business Continuity Management team. The purpose of this manual is to document the BCM methods and approach to be implemented by Azure services, internal Azure groups, and support functions. It defines the purpose of the program and sets forth the drivers, goals, objectives, and strategies that are used as guiding principles. The BCM program is in alignment with those of Microsoft’s Enterprise Business Continuity Management (EBCM) Program. The SOP and BCM System Manual document the following procedures: * Continuity management process * Business impact and dependency analysis * Writing and implementing continuity plans * Continuity planning framework The MSP is available to all Microsoft personnel on the Microsoft Policy website on the Microsoft intranet, and the MSPP and Security Standards are available through the Liquid tool, also on the Microsoft intranet. The Azure SOPs are stored in the Azure Security, Privacy & Compliance SharePoint site. This SharePoint site is accessible to all Azure personnel. The Azure BCM System Manual is maintained in the Azure Business Continuity and Disaster Recovery (BCDR) website on the Microsoft intranet. Service teams may supplement the Azure policies and procedures with offering-specific policies and procedures. Service-team-specific policies and procedures associated with contingency planning are documented and stored within internal Azure SharePoint sites. Only personnel with authorized credentials, adequate levels of permission, legitimate need to know, and specific roles and responsibilities are given access to the service-team-specific policies or procedures. |
||
| 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 |
|