Grant Tenable JIT Permissions

You can connect the following cloud service providers / identity providers (IdPs) for JIT by granting Tenable required permissions:

Note: If you want to use Slack as part of the JIT workflow, allowing users to request/approve access via Slack, you need to configure Slack for JIT.

Connect AWS Identity Center for JIT

Tenable One Cloud Exposure JIT access for AWS is based on IAM Identity Center (successor to AWS Single Sign-On). Follow these guidelines to connect AWS Identity Center for JIT:

  • Connect your IdP to IAM Identity Center.
  • Only IAM Identity Center users and groups can participate in the JIT workflow. Users must match those users who are configured to log in to Cloud Exposure via SSO.
  • To ensure that Tenable collects all relevant IdP data within IAM Identity Center, make sure to connect the AWS management account to Tenable.
  • Tenable supports using an AWS delegated administrator account with JIT. If you use a delegated account, you need to integrate that account as well. Refer to AWS documentation for more information about delegated accounts.
  • Grant JIT-Related Permissions to Tenable

    Note: If you're using a delegated administrator account, make sure to grant permissions in the delegated account, and not the management account.
  • Establish trust between your external identity provider (IdP) and Tenable:
Note: If you use IAM Identity Center to authenticate identities from external IdPs into your AWS environment, you don’t need to integrate the external IdP with Cloud Exposure independently. AWS automatically provisions users and groups from the IdP into IAM Identity Center, and this data is brought into Tenable when you connect the AWS management account.
Caution: Tenable uses several permission sets to define access for JIT users. These are in addition to any existing permission sets your organization already uses. Be aware of the AWS account quotas related to permission sets in IAM Identity Center, and also note that some of these quotas can be increased.

Grant JIT-Related Permissions to Tenable

Note: If you're using a delegated administrator account, make sure to grant permissions in the delegated account, and not the management account. If you grant permissions in both accounts, Tenable will take the permissions from the delegated account. See Add Eligibilities for the ramifications of working with a delegated account within JIT.

To grant Tenable permissions for JIT access:

  1. Ensure that the AWS management account is connected. If you're using an AWS delegated administrator account, you need to connect that account as well.
  2. In the AWS Management Console, navigate to IAM > Roles and open the role that you created when you connected the relevant account:
    • If you're using a delegated administrator account, open the role you created when you connected the delegated account.
    • Otherwise, open the role you created when you connected the management account.
  3. In the Permissions tab, click Add permissions > Create inline policy.
  4. In the JSON tab, replace the existing text by pasting the relevant JIT policy or policies from the sections below:
  5. Click Review policy.
  6. Enter a name for the policy (e.g., TenableJIT) and then click Create policy.

JIT Policy for AWS Account Access

Use these policies to allow Tenable One Cloud Exposure to manage JIT access to AWS accounts and permission sets through AWS Identity Center.

Use only one policy per environment, depending on whether AWS Identity Center is managed directly from the Management Account for Account Access or via a Delegated Administrator Account for Account Access.

Management Account for Account Access

Copy

JSON

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "iam:ListRoles",
                "iam:ListPolicies"
            ],
            "Resource": "*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "iam:AttachRolePolicy",
                "iam:CreateRole",
                "iam:DeleteRole",
                "iam:GetRole",
                "iam:ListAttachedRolePolicies",
                "iam:ListRolePolicies",
                "iam:PutRolePolicy"
            ],
            "Resource": "arn:aws:iam::*:role/aws-reserved/sso.amazonaws.com/*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "iam:GetSAMLProvider",
                "iam:UpdateSAMLProvider"
            ],
            "Resource": "arn:aws:iam::*:saml-provider/AWSSSO_*_DO_NOT_DELETE"
        },
        {
            "Effect": "Allow",
            "Action": [
                "identitystore:Describe*",
                "identitystore:List*",
                "sso:AttachManagedPolicyToPermissionSet",
                "sso:CreateAccountAssignment",
                "sso:CreatePermissionSet",
                "sso:DeleteAccountAssignment",
                "sso:DeletePermissionSet",
                "sso:Describe*",
                "sso:DetachManagedPolicyFromPermissionSet",
                "sso:Get*",
                "sso:List*",
                "sso:ProvisionPermissionSet",
                "sso:PutInlinePolicyToPermissionSet",
                "sso-directory:List*",
                "sso-directory:Search*"
            ],
            "Resource": "*"
        }
    ]
}

