FAQ: JIT
This article contains a list of frequently asked questions related to JIT within Tenable One Cloud Exposure.
AWS Access Assignments
For AWS, Cloud Exposure grants access using AWS IAM Identity Center. When a user requests access through JIT, Tenable:
- Creates a permission set that includes the policies (permissions) defined in the eligibility.
- Assigns the permission set to the requesting user for the selected accounts.
When the request expires or is revoked, Tenable automatically deletes both the permission set and the account assignments, fully revoking the user's access.
Azure Access Assignments
In Azure, access is granted using role assignments, which connect a user (identity), a role (such as Viewer), and a target resource (such as a subscription or resource group).
When a user requests access via JIT, Cloud Exposure creates a separate role assignment for each combination of target and role. For example, if an eligibility grants 5 roles on 10 subscriptions, that results in 50 role assignments.
When the access request expires or is revoked, Tenable deletes the role assignments it created. This is expected behavior and ensures that access is fully revoked when the request ends.
Recurring Access Requests
Yes. While recurring access is enabled by default on all eligibilities, you can disable it for any eligibility. This ensures that requesters must submit a new access request each time without automatic regranting.
How to disable Recurring access:
- In the Cloud Exposure JIT Portal, go to Eligibilities.
- Locate the eligibility and click Edit.
- Under Recurring access, select Disabled.
- Click Save.
Yes. By default, recurring requests can span up to 1 year (365 days) from the start date.
When creating an eligibility, you can define a Maximum recurring days value to limit how far ahead users can schedule recurring access: any value between 1–364 days.
For example, if the limit is set to 60 days and a user requests access starting July 1, they can only schedule recurring access until August 30.
Azure Owner Role
Azure requires that every subscription always has at least one active Owner role assignment.
If a JIT access request is the only active Owner assignment on a subscription, that assignment cannot expire or be revoked, even if its scheduled duration ends. It remains active until another Owner is assigned.
Three users (A, B, and C) are eligible to be assigned to the Owner role for three hours. No approval is required. Here's a breakdown of when each user is assigned to the Owner role and when the permission expires:
| Time | Action | Owners |
|---|---|---|
| 8:00 | User A is assigned to the Owner role. | A |
| 9:00 | User B is assigned to the Owner role. | A, B |
| 11:00 | User A's permission expires. | B |
| 12:00 | User B's permission doesn't expire. No other Owner. | B |
| 13:00 | User C is assigned to the Owner role. User B's permission expires. | C |
Why this happens:
Azure protects subscriptions from being orphaned—left without anyone who can manage access. To prevent this, it doesn’t allow the last Owner or User Access Administrator role assignment at the subscription level to be deleted unless the action is performed by a Global Administrator.
Workarounds:
- Assign Tenable the Global Administrator role in your tenant. This allows Cloud Exposure to delete the last Owner assignment.
- Alternatively, assign Tenable the Owner role on all subscriptions. This ensures that Cloud Exposure is never the last Owner, allowing other JIT-granted Owner roles to be revoked as expected.
Best practice:
To ensure Owner permissions granted through JIT can expire, we recommend assigning a permanent Owner role (outside of JIT) on each subscription.
Managing Jit Access in Large Environments
In large environments with many accounts (and resource groups in Azure) and permissions or roles, you can create broad eligibilities that include a wide set of accounts and roles—then limit how many a requester can select per request.
For example, you can create an eligibility with 50 accounts but allow each requester to select only 3 per request.
In Azure and GCP, requesters can also choose only the specific roles they need access to.
This approach reduces the number of eligibilities you need to maintain while helping enforce least privilege across your environment.
JIT Source IPs
For tenants in the eu-central-1 (Europe) region, JIT traffic originates from these static IP addresses:
- 18.192.163.94
- 3.67.105.194