AI Control Library / CF-12: Security & Abuse Resistance
Designation: Supplemental | Control types represented: Operational and Technical
Control requirement
Obtain and enforce customer authorization for provider privileged access to customer-controlled AI environments or information when required by the service arrangement. Bind authorization to purpose, scope and duration.
Why this matters
Supplier support can expose customer prompts, data or infrastructure through administrative channels. Customer authorization must be reflected in what support personnel can actually access.
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 managed services, remote support and provider maintenance affecting customer-controlled resources. Define contractual emergency exceptions explicitly.
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 service owner maintains customer commitments; support managers request access; platform teams enforce approved boundaries.
Implementation guidance
- Define access requiring customer consent and agreed emergency conditions.
- Present the requested purpose, resources and time window.
- Enforce customer approval through privileged-access controls.
- Record activity and provide agreed access reporting and revocation.
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 |
|---|---|
| No customer authorization | Covered privileged access is denied. |
| Scope-limited approval | Other customer resources remain inaccessible. |
| Customer revokes consent | Effective access ends within agreed conditions. |
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
- Customer terms
- Authorization records
- Privileged activity logs
- Revocation tests
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
Stop unauthorized support access, inform accountable customer contacts through the agreed process and investigate actual exposure.
Example in practice
Hypothetical example: A provider requests one-hour access to diagnose a retrieval failure. The customer approves the index service only, leaving source-document content inaccessible.
Related controls
- CF12-S07: AI Privileged Access Time Limiting
- CF12-S06: AI Privileged Access Role Segregation
- CF12-S09: AI Audit Log Infrastructure Protection
Framework mappings
- CSA AICM (IAM-11)
- NIST AI RMF (MAP 1.1)
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