AI systems with separate access rights are given a named identity, and these rights are limited to a documented scope.
Trigger
The organization has deployed AI systems (agents, scripts or automations) that access systems or data with their own credentials (such as service accounts, API keys or app registrations).
Why
Non-human identities, and identity more broadly, are a significant and increasing part of an organization's digital attack surface. AI systems' access rights should be scrutinized and reviewed at least as much as those of human accounts. With no documented scope, the access cannot be reviewed or reduced.
How
AI systems using their own credentials should be given a dedicated identity, separate from any human account. The scope of the AI system's credentials should be documented (which systems and data it can reach, and whether it can read or write). These identities should be managed through the organization's existing identity and access management processes (see AC.4).
Sources
- No equivalent in NIST AI RMF, ISO/IEC 42001 or the EU AI Act.