Just-in-time (JIT) privileged access grants elevated access only when someone needs it, for a stated reason and a short, fixed time, and removes it automatically when the time is up. The aim is zero standing privilege, where nobody, human or machine, holds admin rights all the time in case they need them. JIT is the core idea of modern privileged access management (PAM), and it applies to AI agents as much as to administrators, because an agent that holds admin access permanently can use it whenever something steers it to.
Why standing privilege is the problem
A privileged account that is always on can be used at any time by anyone who gets hold of it, whether through a stolen password or an insider. It also hides well in access reviews, since an admin role granted for a project two years ago looks exactly like one granted last week.
JIT changes the default. Elevated access does not exist until it is requested, and it ends on its own, so an attacker who takes over an ordinary account has far less to work with unless a privileged session happens to be open at that moment.
How JIT privileged access works
Most implementations follow the same five steps:
- Request: a person or system asks for a specific privilege on a specific target, with a justification.
- Approve: a policy decides, approving some low-risk requests automatically and sending higher-risk ones to a person.
- Grant for a fixed window, which starts when the request is approved and has a hard end time.
- Use the access, with a log of what was done during the session.
- Expire and clean up: the access is removed when the window ends, and any credential that was exposed is rotated.
JIT models
There are four common ways to implement it:
- Time-limited role or group membership, where the person is added to an admin role for a few hours and removed afterwards.
- Credential checkout, where a privileged credential lives in a vault, is checked out for a set time and is rotated when it comes back.
- Ephemeral accounts, created for the session and deleted at the end.
- Break-glass, an emergency path for when the normal one is unavailable, such as during an SSO outage. It usually needs two people and has a short fixed window.
JIT for AI agents
Agents make the case for JIT stronger. An agent that needs to delete a branch once a month has no reason to hold delete rights for the rest of the month. And because an agent’s behaviour depends on what it reads, a standing privilege can be triggered by a prompt nobody anticipated.
Scope is the first thing that changes. For an agent, a JIT grant should be expressed as an action on a resource, such as deleting branches in one repository for 15 minutes, rather than as a role like repository admin. Windows can also be much shorter than for people, since agents work in seconds; a few minutes is usually enough, and the riskier the action, the shorter the window should be.
Approval should follow risk. Low-risk elevation can be approved automatically, while high-risk elevation should reach a person who can see which agent is asking, for which action and on which resource. The grant also needs to be enforced when the agent makes each call, so that calls inside the window succeed and calls after it are refused.
Before any of that, your team needs a list of the agent credentials that are always on. Each one that stays should become a recorded exception with an owner, a reason and an end date.
Common pitfalls
The most common one is a JIT window that is permanent in practice, such as a 30-day “temporary” grant renewed every month. Another is auto-approval applied to everything, at which point the approval step records intent without controlling anything.
Rotation is easy to skip. A vaulted password that was revealed during a checkout and never rotated afterwards is still usable by whoever saw it. Timing rules cause confusion too, so tell people whether the window counts from the request or from the approval.
Finally, many PAM programs cover human admins but leave out the service accounts and agents that hold the same rights, so those identities keep their standing access.
How to tell whether JIT is working
These questions show whether a JIT program has actually changed anything:
- How much privileged access is standing today, for people, service accounts and agents, and is that going down?
- How many standing exceptions are past their review date?
- What share of elevation requests are approved automatically, and are those the low-risk ones?
- Were credentials rotated after every checkout?
- For any privileged action, can you show who requested the access, who approved it and when it ended?
How AtmanID approaches it
AtmanID’s privileged access features are documented in Privileged access: PAM vault, break-glass and just-in-time access.
For AI agents
An administrator can request a JIT session for an agent with an intent, a resource scope, a risk tier and a TTL in minutes. The TTL is capped at 60 minutes for Low risk, 30 for Medium and 15 for High and Critical. High and Critical requests start as pending and raise a human-in-the-loop approval request, and revoking a session ends it immediately.
The sessions also matter at call time. When the AtmanID gateway holds an agent’s tool call for human approval, a JIT session approved in advance can satisfy that hold (MCP gateway).
For standing access, the ZSP (zero standing privilege) posture view lists standing agent credentials. An exception records a justification, a review-by date and an expiry date, and expired exceptions are flagged for review with the owner notified.
For people
An access request in the catalog can be JIT for 4, 8, 24 or 48 hours. It follows its normal approval workflow and is removed automatically when it expires, with the window counted from submission rather than approval.
Vaulted credentials are checked out for 1, 4, 8 or 24 hours with a business justification, and each reveal of the secret is audited. When the credential is returned or the time runs out, it is flagged for rotation. With dual control on, setting or replacing a credential needs a second administrator’s approval.
During an SSO outage, a break-glass request needs a different administrator to approve it, and the session lasts a fixed four hours.
Every step is recorded in the tamper-evident audit trail, with events such as AGENT_JIT_REQUESTED,
AGENT_JIT_REVOKED, PAM_CHECKOUT and BREAK_GLASS_ACTIVATED
(audit chain). AtmanID does not record SSH or RDP sessions and
has no session proxy, and the docs say so.
FAQ
What is just-in-time privileged access?
It is a way of granting elevated access only when it is needed, for a short fixed period, with a justification and often an approval, and removing it automatically when the period ends. It replaces standing admin rights.
What is JIT PAM?
JIT PAM is privileged access management built around just-in-time access, where privileged credentials and roles are granted on request for a limited time instead of being held permanently. Most modern PAM programs aim for it.
What is zero standing privilege?
Zero standing privilege (ZSP) is the goal that no identity holds privileged access by default, so every elevation is requested and time-bound. In practice organisations get close and track the remaining standing access as exceptions, each with an owner and an end date.
How long should a JIT session last?
As short as the task allows. Hours are typical for human administrators, while for AI agents a few minutes is usually enough, with shorter windows for riskier actions.
Do AI agents need privileged access management?
Yes, if they hold privileged access, and deploy agents or agents that manage users often do. They need what human admins get: no standing privilege, approval for risky actions, short windows and a full record, enforced on every call.
Related: AI agent access control · What is an MCP gateway? · What is a non-human identity?