Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Just-in-time access grants a privilege only when it is needed and withdraws it automatically afterwards, so there is no standing administrative right for an attacker to find.

What Is Just-in-Time Access?
Ask an attacker what they are looking for after the first foothold and the honest answer is a list of accounts that already hold the rights they want. Standing privilege is the raw material of lateral movement: it does not need to be created, only found. Just-in-time access attacks that supply directly—nobody holds the privilege by default, and it exists only inside a window that somebody opened deliberately.
The idea is not new. What changed is that the tooling became ordinary: Microsoft Entra Privileged Identity Management, AWS IAM Identity Center session policies, CyberArk and Delinea elevation workflows, HashiCorp Vault dynamic database credentials, and Kubernetes role bindings created and destroyed by a pipeline.
The audit trail that falls out of this is the part most organisations underestimate. You end up with a complete record of every elevation, who approved it, why, and what was done inside the window, which is precisely the evidence an ISO 27001 assessor asks for under Annex A 8.2 and which is almost impossible to reconstruct from a directory of permanent group memberships.
Elevating everything at once. A role that grants global administrator for eight hours after one click has reduced exposure from permanent to eight hours, which is progress, but the activation is doing almost no work. Scope roles narrowly enough that a specific task needs a specific role, then make the high-impact ones require approval.
Leaving the back door open. If the same person retains permanent membership of a group that confers equivalent rights, or holds a local administrator account on the same servers, the elevation workflow is theatre. Map effective permissions before you start, including nested groups, delegated directory permissions, and Active Directory access control entries that nobody has read since 2014.
Ignoring what happens inside the window. An attacker who compromises an eligible account can activate the role themselves. Just-in-time narrows the window; it does not authenticate. Require phishing-resistant multi-factor authentication at activation, alert on activations outside working hours or without a change reference, and monitor the actions taken during the session rather than only the fact of elevation.
No path when the system is down. If the identity platform is unavailable during an incident, nobody can elevate. That is why a small number of break-glass accounts with permanent rights, hardware-key protected, split under dual control, and alerted on every use, remain necessary. Design them deliberately and test them quarterly, as discussed under conditional access policies.
Begin with the roles whose use is genuinely occasional—domain administration, production database access, firewall change rights—rather than with the ones people use hourly. Instrument first: measure how often each privileged role is actually exercised, and you will usually find that most holders use it a handful of times a year, which makes the business case for itself.
Set activation durations from that data rather than from a round number. Allow extension with a second approval instead of a long default. And connect the eligibility list to your access review cycle, because eligibility accumulates exactly as assignment did if nobody prunes it—a hundred people eligible for domain administration is not materially better than a hundred people holding it.
At Privia Security, we test privileged access paths and elevation controls under realistic conditions in our red team services.
Privileged access management is the broader discipline, covering credential vaulting, session brokering, recording, and password rotation for privileged accounts. Just-in-time access is one technique within it, concerned specifically with removing standing privilege by granting rights only for a bounded period. Most mature programmes use both: the vault handles the credential, the workflow handles the timing.
Base it on measurement rather than convention. Instrument how long privileged tasks actually take before you set a policy, then choose a duration that covers the typical case and require a second approval for extension. One to four hours suits most administrative work. Eight-hour defaults tend to mean the privilege is effectively held for the whole working day.
No. An attacker who controls an eligible account can request activation themselves, so the control narrows the window rather than closing it. Pair it with phishing-resistant authentication at activation, approval by a second person for high-impact roles, alerting on unusual activation patterns, and monitoring of the actions performed during the elevated session.
A very small number, yes. If the identity platform or the approval workflow is unavailable during an incident, nobody can elevate, so you need a break-glass path that does not depend on it. Protect those accounts with hardware security keys, split the credentials under dual control, alert on every use, and test them on a schedule.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.