Join our Newsletter — 33% off our NHI Course

Does runtime authorization close zero trust's session gap?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20230
Topic starter  

TL;DR: PlainID describes zero trust as still leaving a session gap when access is decided only at sign-in. Runtime authorization moves control to each request, so data access can change when context or behavior changes.

Editorial analysis by NHI Mgmt Group, based on content published by PlainID: “Why Static Access Checks Are Not Enough for Zero Trust Access Control”.

Key questions

Q: Why do valid sessions still create identity risk?

A: Because session validity only proves the account authenticated successfully.

Q: Why do modern Zero Trust programmes need runtime authorization?

A: Zero Trust depends on continuous verification, but verification is incomplete if access decisions are made only at provisioning time.

Q: What should teams do first when zero trust stops at sign-in?

A: First, separate authentication from continuous access enforcement.

Practitioner guidance

  • Define request-time policy for sensitive data Identify the data sets where a valid session should not equal unrestricted access, then express limits using role, sensitivity, time and behaviour.
  • Move enforcement closer to the resource Place policy decision and enforcement where the application, API or data platform can evaluate each request before release.
  • Separate application access from data access Set different rules for opening a system, reading a record and exporting high-value fields so the session cannot inherit blanket trust.

Bottom line: Zero trust fails when the control stack stops at entry and never re-evaluates what a session can do once it is inside the application.

Glossary terms: Zero Trust Architecture (ZTA), ZTNA, Conditional Access, Policy decision point

What's in the full article

PlainID's full blog post covers the operational detail this post intentionally leaves for the source:

  • Survey findings on how many zero trust programmes still omit runtime authorization and where visibility breaks down
  • Policy design examples for row, column and action-level enforcement across applications, APIs and data platforms
  • Implementation detail on extending identity and access decisions into AI agents, gateways and data stores
  • Operational guidance on measuring authorization maturity before and after rollout

👉 Read PlainID's analysis of zero trust access control and runtime authorization →

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →



   
Quote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.