Tenable One AI Exposure 2026 Completed Changes

Tip: You can subscribe to receive these release notes by email or RSS.

This page describes major changes completed in 2026 in AI Exposure that affect how you work with the platform, including changes with potential backward compatibility issues.

Change Description Date
Tenable One Vulnerability Management Data Available in Tenable AI Exposure Import of Tenable One Vulnerability Management software data into the Software page in AI Exposure, with access for custom roles in Tenable One reset until administrators configure RBAC and restore it. October 4, 2026

What's Changing?

Tenable One Vulnerability Management sends all software components detected in your environment to the Software page in AI Exposure. This creates a unified software inventory that includes components detected on cloud workloads and hosts monitored by Tenable One Vulnerability Management, when you install and connect the relevant sensors.

AI Exposure imports this data into the Self-Managed scope. By default, users with a role assignment that includes the Organization scope in AI Exposure can view it. To prevent unintended access, Tenable removes AI Exposure access from all custom roles in Tenable One that include it as part of this release.

After you configure Role-Based Access Control (RBAC) in AI Exposure, you must manually restore access. For steps, see Tenable One Vulnerability Management Data Available in Tenable AI Exposure (October 4, 2026).

Impact and Value

This release establishes AI Exposure as a centralized view for all AI security data and insights within the Tenable One platform.

  • Org-wide visibility — The Software page in AI Exposure provides a unified view that contains all AI-related software that Tenable detects.
    This page provides you visibility into your usage of both sanctioned and unsanctioned components.
  • Shadow AI detection. AI Exposure identifies unsanctioned AI libraries and packages installed on hosts and cloud workloads, expanding your overall application coverage.
  • Reduced context switching — When you track AI software risk, you no longer need to switch between Tenable One Vulnerability Management and AI Exposure to view the complete AI software inventory.

Important: AI Exposure imports software data from Tenable One Vulnerability Management into the Self-Managed scope. However, AI Exposure does not automatically import the RBAC configured for that data. To restrict access for users who require limited data visibility, you must reconfigure RBAC in AI Exposure.

For steps to restore appropriate access control, see Tenable One Vulnerability Management Data Available in Tenable AI Exposure (October 4, 2026).

Configure RBAC in AI Exposure to Restore Access Control

As part of this release, Tenable One revokes AI Exposure access for all custom roles that include access to AI Exposure. To restore access, you must complete the following steps.

As an administrator, complete the following steps to configure user access:

  1. In the AI Exposure console, go to Settings > Users and Groups.

  2. For each user who needs access to AI Exposure and has an assigned role with an Organization scope, determine their access requirements:

    • If the user requires access to Tenable Vulnerability Management software data: No action is required.
    • If the user should not have access to Tenable Vulnerability Management software data: Remove the role assignment, and then create a new role assignment that excludes the Self-Managed scope.
    Note: To grant a user access to some scopes but not Self-Managed data, use Projects to create a project that includes all scopes except Self-Managed, and assign that project instead. For more information, see Projects.
  3. After you configure all users and role assignments in AI Exposure, re-enable access from Tenable One.
    To do this, enable AI Exposure in a custom role and assign that role to the relevant users. For more information, see Manage Custom Roles in the Tenable One Vulnerability Management User Guide.