AI Governance Institute logo
AI Governance Institute

Practical Governance for Enterprise AI

Security
SEC · SecuritySEC-002Medium effortAgent-relevant

AI System Access Controls

Apply authentication, authorization, and role-based access controls to AI systems, APIs, and the sensitive data they process.

Objective

Ensure that only authorized users and systems can interact with AI capabilities, and that access is scoped to what each role requires.

Maturity Levels

1

Initial

AI systems are accessible to all employees with no role-based restrictions.

2

Developing

Basic authentication exists but authorization is coarse-grained and not regularly reviewed.

3

Defined

Role-based access controls are defined, documented, and enforced for all AI systems and APIs.

4

Managed

Access is reviewed quarterly; provisioning and de-provisioning are tied to HR processes.

5

Optimizing

Access is dynamically adjusted based on context and risk level; anomalous access patterns trigger automated alerts.

Evidence Requirements

What an auditor or assessor would expect to see for this control.

  • RBAC matrix documenting roles, access levels, and authentication methods for all AI systems and APIs
  • Access provisioning records confirming formal approval was obtained before access was granted
  • Quarterly access review records showing active accounts were verified and unused access was revoked
  • De-provisioning confirmation records for departing employees, completed within the defined timeframe
  • Access logs showing system usage by identity for anomaly detection and misuse investigation

Implementation Notes

Key steps

  • Treat AI system APIs as sensitive infrastructure — require API key management, rotation schedules, and usage auditing just as you would for financial or HR systems.
  • Implement separate access tiers for model invocation, training data, output logs, and admin functions.
  • Ensure AI system de-provisioning is part of your offboarding process — departing employees with AI API keys are a frequent oversight.
  • Log all access with sufficient context to detect misuse: user identity, timestamp, inputs provided, and outputs returned.

Example Implementation

Enterprise SaaS company with three AI-powered product features and an internal analytics assistant

AI System Access Control Matrix

SystemUser RoleAccess LevelAuth MethodReview Cadence
Customer SummarizerAccount ManagerInvoke (own accounts only)SSO + RBACQuarterly
Customer SummarizerAdminInvoke (all accounts) + view logsSSO + RBACQuarterly
Fraud Detection APIRisk AnalystQuery (read results)API key per userQuarterly
Fraud Detection APIEngineerInvoke + configureAPI key + MFAQuarterly
Internal Analytics AssistantAll employeesInvoke (own data only)SSOAnnual
Model training pipelinesML EngineerRead/writeShort-lived token via CI/CDPer deployment

De-provisioning: AI system access is included in offboarding checklist; access revoked within 24 hours of departure

Unused access: Accounts with no AI system activity in 90 days flagged for review and de-provisioning

Control Details

Control ID
SEC-002
Domain
Security
Typical owner
CISO / IT
Implementation effort
Medium effort
Agent-relevant
Yes

Tags

access controlauthenticationauthorizationRBAC