Notifications
Clear all
Topic starter
10/06/2026 11:07 pm
TL;DR: Modern infrastructure increasingly issues valid credentials that outlive the runtime context they were meant to protect, making possession-based trust too weak for workload security, according to Riptides. The decisive gap is not token validity but whether the current actor is still legitimate at the moment access is used.
NHIMG editorial — based on content published by Riptides: Bearer Token Meets Runtime Enforcement
Questions worth separating out
Q: How should security teams handle bearer tokens that remain valid outside their original context?
A: Treat token validity as necessary but not sufficient.
Q: Why do workload identities create new risk when used across clouds and APIs?
A: Because workload identities are transferable, their trust value can outlive the runtime conditions that made them safe.
Q: What breaks when authorisation depends only on a valid credential?
A: The system stops distinguishing between the legitimate workload that first obtained the token and any later actor that reuses it.
Practitioner guidance
- Separate issuance from runtime authorisation Map where your current controls only confirm that a credential was issued correctly and where they also validate the live workload at connection time.
- Inventory trust-extension points in federated flows Identify where identity crosses cloud, cluster, or organizational boundaries without a second runtime check.
What's in the full article
Riptides' full post covers the operational detail this post intentionally leaves for the source:
- How runtime-bound enforcement is attached to the process and network boundary in practice
- Why adjacent policy engines and proxies can still fall short of validating the live actor
- The architectural difference between token validation and runtime legitimacy checks
- How the source positions workload access management against traditional possession-based trust
👉 Read Riptides' analysis of bearer tokens and runtime enforcement in workload security →
Bearer tokens and runtime enforcement: are your controls keeping up?
Explore further
12/06/2026 4:56 am
Possession-based trust is no longer a safe authorisation premise for modern workload identity. A valid credential proves that authentication succeeded earlier, not that the current actor should still be trusted now. That premise was designed for slower, more static environments. It fails when credentials are transferable, workloads are ephemeral, and runtime state changes faster than the trust decision.
A few things that frame the scale:
- 59.8% of organisations see value in a solution that simplifies non-human access management and introduces dynamic ephemeral credentials, according to The 2024 Non-Human Identity Security Report.
- 88.5% of organisations acknowledge that their non-human IAM practices lag behind or are merely on par with their human identity and access management efforts, according to The 2024 Non-Human Identity Security Report.
A question worth separating out:
Q: How can teams reduce the risk of replayed bearer tokens in federated environments?
A: Use runtime enforcement that checks the current workload at the point of connection, then limit how far trust is extended across boundaries. Teams should also review where identity propagation depends on portable artefacts alone. The goal is to stop treating a previously valid credential as permanent proof of access.
👉 Read our full editorial: Bearer tokens need runtime enforcement in modern workload security
