AI Control Library / CF-12: Security & Abuse Resistance
Designation: Supplemental | Control types represented: Operational and Technical
Control requirement
Segregate privileged AI roles from routine user roles and separate sensitive administrative capabilities according to duty. Require deliberate activation and accountability for elevated activity.
Why this matters
Everyday use of administrative accounts expands the effect of phishing, mistakes and prompt-driven actions. One unrestricted administrator role can also undermine independent oversight.
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 model administration, infrastructure, identity management, sensitive data management and audit 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 privileged-access owner defines roles; system owners assign duties; independent reviewers examine elevated activity.
Implementation guidance
- Define distinct privileged roles and prohibited combinations.
- Use separate administrative identities or controlled elevation.
- Restrict privileged access channels and administrative tools.
- Review role assignments and actual elevated operations.
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 |
|---|---|
| Routine session | Administrative functions are unavailable. |
| Conflicting privileged roles | Assignment is blocked or formally reviewed. |
| Elevated operation | Actor and approved purpose are traceable. |
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
- Privileged role matrix
- Assignments
- Elevation records
- Activity 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
Remove conflicting or excessive roles and investigate privileged operations performed without appropriate separation.
Example in practice
Hypothetical example: A model registry administrator can manage releases but cannot erase security logs. Daily testing uses an ordinary account with no release permissions.
Related controls
- CF12-S03: AI System Separation of Duties
- CF12-S07: AI Privileged Access Time Limiting
- CF12-S09: AI Audit Log Infrastructure Protection
Framework mappings
- CSA AICM (IAM-09)
- 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