AI agent authorization risks remain a gap in new NIST-CISA token security guidance
NIST and CISA release IR 8587 guidance on securing signed tokens, but AI agent authorization and delegation risks remain out of scope.
NIST, with CISA support, published 'Protecting Tokens and Assertions from Forgery, Theft, and Misuse' (NIST IR 8587), recommending continuous monitoring and tighter token lifecycle controls for SSO and API access. The guidance does not yet fully address AI agent identity, delegation chains, or prompt injection steering agents with valid tokens, and NIST says new or expanded standards are needed. Experts recommend treating AI agents as low-trust non-human identities, maintaining agent inventories, expiring credentials after task completion, and requiring human approval for high-risk actions. The report references shared-signal mechanisms like CAEP and RISC, and follows a May incident where a CISA contractor GitHub repository exposed AWS and GitHub tokens.
- NIST IR 8587 covers asymmetrically signed tokens; API keys are explicitly out of scope.
- AI agent authorization gaps require further guidelines and possibly new standards, per NIST.
- Experts advise least-privilege agent identities, agent inventories, and short-lived credentials over static tokens.
- CISA contractor repo exposure in May highlighted token risks outside traditional IAM controls.
- CAEP and RISC shared-signal mechanisms can help respond to token security condition changes.
- Products
- NIST IR 8587
- Organizations
- IDCOmdiaCounterpoint ResearchKanerika
- Countries
- United States
From the original article
4 min read at csoonline.com
AI agents’ actions are out of scope for new guidance from US authorities on securing identity and access tokens, but there is still plenty enterprises can do to protect their systems from rogue humans and AI agents alike.
csoonline.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.