Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Just-in-Time Access?

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.

Illustration for the cybersecurity term Just-in-Time Access
Home / Blog / Cybersecurity Terms / What Is Just-in-Time Access?
17 November 2026

What Is Just-in-Time Access?

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.

How an Elevation Actually Runs

  1. A user is eligible for a role rather than assigned to it. Eligibility is a durable state; assignment is not.
  2. They request activation, give a reason, and reference a change or incident number.
  3. Policy decides what happens: automatic approval with notification for routine roles, a second person’s approval for sensitive ones, a stronger authentication prompt, or a conditional access check for a compliant device.
  4. The role is assigned for a bounded period, typically one to eight hours.
  5. Expiry removes it. Not a reminder to remove it—removal.

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.

Three Patterns, Not One

Where Deployments Go Wrong

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.

Getting Started Without a Revolt

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.

FAQ – Frequently Asked Questions

How Is Just-in-Time Access Different From Privileged Access Management?

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.

What Activation Duration Should We Set?

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.

Does Just-in-Time Access Stop a Compromised Account?

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.

Do We Still Need Permanent Administrator Accounts?

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.

Related Terms

You May Be Interested In These

What Is Responder?

Cybersecurity Terms

17 November 2026

What Is Responder?

Read More
What Is a Man-in-the-Browser Attack?

Cybersecurity Terms

17 November 2026

What Is a Man-in-the-Browser Attack?

Read More
What Are HART and WirelessHART?

Cybersecurity Terms

17 November 2026

What Are HART and WirelessHART?

Read More