Delegated Administrator Account for Account Access

Copy

JSON

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "sso:AttachManagedPolicyToPermissionSet",
                "sso:CreateAccountAssignment",
                "sso:CreatePermissionSet",
                "sso:DeleteAccountAssignment",
                "sso:DeletePermissionSet",
                "sso:DetachManagedPolicyFromPermissionSet",
                "sso:ProvisionPermissionSet",
                "sso:PutInlinePolicyToPermissionSet"
            ],
            "Resource": "*"
        }
    ]
}

JIT Policy for Application Access

Use these policies to allow Tenable One Cloud Exposure to manage JIT access to applications managed by AWS Identity Center.

Use only one policy per environment, depending on whether AWS Identity Center is managed directly from the Management Account for Application Access or via a Delegated Administrator Account for Application Access.

Management Account for Application Access

Copy

JSON

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "identitystore:Describe*",
        "identitystore:List*",
        "sso:CreateApplicationAssignment",
        "sso:DeleteApplicationAssignment",
        "sso:Describe*",
        "sso:Get*",
        "sso:List*",
        "sso-directory:List*",
        "sso-directory:Search*"
      ],
      "Resource": "*"
    }
  ]
}

Delegated Administrator Account for Application Access

Copy

JSON

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "sso:CreateApplicationAssignment",
        "sso:DeleteApplicationAssignment",
      ],
      "Resource": "*"
    }
  ]
}

Connect Azure for JIT

Add a role assignment in Azure to grant the Cloud Exposure app access to the root management group.

Note: If you already granted Tenable management permissions to the root management group during Connecting Azure, you can skip this procedure. To use JIT, you must also connect Connect a Microsoft Entra ID Tenant.

To grant Tenable permissions for JIT access:

  1. In the Azure portal, open the root management group for your organization. By default, the root management group's display name is Tenant root group.
  2. Navigate to Access control (IAM)
  3. Click Add > Add role assignment.
  4. Under Privileged administrator roles, search for and select User Access Administrator, and then click Next.
  5. Click +Select members, and then search for and select the Cloud Exposure Connector.
  6. Click Select, and then click Review + assign to review the new role assignment.
  7. Click Review + assign again to add the role assignment.

Connect GCP for JIT

Grant the Cloud Exposure service account Security Admin access on the organization level.

Note: If you already granted Tenable management permissions on the organization level during Connecting GCP, you can skip this procedure. To use JIT, you must also connect Google Workspace.

To grant Tenable permissions for JIT access:

  1. In the Google Cloud Console, navigate to the organization node that you want to add.
  2. Navigate to IAM & Admin > IAM.
  3. Click +GRANT ACCESS.
  4. In the New principals field, enter the service account email for the relevant Google Workspace. You can find this value:
    • in the Google Cloud Console, under IAM & Admin > Service Accounts, in the Email field.
    • in the Cloud Exposure Console, under SETTINGS > IDENTITY PROVIDERS > GOOGLE WORKSPACE, in the Service Account Mail field.
  5. In the Role field, search for and select the Security Admin role.

    For more information about this role, refer to Google Cloud documentation.

  6. Click SAVE.

Connect Microsoft Entra ID for JIT

Grant Admin consent to approve the Cloud Exposure JIT Connector app in Azure.

Prerequisites:

To grant permissions for JIT access:

  1. In the Cloud Exposure Console, navigate to Settings > JIT. Make sure you are in the Organization scope.
  2. Under, Microsoft Entra ID group memberships, locate the relevant tenant and click Grant Permissions.
  3. Grant Admin consent to approve the Cloud Exposure JIT Connector app in Azure and grant Tenable the necessary permissions. Once the consent is approved, you’ll be redirected back to Tenable to finish the set up.

    1. Pick an account. On the Microsoft account sign in page, pick an admin account belonging to the tenant you want to integrate with Tenable. Your user must be authorized to consent on behalf of the organization. For more information about the specific roles needed to do this, refer to Microsoft documentation.
    2. On the Permissions requested page, click Accept to approve the Cloud Exposure JIT Connector app in Azure.

    You're returned to Tenable, with the required Microsoft Entra tenant information displayed, and the permissions successfully granted.

