last sync: 2024-Jun-14 18:20:16 UTC

Microsoft Managed Control 1243 - Contingency Planning Policy And Procedures | Regulatory Compliance - Contingency Planning

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1243 - Contingency Planning Policy And Procedures
Id ca9a4469-d6df-4ab2-a42f-1213c396f0ec
Version 1.0.0
Details on versioning
Category Regulatory Compliance
Microsoft Learn
Description Microsoft implements this Contingency Planning control
Additional metadata Name/Id: ACF1243 / Microsoft Managed Control 1243
Category: Contingency Planning
Title: Contingency Planning Policy And Procedures - Reviewing Policy And Procedures
Ownership: Customer, Microsoft
Description: The organization: Reviews and updates the current: Contingency planning policy at least annually; and Contingency planning 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. The BCM System Manual approvers review and update the document at least annually and when required by a significant change. The Azure BCM System Manual is maintained in the Azure BCDR website on the Microsoft intranet. Affected individuals are notified by email when updates, changes, or modifications are made.
Mode Indexed
Type Static
Preview False
Deprecated False
Effect Fixed
RBAC role(s) none
Rule aliases none
Rule resource types IF (2)
The following 4 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1243 - Contingency Planning Policy And Procedures' (ca9a4469-d6df-4ab2-a42f-1213c396f0ec)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
op.cont.1 Impact analysis op.cont.1 Impact analysis 404 not found n/a n/a 68
op.cont.2 Continuity plan op.cont.2 Continuity plan 404 not found n/a n/a 68
op.cont.3 Periodic tests op.cont.3 Periodic tests 404 not found n/a n/a 91
op.cont.4 Alternative means op.cont.4 Alternative means 404 not found n/a n/a 95
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
Spain ENS 175daf90-21e1-4fec-b745-7b4c909aa94c Regulatory Compliance GA BuiltIn
History none
JSON compare n/a