Convert Standing Admin Access to Just-in-Time Access

Required License: This playbook requires a license that includes both JIT and on-demand least-privilege recommendations. The JIT license alone does not include least-privilege recommendations.

Objective
A user with standing admin access is a permanent target. If their credentials leak, the attacker gets admin, any time of day. This playbook shows you how to measure what the user actually does with that access, build a JIT eligibility that grants exactly that on request, and then remove the standing assignment.

Run it for one user at a time. Start with a user whose admin access shows up as a Critical permission severity on the Excessive Permissions page.

Prerequisites

Before you begin:

  • Ensure you have the Administrator role in Tenable One Cloud Exposure. Generating least-privilege policies requires Collaborator or Administrator. Adding eligibilities requires Administrator or JIT Administrator.
  • Ensure you granted Tenable JIT permissions for the relevant cloud provider.
  • Ensure the user can log in to the JIT Portal via SSO.
    • AWS: Because JIT for AWS only grants access to Identity Center users and groups, confirm the user is an IAM Identity Center user. If the standing admin is an IAM user, move the user to Identity Center before you start.
Caution: Do not remove the standing assignment until you confirm the JIT eligibility works. Revoking first locks the user out of work they still need to do.

Step 1: Determine Usage

Cloud Exposure marks a permission as excessive if it was not used during the Permission Usage Learning Period (90 days by default). The usage data behind that calculation is what you base the JIT permissions on.

To review a user's usage:

  1. In the Cloud Exposure Console, navigate to Risks > Excessive Permissions.
  2. Filter the table for the relevant user, and review the Services and Resources columns. These show how many services and resources the user can access but has not used.
  3. Drill down into the user to see the used and unused permissions, and the permission mapping.
  4. Write down any task the user runs less often than the learning period, for example a quarterly close or an annual key rotation. Usage data does not capture these, and you will need to add them manually when generating the permission set.

Step 2: Generate a Least-Privilege Permission Set

Generate a policy or custom role with least privileges from the user's actual activity. This becomes the permission that the user requests through JIT.

To generate the permission set:

  1. In the Cloud Exposure, navigate to Explore > IAM > Identity Intelligence.
  2. Find the relevant identity, and do one of the following:
    • AWS — Click the three-dot menu and select Generate Least Privilege Policy. Clear Use specific resources instead of wildcards (only in supported AWS services). Specific resources make the policy larger, and the policy must fit in the eligibility's inline policy limit.
    • Azure — Click Generate Custom Role on the Microsoft Entra ID user. Select the Scope Level (management group, subscription, or resource group) that matches where the user needs access.
    • GCP — Click Generate Custom Role on the Google Workspace user. Select the Scope Level (organization, folder, or project) that matches where the user needs access.
  3. Set the learning period (Time Frame for Azure and GCP) to cover the user's full work cycle. Use at least the 90-day default.
  4. If the user gets admin access through a group, select Include permissions granted via group membership.
  5. Click Generate and copy the result.
  6. Add any infrequent tasks you noted previously.
  7. (Azure and GCP only): Create the custom role in your cloud provider from the generated definition. The JIT eligibility lists all built-in and custom roles, so the role must exist before the eligibility is created.
Note: AWS: If the generated policy exceeds the AWS maximum policy size, Cloud Exposure splits it into multiple policies. The number appears in parentheses next to the JSON policy icon.

Step 3: Create a JIT Eligibility for the Permission Set

The eligibility defines who can request the permission set, on which accounts, for how long, and with whose approval.

To create the eligibility:

  1. In the JIT Portal, select the scope that contains the accounts the user needs.
  2. Navigate to Eligibilities and click Add Eligibility.
  3. Enter a Name that describes the task, for example Prod DB Admin. Requesters see this name.
  4. Under Users and groups, select the user.
  5. Under Permissions, add the permission set you generated earlier:
    • AWS — Paste the generated policy into Add an inline policy. The inline policy cannot exceed 7,680 characters.
    • Azure — Select the custom role. To limit access below the subscription, select Resource groups only and then select the resource groups.
    • GCP — Select the custom role.
  6. Under Accounts, select only the accounts where the user had standing admin access. To restrict each request further, enable Limit account selection per request.
  7. Set Maximum duration to the shortest window that covers a typical task. The range is 1-24 hours.
  8. Under Approval workflow, select Approval required, and select one or more Approvers. For admin-level access, consider adding a second approval level.
  9. Enable Justification.
  10. Under Recurring access, select Disabled, or set a low Maximum recurring days value. Recurring access is enabled by default for up to 364 days, and a year of scheduled regrants behaves a lot like standing access.
  11. Click Add.

Step 4: Confirm the Eligibility Works

Have the user test the eligibility while the standing access is still in place.

To confirm the eligibility:

  1. Ask the user to Request Access through the JIT Portal, Slack, or Teams, and to run one real task with the granted permissions. To make the test meaningful, the user must sign in through the JIT-granted assignment, and not through their standing access.
  2. If a task fails, add the missing permission to the eligibility and repeat the test.
  3. In the JIT Portal, navigate to Audit > Access Requests, and confirm the request, approval, and duration appear as expected.

Step 5: Remove the Standing Access

Remove the standing assignment in your cloud provider. Choose the end state that fits the user:

  • Option A: Zero standing access. Remove every standing assignment. The user has no access to the accounts until a JIT request is approved.
  • Option B: Read-only baseline — Replace the admin assignment with a read-only role, for example AWS ReadOnlyAccess, Azure Reader, or GCP Viewer. The user keeps visibility for daily work and requests JIT for any change.
Note: One-click remediation from the Excessive Permissions page does not reach either end state. It replaces the user's policies with a least-privilege policy built from used permissions, so the admin actions the user ran stay standing.

To remove standing access:

  • AWS — In IAM Identity Center, remove the user's account assignment for the admin permission set. If the user gets the permission set through a group, remove the user from the group, and do not change the group's assignment (other members still depend on it). For Option B, assign a read-only permission set.
  • Azure — Remove the user's role assignment at the subscription or resource group. For Option B, assign Reader at the same scope.
  • GCP — Remove the user's IAM binding at the organization, folder, or project. For Option B, grant Viewer at the same level.
Caution: Azure: Azure requires every subscription to keep at least one active Owner. If the user is the last permanent Owner, assign a permanent Owner (outside of JIT) before you remove the user. Otherwise, any JIT-granted Owner assignment that becomes the only Owner does not expire. See FAQ: JIT for more information.

Step 6: Verify the Result

To verify the result:

  1. In the Cloud Exposure Console, navigate to Risks > Excessive Permissions and confirm the user no longer appears with admin-level excessive permissions. The Overprivileged finding for the user closes after the next sync.
  2. In the JIT Portal, review Audit > Access Requests for the user after 2 weeks. Frequent requests that hit the maximum duration mean the duration is too short or the user's work needs a different eligibility. Requests that never happen mean the user may not need the access at all, and you can delete the eligibility.