feat(C5): add just-in-time access provisioning control for AI resources (5.2.9)#625
Open
RicoKomenda wants to merge 1 commit intoOWASP:mainfrom
Open
feat(C5): add just-in-time access provisioning control for AI resources (5.2.9)#625RicoKomenda wants to merge 1 commit intoOWASP:mainfrom
RicoKomenda wants to merge 1 commit intoOWASP:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds 5.2.9 to C5.2 (Authorization & Policy) to address a gap identified during OASB cross-referencing and review of NIST SP 800-207 (Zero Trust) and NIST AI RMF guidance.
New control:
Level: 2
Why this is needed
Existing controls (5.2.1, 5.2.2) cover RBAC/ABAC policy and logging of access modifications, but do not require JIT provisioning or prohibit permanent standing access. Permanent standing access to model weights and training pipelines is a significant attack surface: a compromised account with standing access can silently exfiltrate weights, inject poisoned training data, or alter production configuration without any time-bounded detection window.
JIT access is well-supported by PAM tooling (HashiCorp Vault, CyberArk, AWS IAM Identity Center temporary roles, Azure PIM) and is verifiable through access log inspection. This is AI-specific because model weights and training pipelines are the critical assets in an AI system that do not have a direct equivalent in a general web application.
Changes
1.0/en/0x10-C05-Access-Control-and-Identity.md: add 5.2.9, fix MD060 separator rows1.0/en/0x93-Appendix-D_AI_Security_Controls_Inventory.md: add entry to AD.2