AI Control Library / CF-01: Lifecycle Governance
Designation: Supplemental | Control types represented: Operational and Technical
Major disruption can remove the systems, staff or credentials that normal recovery assumes. The plan must establish a trusted environment and approved baseline before restarting consequential activity.
Control requirement
Maintain a disaster response plan for restoring disrupted AI services and dependencies when ordinary recovery is insufficient. Define activation authority, recovery order, required resources, data reconciliation and criteria for safe return to service.
Why this matters
The control is effective when its required decisions and safeguards can be demonstrated in the actual workflow. An approved document or completed form alone is insufficient if the described actions are not performed.
How the control types work together
Operational controls define the process and decision authority; Technical controls enforce boundaries or produce the system evidence needed to verify it.
When it applies
Severe service, site, infrastructure or provider failures affecting AI, coordinated with business continuity and security incident response.
Tailor depth and review frequency to potential impact, system authority and uncertainty. Document the reason for any exclusion; a supplemental designation does not make an otherwise applicable safeguard optional.
Ownership
The disaster response lead coordinates recovery; system, security and business owners approve restored components and service resumption.
Implementation guidance
- Define disaster activation criteria and authority, separating technical recovery decisions from business prioritization.
- Map recovery dependencies and a feasible sequence for identity, infrastructure, data, models, integrations and monitoring.
- Specify trusted recovery artifacts, alternative resources, access routes and coordination with suppliers; address compromised backups or environments.
- Verify restored data, permissions, model behavior and monitoring; reconcile incomplete transactions and obtain return-to-service approval.
How to verify it
Use a representative sample of actual records or an authorized controlled exercise. A reviewer with suitable expertise should compare observed practice with the approved scope and acceptance criteria.
| Test | Expected result |
|---|---|
| Exercise the restoration sequence | Dependencies are available when each recovery step needs them. |
| Assume the original environment is untrusted | Recovery uses verified artifacts and appropriate identity controls. |
| Assess service readiness | Quality, security and business checks precede consequential resumption. |
Record a finding when a required result is absent, evidence cannot substantiate the claim, or practice differs materially from the approved conditions. An exception may record accepted risk, but does not turn a failed safeguard into an effective one.
Evidence to retain
- Disaster plan and dependency order
- Recovery resource and access records
- Trusted-baseline and restoration evidence
- Return-to-service decisions
Protect evidence according to its sensitivity and approved retention requirements. Retain enough detail to substantiate the assessment without unnecessarily duplicating confidential or personal information.
If the control fails
Escalate unavailable dependencies or unsafe restored behavior to the response lead and business owner. Maintain reduced service or suspension rather than bypassing trust and acceptance checks.
Example in practice
Hypothetical example: After an infrastructure compromise, an agent platform is rebuilt from verified artifacts. Its tool credentials are replaced and actions remain blocked until restored permissions and behavior pass the recovery checks.
Related controls
Framework mappings
- CSA AICM (BCR-09)
- NIST AI RMF (MANAGE 4.1)
- ISO 42001 (Cl. 8.2)
Review and maintenance
Review at the interval approved by the control owner and after a material change, relevant incident or failed assessment. Reassess the affected scope, update records and verify corrective actions before closing findings.
Version 1.0