AI Control Library / CF-12: Security & Abuse Resistance
Designation: Supplemental | Control types represented: Operational
Control requirement
Maintain an inventory of human, service, agent and supplier identities with AI access. Record owner, purpose, permissions, environment and lifecycle state so that every active identity is accountable.
Why this matters
Orphaned accounts and forgotten integrations retain access after their original purpose ends. Inventory provides the basis for access review and reliable incident containment.
How the control types work together
Operational controls establish the assigned responsibilities, review processes and response decisions described here. Their effectiveness depends on performing the work and using evidence to guide action, rather than approving a document alone.
When it applies
Apply to application accounts, cloud identities, provider portals, workload identities and delegated integrations. Include temporary and emergency identities.
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 identity owner maintains the inventory; system owners reconcile actual accounts; sponsors justify non-employee access.
Implementation guidance
- Discover identities across AI-related systems and providers.
- Record ownership, purpose, effective access and expiry.
- Reconcile inventory with authoritative employment and service records.
- Investigate orphaned, duplicated and unexpectedly active identities.
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 |
|---|---|
| Active account sample | Owner and purpose are current. |
| Inventory reconciliation | Unknown identities generate findings. |
| Retired service | Its identities are identified for removal. |
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
- Identity inventory
- Reconciliation results
- Ownership attestations
- Cleanup records
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
Disable unjustified identities according to impact, identify their recent activity and assign ownership before reactivation.
Example in practice
Hypothetical example: A provider-console review finds a contractor account with no current sponsor. The owner disables it and checks whether its API keys remain active.
Related controls
- CF12-001: AI Identity & Access Management Policy
- CF12-S04: AI System Access Provisioning
- CF12-S05: AI System Access Revocation
Framework mappings
- CSA AICM (IAM-03)
- 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