Topic starter
23/03/2026 3:42 pm
TL;DR: Workflow-based JIT access can stall users for minutes to days and encourage approval fatigue, while static pre-approval rules can widen the attack surface when an identity is compromised, according to Andromeda Security. The real governance issue is that access decisions need context, not just a ticket and an inbox.
Editorial analysis by NHI Mgmt Group, based on content published by Andromeda Security: “Beyond the Workflow: Moving to Context-Driven JIT Access”.
Key questions
Q: What breaks when JIT access is based on static approval rules?
A: Static approval rules break the core promise of JIT because they stop evaluating the request at the moment of use.
Q: Why does workflow-based privileged access create approval fatigue?
A: Workflow-based privileged access creates approval fatigue because approvers are asked to make decisions with too little context and too many routine notifications.
Q: How should PAM teams evaluate context before granting JIT access?
A: PAM teams should evaluate the request against runtime signals such as device trust, geo, business criticality, on-call status, ticket state, request frequency, and role sensitivity.
Practitioner guidance
- Audit approval latency and rubber-stamp behaviour Review how long privileged requests wait, how often approvers rely on thin request text, and where decisions are being made without enough business context to justify the grant.
- Replace static pre-approval with context checks Limit rule-based grants to narrow, well-understood scenarios and require runtime evaluation for location, device, ticket state, business criticality, and usage pattern.
- Route outlier requests to informed human review Reserve manual approval for requests that fail contextual thresholds, and provide the approver with the specific signals that caused the request to be flagged.
Bottom line: Workflow-based JIT can reduce standing access, but it still fails if the approval process cannot evaluate the request in context.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 5 days ago by NHI Mgmt Group
06/10/2026 8:43 pm
Workflow-based JIT is a queue management model, not a security decision model. When access decisions depend on who can respond to an inbox fastest, the programme is optimising approval throughput rather than trust conditions. That collapses the distinction between administrative convenience and privilege governance. Practitioners should treat long approval latency as evidence that the control is operating as paperwork, not as contextual authorisation.
A few things that frame the scale:
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: When does temporary access become a standing-risk problem?
A: Temporary access becomes a standing-risk problem when the approval rule stays broad enough that a compromised identity can reuse it repeatedly. If the same policy grants access to many resources or many users without fresh context, the attacker does not need persistence inside the workflow. They only need one successful request path.
👉 Read our full editorial: Context-driven JIT access exposes the limits of workflow-based PAM