Required Permissions for Tenable JIT App

Approving the Cloud Exposure JIT Connector app grants Tenable permissions to:

  • Sign in and read user profile — Allows users to sign-in to the app, and allows the app to read the profile of signed-in users. It also allows the app to read basic company information of signed-in users.
  • Read and write all group memberships — Allows the app to list groups, read basic properties, read and update the membership of the groups this app has access to without a signed-in user. Group properties and owners cannot be updated and groups cannot be deleted.
Note: Approving the app in Azure creates a service principal in your tenant, which acts as the governing mechanism for the app, and can be considered the instance of the app in your directory. For more information about application and service principal objects in Microsoft Entra, refer to Microsoft documentation.

Connect Google Workspace for JIT

You can connect Google Workspace for JIT:

  • During initial Google Workspace integration to Cloud Exposure, when you Add a Google Workspace.
  • After initial integration, by following the steps below.

Prerequisites:

To grant permissions for JIT access:

Choose one of the following ways to grant Tenable permissions:

Note:

  • Custom role — Supports all core functionality within Cloud Exposure, including Just-In-Time access. This option is recommended for most organizations.
  • Domain-wide delegation — Designed for organizations that require advanced IAM functionality, and also supports Just-In-Time access. For more information, see Domain-Wide Delegation (Advanced).

For more information about why these permissions are needed, see Connect a Google Workspace.

Connect Okta for JIT

You can connect Okta for JIT:

  • During initial Okta integration to Cloud Exposure, when you Add an Okta Organization.
  • After initial Okta integration, by following the steps below.

Prerequisites:

To grant permissions for JIT access:

  1. Log in to the Okta admin console as a Super Administrator.
  2. Navigate to Security > Administrators and click on the Admins tab.
  3. Find the admin that you used when you added an Okta organization to Cloud Exposure (with the Read-only Administrator role).
  4. Click Edit > Edit assignments.
  5. Click + Add assignment and then search for and select Group Membership Administrator.

    Note: If you have groups with administrative roles, you need to assign the Super Administrator role instead, since only super admins can manage such groups.
  6. Click Save Changes when finished.

Connect OneLogin for JIT

You can connect OneLogin for JIT:

  • During initial OneLogin integration to Cloud Exposure, when you Add a OneLogin Account.
  • After initial OneLogin integration, by following the steps below.

Prerequisites:

To grant permissions for JIT access:

  1. Go to the OneLogin Administration page.
  2. In the top menu, click Developers > API Credentials.
  3. Click New Credential, enter a Name, and select Manage Users to allow Cloud Exposure read/write access to your directory data. Click Save.
  4. Copy the Client ID and Client Secret. You will need to enter these in the upcoming steps.
  5. In the Cloud Exposure Console, navigate to Settings > Integrations > OneLogin.
  6. Find the relevant OneLogin account and click the three dots icon, and then click Edit.
  7. In the Edit OneLogin Account wizard, navigate to step 3 [Grant JIT Access (Optional)] by clicking Next.
  8. In step 3b, enter the Client ID and Client Secret you copied earlier and then click Finish.

Connect Ping Identity for JIT

You can connect Ping Identity for JIT:

  • During initial Ping Identity integration to Cloud Exposure, when you Add a Ping Identity Environment.
  • After initial Ping Identity integration, by following the steps below.

Prerequisites:

To grant permissions for JIT access:

  1. Log in to the Ping Identity console, and navigate to Applications > Applications.
  2. Click on the application that you created when you added a Ping Identity environment to Cloud Exposure.
  3. On the application page that displays, navigate to the Roles tab and click Grant Roles.
  4. Expand the Identity Data Admin role and select the relevant environment to grant the role.
  5. Click Save to update the role assignments, and ensure that the toggle button on the top is selected, to enable the application.