Excessive Permissions and Inactive Identities

Enforce least privilege in your cloud environment. The Tenable One Cloud Exposure Excessive Permissions page lets you view a breakdown of identities that have been assigned more permissions than what they need, to help you minimize the risk that such identities pose to your organization. This page also provides insight into the activity status of such identities, allowing you to view inactive identities.

Definition of Excessive Permissions

In Cloud Exposure, by default, excessive permissions for both service identities and users are defined as any permission that wasn't used in the last 90 days. You can change the Permission Usage Learning Period to adjust this period.

Note: For customers who started working with Cloud Exposure before February 2, 2025, the default values may differ. For example, for human identities in AWS, the default was defined using a 180 day period.
Important: Permissions are determined as “Used” either based on explicit cloud log evidence from the relevant CSP, or implicit evidence (i.e. Cloud Exposure doesn’t have evidence that the permission is excessive). See Visualize Permission Mapping to learn more about how unlogged permissions affect how Tenable determines which permissions are excessive and which are used.

Every identity that has excessive permissions has at least one finding associated with it. These findings are often triggered by an “Overprivileged” policy (for example, Overprivileged IAM role). In addition to handling these findings from the Findings page, you can also view, and automatically remediate them, from the Excessive Permissions page.

For Azure and GCP accounts, findings are opened per subscription or project, accordingly. If the same identity exists in multiple subscriptions or projects, Tenable will open separate findings for the identity, per subscription/project. These are represented on the Findings page as separate items. On the Excessive Permissions page, however, any such multiple findings are consolidated into a single table entry. As a result:

  • If you automatically remediate the identity from this page, all findings will be resolved.
  • If you manually trigger an action for the identity, multiple tickets will be created for each finding.

Definition of Inactive Identities

In Cloud Exposure, by default, inactive identities for both service identities and users are defined as any identity that showed no activity in the last 90 days. You can change the Permission Usage Learning Period to adjust this period.

  • For customers who started working with Cloud Exposure before February 2, 2025, the default values may differ. For example, for human identities in AWS, the default was defined using a 180 day period.
  • AWS: Cloud Exposure monitors any activity, including the use of credentials or attempts to assume the role.
  • Azure/Microsoft Entra ID:
    • Inactive applications are identified by the absence of sign-in logs for users or service principals, while inactive managed identities are identified by the absence of sign-in logs for service principals only.
    • Inactive applications that are performing provisioning are excluded from policy detection.
    • Tenable can't monitor activity for Enterprise applications with linked single sign-on, since such applications lack sign-on events.
  • GCP/Google Workspace: Cloud Exposure checks successful sign-in logs and activity time to verify usage.

Definition of Unused Roles

In Cloud Exposure, unused roles in GCP and Azure are identified to help reduce unnecessary roles and improve your cloud environment’s security and manageability.

A role is marked as Unused if it has no active bindings or assignments. In GCP only, a role is also marked as "Unused" if all of its bindings have been flagged as "unused" for more than 30 days.

This allows you to quickly identify and remove roles that are no longer in use, supporting least privilege enforcement alongside inactive identity and excessive permission insights.

Finding Creation for Overprivileged and Inactive Identities

The following table describes how findings are created for overprivileged and/or inactive identities.

Scenario Result
Identity is active and overprivileged Only an Overprivileged finding is created
Identity is inactive, but not overprivileged Only an Inactive finding is created. The Inactive label is applied to the identity and associated finding.
Identity is inactive and overprivileged Both an Overprivileged and an Inactive finding are created. The Inactive label is applied to the identity and the associated Overprivileged and Inactive finding.