AI Control Library / CF-12: Security & Abuse Resistance
Designation: Supplemental | Control types represented: Operational and Technical
Control requirement
Preserve AI security controls during infrastructure migration, including identities, data permissions, network rules, secrets, logging and artifact integrity. Verify the target environment before transferring live authority.
Why this matters
Migrations can create temporary public access, duplicate credentials and forgotten source copies. Functional success does not establish that security properties survived the move.
How the control types work together
Operational controls define scope, authority and the actions required when conditions are not met. Technical controls produce evidence or enforce the relevant boundaries. Both must apply to the same deployment and operating conditions.
When it applies
Apply to cloud moves, region changes, platform replacement and major service transitions. Include rollback environments and temporary transfer infrastructure.
Define the assessed boundary, dependencies and evidence limitations. Tailor depth and review frequency to potential impact, and document why a particular safeguard or exclusion is appropriate to the actual deployment.
Ownership
The migration owner coordinates checks; security approves boundary changes; data and service owners verify transferred assets.
Implementation guidance
- Inventory source assets, controls and target responsibilities.
- Protect transfer paths and verify data and artifact integrity.
- Test target access, isolation, logging and recovery before cutover.
- Retire source access, copies and temporary resources under approved retention rules.
How to verify it
Use representative records and authorized controlled tests. Identify the relevant version, operating conditions and expected result before testing, and retain enough evidence to support the conclusion.
| Test | Expected result |
|---|---|
| Target permission comparison | Required restrictions remain effective. |
| Transferred artifact | Integrity matches the approved source. |
| Source retirement review | Residual accounts and copies are resolved. |
Record a finding when required results cannot be demonstrated or practice differs materially from the approved conditions. Missing evidence limits the conclusion; it should not be treated as a successful test.
Evidence to retain
- Migration plan
- Control comparison
- Cutover approvals
- Retirement evidence
Protect evidence according to its sensitivity, access needs and retention rules. Avoid unnecessary copies of personal information, secrets or confidential material, while preserving the records needed for authorized review.
If the control fails
Pause cutover or use the tested rollback plan, contain exposed target resources and reconcile data and authority before resuming.
Example in practice
Hypothetical example: A model service moves regions. Engineers verify private endpoints and secret access before switching traffic, then remove obsolete credentials from the former deployment.
Related controls
- CF12-S15: AI Infrastructure Network Security
- CF12-S17: AI Production & Non-Production Environment Separation
- CF13-008: Production Model Integrity Monitoring
Framework mappings
- CSA AICM (I&S-07)
- NIST AI RMF (MAP 1.1)
- ISO 42001 (Cl. 8.2)
Review and maintenance
Review at the interval approved by the control owner and after relevant changes, incidents or failed assessments. Update affected procedures and configuration, address evidence gaps and verify corrective action before closing findings.
Back to Security & Abuse Resistance
Version 1.0