Access Control & Identity for AI Components & Users · AI Resource Authorization & Classification
Just-in-time access to model weights
Verify that privileged access to model weights, training pipelines, and production AI configuration is granted just in time, with a defined maximum session duration and automatic expiry. Zero Standing Privilege (ZSP) to these resources is encouraged.
OWASP AISVS v1.01, requirement 5.2.6
In plain English
Nobody should hold standing access to model weights, training pipelines or production AI settings. Grant privileged access when it is needed, for a fixed time, and let it expire by itself. An attacker who takes over an engineer's account then finds nothing to use.
What good looks like
- Privileged access is requested for a stated reason, approved and limited in time.
- A maximum session length is defined, and access ends automatically.
- Grants are logged and reviewed.
- The list of people and services with permanent privileged access is close to empty.
How teams usually do it
- Just-in-time access features in your platform, for example Microsoft Entra Privileged Identity Management, temporary elevated access in AWS IAM Identity Center, or tools such as Teleport.
- Approval through a chat or ticket workflow so that asking is quick. If it is slow, people will keep standing access.
- Break-glass accounts for emergencies, sealed, monitored and tested.
Suggested evidence
- Access request and approval records.
- The configured maximum session length.
- The current list of standing privileged permissions.
Common mistakes
- Break-glass accounts that are used every week.
- Just-in-time access for people while pipelines and service accounts keep permanent admin rights.
- Sessions that last a week because the default was never changed.
Not sure which requirements apply to your system? Take the assessment, or browse every guide in this chapter.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.