AI Governance Institute
← News
Standards2026-09-16

NIST IR 8587 Leaves AI Agent Authorization Without a Federal Standard

What happened

NIST, supported by CISA, published IR 8587, a guidance document on securing identity and access tokens that addresses post-authentication controls including token lifecycle management, audience restrictions, and continuous monitoring. The document explicitly carves out AI agent authorization, stating that agentic systems create identity and access management challenges that require dedicated standards not yet developed. That exclusion is significant because enterprise compliance programs have increasingly relied on existing IAM frameworks to justify their agent security posture. In the absence of authoritative guidance, NIST advises teams to treat AI agents as low-trust non-human identities, enforce short-lived credentials, maintain agent inventories, and require human approval for higher-risk actions. This follows a growing pattern of disclosures showing that agent credential and OAuth controls are actively exploited, with standing agent credentials already named as a material control gap.

Why it matters

  • ·Compliance programs that cite existing IAM frameworks to cover AI agent authorization now have an explicit federal acknowledgment that those frameworks do not apply. Teams need to document their interim agent identity controls as operating ahead of guidance, not under it.
  • ·The gap directly implicates non-human identity governance at a time when agent credential abuse is accelerating. Controls such as AGT-009 and AGT-015 that are already in place should be reviewed against NIST's interim recommendations -- short-lived credentials, least-privilege scoping, and agent inventories -- to identify any divergence.
  • ·Regulated industries face compounding pressure: the NIST AI RMF Playbook and sector-specific guidance such as the MAS Guidelines on Artificial Intelligence Risk Management assume coherent IAM foundations that IR 8587 now publicly flags as incomplete for agentic deployments, creating a documented standards gap that auditors and regulators will not overlook.

Stay ahead of stories like this

Get every US AI governance development like this one, plus the rest of the week's developments. Every Thursday.

Free every Thursday. Unsubscribe anytime.

Governance controls affected

What to do now

  • ☐Audit every AI agent deployment to confirm it is registered as a non-human identity with scoped, short-lived credentials rather than standing service accounts.
  • ☐Document the interim agent authorization controls your organization is relying on and explicitly note they are not yet covered by a federal standard, to preserve an audit-defensible rationale.
  • ☐Map your agent inventory against the NIST IR 8587 interim recommendations -- low-trust posture, audience-restricted tokens, and human approval gates for high-risk actions -- and record any gaps.
  • ☐Update your vendor due diligence questionnaire to ask AI agent platform providers how they implement token lifecycle management and whether their controls align with IR 8587 interim guidance.
  • ☐Flag the agent authorization gap to your board or risk committee as an area where enterprise controls are operating ahead of regulatory standards, and set a review trigger for when NIST publishes dedicated agentic IAM guidance.

What to watch next

NIST has acknowledged that dedicated agentic authorization standards are under development, but has not committed to a publication timeline. Compliance teams should monitor the NIST AI program and CISA agentic AI guidance tracks for follow-on documents. The Five Eyes Guidance on the Careful Adoption of Agentic AI Services and the CISA agentic AI guidance are the closest existing authoritative references and should be treated as the interim baseline until IR 8587's agentic companion document appears. Enforcement activity in the EU under the EU AI Act is already scrutinizing agent containment and identity controls, meaning the gap documented in IR 8587 could become an audit finding in regulated markets before NIST closes it.

Related Coverage

Research2026-11-14

One Rogue Employee-Built AI Agent Exposed Five Identity and Control Gaps

Token Security published a case study tracing how a single AI agent created five governance failures. The study draws on a Cloud Security Alliance survey of 418 IT and security professionals. The failures span agent identity, access provisioning, prompt injection, overprivileged static credentials, and behavior-based detection. The findings apply to any enterprise where employees can build agents using no-code or AI-assisted tools.

Corporate Policy2026-11-13

United Airlines Blocks AI Agents Over Credential Risk and Federal Aviation Rules

United Airlines announced it will block AI agents and autonomous assistants from booking flights or managing reservations on customers' behalf. The airline cited credential-sharing risks and potential violations of federal aviation rules, including requirements that a human acknowledge banned substances at check-in. United is updating its booking, ticketing, and distribution policies to cover both its own digital platforms and indirect access through travel agencies and aggregators.

Research2026-11-12

KPMG and Cequence Set Runtime Controls as the Agentic Governance Baseline

Cequence Security and KPMG in Singapore have published a joint report, "Delegating Outcomes, Not Authority: Agentic AI Runtime Security, Governance, and Control." The report argues that static permissions alone are insufficient to govern AI agents. The report recommends runtime controls that evaluate each agent action before it executes, covering least-privilege access, non-human identity, tool-use monitoring, audit trails, and prompt injection defense. Cequence field data from October 2026 tracked more than 281,000 AI agent visits across five industries in a single week.