AzPolicyAdvertizer

last sync: 2024-Jul-26 18:17:39 UTC

Microsoft Managed Control 1296 - Information System Recovery And Reconstitution | Transaction Recovery | Regulatory Compliance - Contingency Planning

Azure BuiltIn Policy definition

Source Azure Portal
Display name Microsoft Managed Control 1296 - Information System Recovery And Reconstitution | Transaction Recovery
Id e57b98a0-a011-4956-a79d-5d17ed8b8e48
Version 1.0.0
Details on versioning
Category Regulatory Compliance
Microsoft Learn
Description Microsoft implements this Contingency Planning control
Additional metadata Name/Id: ACF1296 / Microsoft Managed Control 1296
Category: Contingency Planning
Title: Information System Recovery And Reconstitution | Transaction Recovery
Ownership: Customer, Microsoft
Description: The information system implements transaction recovery for systems that are transaction-based.
Requirements: Currently there are no transaction-based systems in the Azure environment. The primary and alternate sites are operational, management, and technical mirrors. Therefore, the need to recover and reconstitute information systems during significant contingency events is eliminated. Instead of using transaction journaling, Azure uses live replicated databases. MySQL uses transaction journaling while Microsoft SQL uses transaction logs. Transaction logging is a core function of the SQL engine and cannot be disabled. Common practice at Microsoft is replicate the transaction log to multiple assets and replay them to keep hot standby secondary databases on those assets up to date. This mechanism is referred to as Always On. Always On maintains multiple copies of a single database that reside on different server instances in different locations. One server instance serves the database to clients (the primary server). The other instance acts as a hot or warm standby server. In the event of a disaster, a failover quickly brings the standby copy of the database online (without data loss). For an Overview of SQL Server Always On, please refer to Therefore, this is an alternative to transaction journaling because it provides the means to provide support for contingency events. Also, per Microsoft "10.01 Business Continuity Management Standard", transaction recovery plans are required and managed by the different business groups to ensure the continuation of business processes in the event of an interruption.
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
The following 4 compliance controls are associated with this Policy definition 'Microsoft Managed Control 1296 - Information System Recovery And Reconstitution | Transaction Recovery' (e57b98a0-a011-4956-a79d-5d17ed8b8e48)
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
JSON
api-version=2021-06-01
EPAC