AI Control Library / CF-12: Security & Abuse Resistance
Designation: Supplemental | Control types represented: Operational and Technical
Control requirement
Limit privileged AI access to an approved duration and purpose, with automatic expiry and verification that sessions and issued credentials lose authority when the window closes.
Why this matters
Standing administrative access increases exposure long after a maintenance task ends. Expiry that removes a role but leaves a privileged session active provides incomplete protection.
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 human administrators, supplier support and elevated automation. Define controlled emergency access where normal approval is unavailable.
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 privileged-access owner operates elevation; resource owners approve duration and scope; security reviews exceptions.
Implementation guidance
- Define approved elevation purposes, maximum durations and approvers.
- Issue temporary roles or credentials for the specific task.
- Revoke effective authority at expiry, including active sessions where required.
- Review renewals, emergency use and failed expiry checks.
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 |
|---|---|
| Elevation period ends | Privileged operations are denied. |
| Renewal request | Continuing need and approval are verified. |
| Emergency elevation | Use is logged and independently reviewed. |
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
- Elevation requests
- Expiry configuration
- Session tests
- Emergency reviews
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
Terminate residual privileged sessions, revoke affected credentials and correct the expiry mechanism before further elevation.
Example in practice
Hypothetical example: An engineer receives thirty minutes of production access for diagnosis. After expiry, the same session can no longer change serving configuration.
Related controls
- CF12-S06: AI Privileged Access Role Segregation
- CF12-S08: Customer Authorization for AI Privileged Access
- CF12-S05: AI System Access Revocation
Framework mappings
- CSA AICM (IAM-10)
- 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