last sync: 2024-Sep-18 17:50:24 UTC

Resume all mission and business functions | Regulatory Compliance - Operational

Azure BuiltIn Policy definition

Source Azure Portal
Display name Resume all mission and business functions
Id 91a54089-2d69-0f56-62dc-b6371a1671c0
Version 1.1.0
Details on versioning
Versioning Versions supported for Versioning: 1
1.1.0
Built-in Versioning [Preview]
Category Regulatory Compliance
Microsoft Learn
Description CMA_C1254 - Resume all mission and business functions
Additional metadata Name/Id: CMA_C1254 / CMA_C1254
Category: Operational
Title: Resume all mission and business functions
Ownership: Customer
Description: The customer is responsible for resuming all mission and business functions once contingency activities have commenced. Microsoft Azure can support continued system operation during contingency activities if the customer configures Azure appropriately for reserving processing capacity in an alternate region.
Requirements: The customer is responsible for implementing this recommendation.
Mode All
Type BuiltIn
Preview False
Deprecated False
Effect Default
Manual
Allowed
Manual, Disabled
RBAC role(s) none
Rule aliases none
Rule resource types IF (1)
Microsoft.Resources/subscriptions
Compliance
The following 13 compliance controls are associated with this Policy definition 'Resume all mission and business functions' (91a54089-2d69-0f56-62dc-b6371a1671c0)
Control Domain Control Name MetadataId Category Title Owner Requirements Description Info Policy#
FedRAMP_High_R4 CP-2(4) FedRAMP_High_R4_CP-2(4) FedRAMP High CP-2 (4) Contingency Planning Resume All Missions / Business Functions Shared n/a The organization plans for the resumption of all missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of all missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. link 1
ISO27001-2013 A.17.1.1 ISO27001-2013_A.17.1.1 ISO 27001:2013 A.17.1.1 Information Security Aspects Of Business Continuity Management Planning information security continuity Shared n/a The organization shall determine its requirements for information security and the continuity of information security management in adverse situations, e.g. during a crisis or disaster. link 11
ISO27001-2013 A.17.1.2 ISO27001-2013_A.17.1.2 ISO 27001:2013 A.17.1.2 Information Security Aspects Of Business Continuity Management Implementing information security continuity Shared n/a The organization shall establish, document, implement and maintain processes, procedures and controls to ensure the required level of continuity for information security during an adverse situation. link 18
ISO27001-2013 A.17.2.1 ISO27001-2013_A.17.2.1 ISO 27001:2013 A.17.2.1 Information Security Aspects Of Business Continuity Management Availability of information processing facilities Shared n/a Information processing facilities shall be implemented with redundancy sufficient to meet availability requirements. link 17
ISO27001-2013 A.6.1.1 ISO27001-2013_A.6.1.1 ISO 27001:2013 A.6.1.1 Organization of Information Security Information security roles and responsibilities Shared n/a All information security responsibilities shall be clearly defined and allocated. link 73
mp.eq.3 Protection of portable devices mp.eq.3 Protection of portable devices 404 not found n/a n/a 71
mp.eq.4 Other devices connected to the network mp.eq.4 Other devices connected to the network 404 not found n/a n/a 35
mp.info.6 Backups mp.info.6 Backups 404 not found n/a n/a 65
NIST_SP_800-53_R4 CP-2(4) NIST_SP_800-53_R4_CP-2(4) NIST SP 800-53 Rev. 4 CP-2 (4) Contingency Planning Resume All Missions / Business Functions Shared n/a The organization plans for the resumption of all missions and business functions within [Assignment: organization-defined time period] of contingency plan activation. Supplemental Guidance: Organizations may choose to carry out the contingency planning activities in this control enhancement as part of organizational business continuity planning including, for example, as part of business impact analyses. The time period for resumption of all missions/business functions may be dependent on the severity/extent of disruptions to the information system and its supporting infrastructure. Related control: PE-12. link 1
org.1 Security policy org.1 Security policy 404 not found n/a n/a 94
org.4 Authorization process org.4 Authorization process 404 not found n/a n/a 126
SWIFT_CSCF_v2022 10.1 SWIFT_CSCF_v2022_10.1 SWIFT CSCF v2022 10.1 10. Be Ready in case of Major Disaster Business continuity is ensured through a documented plan communicated to the potentially affected parties (service bureau and customers). Shared n/a Business continuity is ensured through a documented plan communicated to the potentially affected parties (service bureau and customers). link 5
SWIFT_CSCF_v2022 8.1 SWIFT_CSCF_v2022_8.1 SWIFT CSCF v2022 8.1 8. Set and Monitor Performance Ensure availability by formally setting and monitoring the objectives to be achieved Shared n/a Ensure availability by formally setting and monitoring the objectives to be achieved link 8
Initiatives usage
Initiative DisplayName Initiative Id Initiative Category State Type
FedRAMP High d5264498-16f4-418a-b659-fa7ef418175f Regulatory Compliance GA BuiltIn
ISO 27001:2013 89c6cddc-1c73-4ac1-b19c-54d1a15a42f2 Regulatory Compliance GA BuiltIn
NIST SP 800-53 Rev. 4 cf25b9c1-bd23-4eb6-bd2c-f4f3ac644a5f Regulatory Compliance GA BuiltIn
Spain ENS 175daf90-21e1-4fec-b745-7b4c909aa94c Regulatory Compliance GA BuiltIn
SWIFT CSP-CSCF v2022 7bc7cd6c-4114-ff31-3cac-59be3157596d Regulatory Compliance GA BuiltIn
History
Date/Time (UTC ymd) (i) Change type Change detail
2022-09-27 16:35:32 change Minor (1.0.0 > 1.1.0)
2022-09-19 17:41:40 add 91a54089-2d69-0f56-62dc-b6371a1671c0
JSON compare
compare mode: version left: version right:
JSON
api-version=2021-06-01
EPAC