Notifications
Clear all
Topic starter
25/06/2026 1:08 am
TL;DR: Identity-only access models still leave overprivileged accounts, manual approvals, and weak device or session checks exposed to misuse, according to Apono’s analysis of context-aware access control. Static identity signals are no longer enough to govern JIT, JEP, and privileged access in cloud-native environments, where environment and intent now shape the real security decision.
NHIMG editorial — based on content published by Apono: Identity Is NOT the New Perimeter, Context Is (Just Ask Security Vendors)
By the numbers:
- 92% of organisations expose NHIs to third parties, raising concerns about supply chain security.
Questions worth separating out
Q: How should security teams implement context-aware access for privileged users?
A: Start by treating identity as only one input to authorisation.
Q: Why do identity-only access models fail in cloud-native environments?
A: They fail because cloud-native work is dynamic while identity-based policy is usually static.
Q: What breaks when JIT access is not tied to context?
A: JIT becomes a time limit on standing privilege instead of a genuine risk control.
Practitioner guidance
- Map access decisions to runtime context Review which privileged paths still rely only on identity, then add device health, location, resource sensitivity, and behavioural baseline into the decision policy for those paths.
- Bind JIT approvals to session context Require contextual signals before issuing temporary elevation, including managed device status, approved change window, and the risk level of the target system.
- Narrow JEP by task and posture Define the minimum privilege for the task, then condition that privilege on where the user or workflow is operating and whether the environment is trusted.
What's in the full article
Apono's full article covers the operational detail this post intentionally leaves for the source:
- Specific contextual signals used in its access decision model, including device identity and workload/task context
- Examples of how JIT and JEP workflows are applied in practice to reduce standing privilege
- The EverC access control case study and the operational outcomes it achieved
- The vendor's implementation framing for security teams evaluating contextual authorisation
👉 Read Apono's analysis of context-aware access and JIT privilege control →
Context-aware access controls: what IAM teams need to change?
Explore further
25/06/2026 10:20 am
Identity-only access governance is already too coarse for cloud-native privilege decisions. Identity proves who authenticated, but it does not prove whether the request should be allowed in that session, from that device, for that resource, at that time. That is why static role assignment and manual approvals leave exposed gaps even when authentication is strong. Practitioners should treat context as part of authorisation, not an optional enhancement.
A few things that frame the scale:
- 91.6% of secrets remain valid five days after the targeted organisation is notified, showing a critical gap in remediation procedures, according to Ultimate Guide to NHIs.
- Only 5.7% of organisations have full visibility into their service accounts, which means most access decisions are still made without complete identity inventory.
A question worth separating out:
Q: Who is accountable when a valid session is abused after login?
A: Accountability sits with the identity and access programme that allowed identity to be the only decision signal. When a valid session is abused, the issue is usually not failed authentication but insufficient contextual gating at authorisation time. That is why privileged access policy, not login success, is the control boundary that matters.
👉 Read our full editorial: Context-aware access is replacing identity-only perimeter thinking
