Notifications
Clear all
Topic starter
25/06/2026 3:13 pm
TL;DR: Always-on admin access keeps standing privilege alive long after a task ends, expanding attack and audit risk, according to SecurEnds. Just in time access narrows that exposure window, but the real security gain comes from replacing persistent entitlement with tightly governed, task-scoped elevation.
NHIMG editorial — based on content published by SecurEnds: just in time access and privileged access management
By the numbers:
Questions worth separating out
Q: What breaks when admin access is not time-bound?
A: When admin access is not time-bound, privilege becomes easy to abuse, hard to audit, and difficult to justify.
Q: Why do privileged accounts increase breach impact in cloud environments?
A: Privileged accounts increase breach impact because they allow attackers or insiders to move from one foothold to many high-value systems quickly.
Q: How do security teams know if JIT access is actually working?
A: JIT access is working when elevated access is rare, time-limited, approved for clear reasons, and consistently removed without manual intervention.
Practitioner guidance
- Inventory standing admin rights across human and machine-operated paths Identify every account that retains elevated access by default, including break-glass, contractor, and cloud administration roles.
- Convert permanent elevation into task-scoped approval flows Require a specific request reason, linked ticket, approver, and expiry condition before rights are granted.
- Enforce automatic revocation after the access window closes Make expiry deterministic and system-driven so no one has to remember to clean up access manually.
What's in the full article
SecurEnds's full blog covers the operational detail this post intentionally leaves for the source:
- Step-by-step explanations of how its policy-triggered access flow is configured in practice
- Examples of how JIT interacts with Active Directory, Azure, AWS IAM, and existing PAM tooling
- The article's audit and reporting output for proving revocation, approval, and access duration
- Use cases for patching, cloud DevOps bursts, and contractor onboarding
👉 Read SecurEnds' full guide on just in time privileged access management →
Just in time access: is your admin privilege model still too open?
Explore further
25/06/2026 4:37 pm
Just in time access is a control over privilege duration, not a replacement for governance. The model reduces the time window in which privileged credentials exist, but it does not by itself solve role design, approval quality, or offboarding. If the underlying entitlement model is already bloated, JIT only narrows the exposure window around a bad structure. Practitioners should treat it as a governance mechanism that forces privilege to be earned at the moment of use.
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 access governance often starts from partial inventory rather than reliable control, according to NHI Mgmt Group research.
A question worth separating out:
Q: Who should approve just in time access requests?
A: Approval should sit with someone who can validate business need and risk, usually a manager, system owner, or delegated control point defined by policy. The important issue is not the job title alone, but whether the approver can meaningfully confirm scope, urgency, and expiry before access is granted.
👉 Read our full editorial: Just in time access reduces admin blast radius in modern PAM
