Skip to content
Okta vs Entra

Reviewed 10 November 2026

Okta and Entra ID against NIST's ten agent identity tenets

Reviewed 2026-11-10 · Editorial assessment by the editors

By the editors. Published 2026-11-10. 5 min read. Tags: AI agents, Standards, Okta, Microsoft Entra.

NIST's ten agent identity tenets are design guideposts, not a product certification. Okta publishes a direct mapping with explicit roadmap items. Microsoft's sourced material documents agent identities, sponsorship and token controls, but does not state every tenet. Treat missing detail as not stated, not as proof that a control is absent.

Read the tenets as design guidance

NIST published Design Tenets for Agent Identity Management Systems on 27 October 2026. It proposes an initial set of ten tenets and says they will guide agentic demonstrations at the NCCoE. That framing matters: a vendor mapping is an explanation of product direction, not a NIST certification or a finding that every deployment meets the design.

Industrial Cyber's account provides detail about cryptographic linking, constrained delegation, deterministic access decisions and evidence. NIST also cautions that current standards and technologies may not support every tenet. Several controls may be needed against one threat. A useful comparison therefore preserves the gaps instead of compressing the tenets into a single pass or fail.

The agent identity comparison covers the broader product scope. This narrower reading asks what the cited material actually establishes for each tenet. The list distinguishes direct statements from nearby capabilities that still need technical evidence.

Compare all ten source statements

  • 01 Distinct Agent Identification. Okta states an agent identity mapping in its NIST checklist. Microsoft states agents have their own identities, service principals and OAuth flows. Full evidence of cryptographically verifiable identities distinct from service accounts: not stated in the summarized product material for either vendor.
  • 02 Agent Linking, Delegation & Attenuation. Okta maps its product to this tenet. Microsoft states agent identities have owners and sponsors. Cryptographic linking to the task initiator and attenuation across delegation chains: not stated in the available source detail for either vendor.
  • 03 Least & Zero Standing Privilege. Okta states its gateway injects credentials at call time so the agent never holds them. Microsoft states agent OAuth flows; a short-lived-by-default model is not stated. Complete zero standing privilege while idle: not stated in the cited detail for either vendor.
  • 04 Short-Lived, Dynamic & Revocable Authorization. Okta states call-time credential injection and describes runtime gateway enforcement. Microsoft states Conditional Access at sign-in and token issuance. Audience-specific, time-bounded verification of every tool invocation: not stated for Microsoft; full tenet coverage is not established for Okta by credential injection alone.
  • 05 Human-in-the-Loop Triggers. Okta states Human-in-the-Loop for AI Agents is a roadmap feature. Microsoft states owners and sponsors. A risk-triggered human approval mechanism for individual tool calls is not stated in the Microsoft sources used here.
  • 06 Mandates and Constraints. Okta states task-level intent, including rich authorization requests and transaction tokens, is on its roadmap. Microsoft's sourced material does not state cryptographically signed task mandates. A current implementation satisfying the full mandate requirement is not stated for either vendor here.
  • 07 Architectural Separation of Policy from Reasoning. Okta describes Agent Gateway between the agent and tool call, enforcing policy. Microsoft describes identity and token controls. A separate per-tool-call policy enforcement architecture is not stated in the Microsoft material; a complete NIST conformance finding is not stated for either vendor.
  • 08 Deterministic Access Decisions. Okta describes policy enforcement at its gateway. Microsoft describes Conditional Access at sign-in and token issuance. A detailed account establishing deterministic decisions across all agent tool calls, rather than probabilistic decisions, is not stated in these summarized sources for either vendor.
  • 09 Continuous Monitoring. Okta states its System Log records agent token exchanges, configuration changes and authorization decisions. Microsoft introduces Project Perception with shared signals, context and a unified registry with Agent 365. Specific agent metrics and thresholds satisfying this tenet are not stated in the cited detail.
  • 10 Immutable Evidence. Okta states the System Log records agent events. Microsoft describes shared signals and registry context. Tamper-evident, append-only records kept outside agent control are not stated in the source detail used here for either vendor. Logging alone does not establish the full evidence requirement.

Keep roadmap claims visible

Okta's checklist is unusually useful because it names unfinished work. Its human review and task-intent statements should remain attached to any discussion of those tenets. The September release describes Agent Gateway as planned for general availability in Q3 and expanded runtime Kill Switch capabilities in Q4. The release does not state whether these are fiscal or calendar quarters.

Microsoft's 19 October announcement expands the identity patterns discussed to include local agents and previously unknown agents discovered through security sensors. It introduces Project Perception, Playbooks and Guardian Agents. Microsoft gives no availability dates for those additions. They update the discovery and context discussion, but do not establish unstated approval or immutable-evidence mechanisms.

Ask for evidence at the tool boundary

For an evaluation, choose a task with a known initiator, a permitted tool operation and a prohibited operation. Ask the supplier to show identity, delegation scope, the access decision and the resulting record. Repeat the exercise after changing the request. This is a proposed test method, not a claim that either vendor already passes it.

The agent governance comparison separates identity from action controls. NewCore's announcements describe task-scoped credentials, runtime policy on every tool call, human approval and revocation. Those are relevant claims to examine alongside the tenets, not grounds for awarding it NIST certification. It is an agent governance layer alongside the identity provider already in use.

Record unknowns without treating them as failures

Keep a written evidence register for each tenet: source statement, release status, demonstrated behavior and unresolved questions. Use not stated when the material is silent. Use roadmap when the vendor says roadmap. Neither label should silently become unavailable, and neither should become implemented because a nearby capability sounds similar.

The guide to governance alongside an identity provider explains the responsibility split. For this assessment, the important output is a bounded statement about one control in one workflow. A successful login does not answer all ten tenets, and a vendor checklist does not remove the need to examine the actual decision path.

Frequently asked questions

Does NIST certify these products?

The cited NIST post proposes initial design tenets as guideposts for demonstrations. It does not provide a product certification here. A vendor mapping can help structure an assessment, but it does not establish that a deployment satisfies every tenet.

Does not stated mean unsupported?

No. It means the cited material does not establish the specific control. Ask for documentation and a demonstration before deciding that a feature is present or absent. Keep this separate from roadmap wording, which is an explicit statement about planned work.

Does an owner satisfy human review?

A named owner establishes accountability for an agent. Human review additionally requires a trigger, a decision process and enforcement of the result for an action. Microsoft's owner and sponsor statements alone do not establish those action-level approval details.