How to meet it
OWASP AISVS v1.01
Access Control & Identity for AI Components & Users · Authentication
Step-up sign-in for high-risk operations
Verify that high-risk AI operations (model deployment, weight export, training data access, production configuration changes) require step-up authentication.
OWASP AISVS v1.01, requirement 5.1.1
In plain English
Ask for a second, stronger proof of identity before someone deploys a model, exports weights, reads training data or changes production AI settings.
What good looks like
- The list of high-risk operations is written down.
- Each one requires fresh multi-factor authentication at the time of the action.
- Step-up events are logged with who, what and when.
How teams usually do it
- Conditional access policies in your identity provider that require re-authentication for named actions.
- Approval steps in the deployment pipeline that require a hardware key.
Evidence an auditor would accept
- Identity provider policies for the listed operations.
- Log entries showing step-up for recent deployments.
Common mistakes
- Relying on a login from that morning for a weight export in the afternoon.
- Protecting the console while the same action is possible through an API token with no step-up.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.