Data
Configure the following settings and scope to fine-tune how Tenable One Cloud Exposure scans
your data.
- Disabling scanning immediately stops scans for all data platform resources. Those resources are excluded from billing until scanning is re-enabled.
- You need the Administrator role in Cloud Exposure to configure these settings. See Users and Groups.
This is a how-to guide for configuring Data settings in Cloud Exposure.
- For a conceptual overview of data protection capabilities, see Data Protection.
- For a how-to guide about connecting data resources to Tenable, see Connect Data Resources.
- For a how-to guide about viewing and managing data resources, see Data Resources.
Scanning
Buckets
Configure how Cloud Exposure scans cloud buckets, including public and private buckets. You can:
- Enable or disable scanning for specific accounts or scopes
- Enable or disable scanning of private buckets
- Configure access to restricted Azure storage accounts using Private Network Access
Configure Scanning Scope for Buckets
By default, Cloud Exposure scans buckets in any account where you grant data permissions. You can enable or disable scanning by scope.
To configure bucket scanning:
- In the Cloud Exposure Console, go to Settings > Security > Data > Scanning tab.
- From the top left in the Organization tree, select a scope from the dropdown to apply the configurations to.
-
In Buckets, select one of these from the dropdown:
Inherit — Select to inherit the configuration of the parent-level scope.
Note: If you selected the entire Organization as the scope, Inherit is not available.- Enable — Select to enable Data Scanning in buckets for the selected scopes. When you enable, you can also select the following:
- Scan private buckets — select if you want to scan private buckets in the selected scope or not.
Scan Azure networks restricted storage accounts — Select if you want to scan restricted storage accounts in Azure in the selected scope or not.
Note: Before enabling, review Configure Private Network Access for Azure Storage Accounts.
- Disable — Select to disable scanning for this scope. This overrides the configuration of the parent-level scope.
Configure Private Network Access for Azure Storage Accounts
If a storage account restricts network access (for example, it is accessible only through a virtual network), Cloud Exposure uses private endpoints to scan it. To enable this, select Scan Azure networks restricted storage accounts when you configure bucket scanning.
Before you enable this setting, review your Azure network and DNS configuration{target=_blank}. When you create a private endpoint, Azure can update the DNS records for the storage account, which in some environments blocks access and causes connectivity failures. To resolve this, you can fall back to the internet for Azure Private DNS zones{target=_blank}, or use virtual network (VNet) IDs to control routing behavior. For more guidance, contact your Cloud Exposure support representative.
Databases
Configure how Cloud Exposure scans your managed database environments.
Configure Scanning Scope for Managed Databases
By default, Cloud Exposure performs data analysis scans on managed databases in any account where you grant data permissions. You can enable or disable data scanning by scope.
To configure managed database scanning:
- In the Cloud Exposure Console, go to Settings > Security > Scanning.
- In the top left, select a scope in the Organization tree dropdown to apply the configurations to your desired account or a group of accounts within your hierarchy.
-
In the Databases section, select one of these from the dropdown:
Inherit — Select to inherit the configuration of the parent-level scope.
Note: If you selected the entire Organization as the scope, Inherit is not available.- Enable — Select to enable scanning for this scope, regardless of what the configuration of the parent scope is.
- Disable — Select to disable scanning for this scope, regardless of what the configuration of the parent scope is.
Virtual Machines
Configure how Cloud Exposure scans virtual machines.
Configure Scanning Scope for Virtual Machines
By default, Cloud Exposure scans virtual machines in any account where you grant data permissions. You can enable or disable data scanning by scope.
To configure virtual machine scanning:
- In the Cloud Exposure Console, go to Settings > Security > Data > Scanning tab.
- In the top left, select a scope in the Organization tree dropdown to apply the configurations to your desired account or a group of accounts within your hierarchy.
-
In the Virtual Machines section, select one of these from the dropdown:
Inherit — Select to inherit the configuration of the parent-level scope.
Note: If you selected the entire Organization as the scope, Inherit is not available.- Enable — Select to enable scanning of virtual machines for this scope, regardless of the configuration of the parent-level scope.
- Disable — Select to disable scanning of virtual machines for this scope, regardless of the configuration of the parent-level scope.
Virtual Machine Images
Configure how Cloud Exposure scans virtual machine images. You can enable or disable data scanning by scope.
Configure Scanning Scope for Virtual Machine Images
By default, Cloud Exposure scans virtual machine images in any account where you grant data permissions. You can enable or disable data scanning by scope.
To configure virtual machine image scanning:
- In the Cloud Exposure Console, go to Settings > Security > Data > Scanning tab.
- In the top left, select a scope in the Organization tree dropdown to apply the configurations to your desired account or a group of accounts within your hierarchy.
-
In the Virtual Machine Images section, select one of these from the dropdown:
Inherit — Select to inherit the configuration of the parent-level scope.
Note: If you selected the entire Organization as the scope, Inherit is not available.- Enable — Select to enable scanning of virtual machine images for this scope, regardless of the configuration of the parent-level scope.
- Disable — Select to disable scanning of virtual machine images for this scope, regardless of the configuration of the parent-level scope. The unique configuration remains on the child-level scope, regardless of any changes made in the parent-level scope.
Data Platforms
Configure how Cloud Exposure scans data platform environments, starting with Snowflake. You can enable or disable scanning by scope.
Configure Scanning Scope for Data Platforms
By default, Cloud Exposure scans connected Snowflake accounts where you grant data permissions. You can enable or disable data scanning by scope.
The Data Platforms section is available only when you select a scope that includes Snowflake.
To configure data platform scanning:
- In the Cloud Exposure Console, go to Settings > Security > Data > Scanning tab.
- In the top left, select a scope in the Organization tree dropdown that includes Snowflake to apply the configurations to your desired account or a group of accounts within your hierarchy.
-
In the Data Platforms section, select one of these from the dropdown:
Inherit — Select to inherit the configuration of the parent-level scope.
Note: If you selected the entire Organization as the scope, Inherit is not available.- Enable — Select to enable scanning for this scope, regardless of the configuration of the parent-level scope.
- Disable — Select to disable scanning for this scope, regardless of the configuration of the parent-level scope. The unique configuration remains on the child-level scope, regardless of any changes made in the parent-level scope.
Scan Exclusions
Use Data Scan Exclusions to define which cloud resources Cloud Exposure skips during data scans.
Common use cases include:
- Cost Optimization — Exclude non-critical development or testing resources to preserve license capacity.
- Environment Isolation — Exclude "sandbox" environments or resources already monitored by other tools.
- Sensitive Silos — Exclude highly regulated environments that enforce "no-tooling" policies.
View and Manage Data Scan Exclusions
The Data Scan Exclusions table provides a centralized view of all active and inactive exclusions.
- Go to Settings > Security > Data > Scan Exclusions.
- Select a scope in the Organization tree dropdown.
-
By default, the table displays items defined in the selected scope and parent scopes. Click Flat View to also see any items defined in children scopes.
- To view more details about an exclusion, including the specific resources currently targeted, click on the exclusion row to open the details pane.
- To manage an exclusion, click the three-dot menu at the end of the row to Edit, Enable/Disable, or Delete.
Data Scan Exclusion Statuses
| Status | Description |
|---|---|
| Enabled | The exclusion is active, and if it is not expired, applied in the next scan. Once the exclusion expires, findings it covered are reopened or reverted if no other exclusion applies. |
| Disabled | The exclusion is inactive but can be re-enabled. |
| Pending update | Modified and will update in the next scan. |
| Pending disable | Being disabled. Remains active until the scan completes. |
| Pending deletion | Queued for removal. Remains active until the scan completes. |
Create a Data Scan Exclusion
When you create an exclusion, you use the Explorer query builder to define the targeted resources. This logic is dynamic: any future resources that match your query parameters will automatically be excluded from the next scan cycle.
To create a data scan exclusion:
- Go to Settings > Security > Data > Scan Exclusions.
- Select a scope in the Organization dropdown. By default, the entire Organization (all accounts) is selected.
- Click + Add Exclusion.
- Enter a Name and Description.
-
In the Excluded Resources section, use the query builder to select your targets:
- Find Resource — Select a Native or Generic object (e.g., AWS S3 Bucket or Managed Database).
- Add Filters — Click + to add specific attributes such as Region, Account ID, or Tags.
- Review Preview — A list of currently targeted resources appears as you build the query.
- Click Save.
Classification Exclusions
A classification exclusion lets you fine-tune the data you want Tenable to ignore and where to ignore it. You define what to exclude (a data type, category, sensitivity, or specific value) and the exact resources and data objects it applies to. The scan still runs on the resource, so other sensitive data is still classified and billing is unaffected. For more information on how exclusions work, see Classification Exclusions.
Create a Classification Exclusion
Create a classification exclusion to stop Tenable from classifying specific sensitive data in specific locations, so that known-safe or irrelevant matches no longer generate findings.
Before you begin:
- Confirm that Data Protection is enabled for the resources you want to scope.
To create a classification exclusion:
- In the Cloud Exposure Console, go to Settings > Data.
-
Click the Classification Exclusions tab.
The Classification Exclusions section appears with any existing exclusions.
- Click + Add Classification Exclusion.
- In the Name box, type a name for the exclusion.
- (Optional) In the Description box, type a description.
-
In the Data section, under Types, select one of the following options:
- All data types, to ignore every data type.
- Specific data categories, then select one or more categories.
- Specific data sensitivities, then select one or more sensitivity levels.
- Specific data types, then select one or more data types.
-
Under Values, do one of the following:
- To ignore every value for the selected types, select All values.
- To ignore only certain values, select Specific values, then type an RE2 regex pattern in the box. The regex must follow RE2 syntax{target=_blank}.
-
In the Resources section, do one of the following:
- To apply the exclusion to every resource in your scope, select All resources.
- To apply the exclusion to certain resources, select Specific resources, then build a query to select them.
-
In the Data Objects section, define where Tenable ignores the data:
- To apply the exclusion to the entire resource, select All data objects.
- To target precise locations, select Specific data objects, click + Add, then add one or more location conditions: database name, database schema name, database table name, file extension, or object path. Each condition accepts multiple RE2 regex values, and Tenable applies OR logic between the conditions. The regex must follow RE2 syntax{target=_blank}.
If you selected All data types in step 6, the All data objects option is disabled. Select Specific data objects to continue.
-
Click Save.
Tenable creates the classification exclusion and lists it as Enabled. Save is available only after you complete the required selections.
What to do next:
- To change, turn off, or remove an exclusion, see the management steps below.
Manage a Classification Exclusion
You can edit, enable, disable, or delete an existing classification exclusion from the list.
To manage a classification exclusion:
-
In the Cloud Exposure Console, go to Settings > Data, then click the Classification Exclusions tab.
The Classification Exclusions section appears.
- In the row for the exclusion, click the action menu.
-
Do one of the following:
- To change the exclusion, click Edit, update the settings, then click Save.
- To turn the exclusion on or off, click Enable or Disable.
- To remove the exclusion, click Delete, then confirm.
Tenable applies the change and updates the Status column.
Data Types
A data type defines how Cloud Exposure identifies and classifies sensitive data during scans. Each data type includes detection logic and is mapped to a Category (such as PCI or PII) and a Sensitivity level, which together determine how findings are labeled and how risk severity is calculated.
Data types are evaluated during data scans and are used across findings, dashboards, and risk calculations.
Cloud Exposure supports two types of data types:
- Built-in data types — Predefined data types provided by Cloud Exposure to detect common sensitive data, such as email addresses, IP addresses, and national identifiers. Built-in data types include default detection logic, category, and sensitivity, which you can configure to match your organization’s requirements.
- Custom data types — User-defined data types that allow you to detect organization-specific sensitive data, such as internal identifiers, membership IDs, or transaction codes. When creating a custom data type, you define the detection logic and assign the category and sensitivity.
The Data Types table lists both built-in and custom data types and their current configuration. This view is available only when the scope is set to Organization. You can use the Type filter to view data types by source (Built-in or Custom).
You can enable or disable data types to control whether they are classified during scans.
Create a Custom Data Type
You can create custom data types to classify sensitive data that is specific to your organization, such as internal identifiers, membership IDs, or transaction codes.
When creating a custom data type, it is recommended to initially select the sensitivity level as Public or Private because the sensitivity levels influence the severity of findings. If a data type is assigned any other level (such as Confidential, Proprietary, or Restricted), the severity of findings associated with detected data is increased by one level. Selecting a lower sensitivity during initial validation helps confirm accurate classification before affecting risk severity.
After creating a custom data type, it is enabled by default and takes effect after the next data scan. You can later edit the custom data type and disable it.
To create a custom data type:
- Ensure the scope is set to Organization.
- Go to Settings > Security > Data > Data Types.
- Click Add Custom Data Type.
- Enter a Name and (optional) Description.
- Select a Category.
- Select a Sensitivity level.
-
Configure one or more of the following regex fields:
- Include regex — Defines the pattern used to identify values for this data type.
- Exclude regex (optional): Excludes specific values from being classified.
- Context regex (optional): Matches keywords or context near the value, such as column names or paths within files.
Keep in mind:- The regex must follow RE2 syntax{target=_blank}.
- Exclusions apply only to the selected data type.
- Click Create.
For more information, see Governing Proprietary Sensitive Data.
Edit a Data Type
You can change the configuration of built-in and custom data types to match your organizational requirements. This includes changes such as updating its classification, sensitivity level, or enabling or disabling the data type.
These adjustments affect labeling and how the data appears across findings and dashboards, but they do not affect core scanning behavior. You must be an admin to edit data types.
You can adjust the following properties:
- Category — Assign a different classification to the data type.
- Sensitivity — Set the sensitivity level applied to the data type.
- Status:
- Enabled — The data type is classified and appears in findings.
- Disabled — The data type is not classified and does not appear in findings or risk calculations.
- Exclude regex (optional): Exclude specific values from being classified for this data type.
For custom data types, you can also update:
- Include regex — Defines the pattern used to identify values for this data type.
- Context regex — Matches keywords or context near the value, such as column names or file paths.
To edit a data type:
- Ensure the scope is set to Organization.
- Go to Settings > Security > Data > Data Types.
- Find the data type you want to modify, open the three-dot menu, and click Edit.
- Update the Category, Sensitivity, or Status, as needed.
-
Under Value, specify an Exclude regex to exclude matching values from classification. For custom data types, you can also update the Include regex or Context regex to modify detection logic.
Note:- The regex must follow RE2 syntax.
- Exclusions apply only to the selected data type.
- If you restore the default configuration for a built-in data type, any configured exclusion regex is deleted.
- Click Save. Changes take effect after the next data scan.
Restore Default Classification (Built-in Data Types)
If a built-in data type has been modified, you can revert it to its default configuration. Restoring a data type immediately clears all customizations.
If the data type includes an Exclude regex, restoring the default configuration also deletes the exclusion regex.
To restore a data type’s default configuration:
- Ensure the scope is set to Organization.
- Go to Settings > Security > Data > Data Types.
- Find the data type, open the three-dot menu, and click Restore Default.
- Click Yes to confirm.
Delete a Custom Data Type
You can delete custom data types that are no longer needed.
If a custom data type is currently used by a custom policy, it cannot be deleted.
To delete a custom data type:
- Go to Settings > Security > Data > Data Types.
- Find the custom data type, open the three-dot menu, and click Delete.
- If the data type is being used, a message lists the referencing custom policies. To confirm deletion, click Yes.