FAQ: Data Protection
This article contains a list of frequently asked questions related to Data Protection within Tenable One Cloud Exposure.
Coverage
This section outlines the scope of data scanning in Cloud Exposure, including which resource types, file formats, and data types are supported.
Scanned Resource Types
For the list of supported resource types, see How Tenable Scans Your Data.
Scanned File Formats
For the list of supported file formats, see Scanned File Formats.
Scanned Data Types
For the list of the supported built-in data types, see Scanned Data Types. You can also create custom data types.
Data Scan Frequency
The scan frequency depends on multiple factors, such as the resource type, size, and data updates. Generally speaking, scanning occurs once every 2-7 days. Contact Technical Support for more information about changing this frequency.
Billing after Scanning Is Disabled
Billing begins as soon as a resource is scanned. If any of the following occur:
- Scanning is later disabled
- The resource is opted out
- Cloud Exposure loses access to the resource
Cloud Exposure attempts to scan the resource up to two more times during regular scan cycles. If the resource still cannot be scanned after these attempts, it is removed from the billing report.
Data Storage Policy
No. While telemetry and metadata (the existence and location of specific data types) is collected in the outpost and transmitted to the global Cloud Exposure platform, your sensitive data is never stored at rest anywhere else.
Viewing Detected Data
Yes. In the Inventory view of a scanned resource type, you can filter by data category information to view resources with sensitive data. Then in the profile view of a specific resource, navigate to the Data tab. See Data Resources for more information.
Regex and Data Classification
You can either edit an existing data type or create a new custom data type.
You can create custom data types and define detection regex for sensitive data that is specific to your organization. See Governing Proprietary Sensitive Data for more information.
Yes. You can use a Value exclude regex to exclude specific values from being classified for a data type.
For example, you can exclude known test email addresses, service accounts, or internal identifiers while continuing to scan and classify all other values of that data type.
Data Protection Permissions
Tenable aims to use the minimum permissions necessary, primarily read-only permissions. However, for some services, limited write permissions are required to enable indirect scans. These permissions allow scoped operations like creating backups or adjusting network access.
Currently, the following write permissions are required:
| Cloud | Resource | Permission | Details |
|---|---|---|---|
| AWS | RDS Cluster and Instance | rds:CreateDBClusterSnapshot rds:CreateDBSnapshot rds:ModifyDBClusterSnapshotAttribute rds:ModifyDBSnapshotAttribute |
Create database snapshots to enable indirect data scans |
| Azure | Storage Account Blob Container | Microsoft.Storage/storageAccounts/privateEndpointConnections/write | For Storage Account Blob Containers with network restrictions, Tenable uses Private Endpoints to access the stored objects. This permission is required to approve pending Private Endpoint connection requests initiated by Tenable. |
| Azure | SQL Server | Microsoft.Sql/servers/databases/write | Create database backups to enable indirect data scans |
No. Cloud Exposure uses the same permissions defined when Connecting OCI. If you've already configured access for Cloud Exposure to scan your OCI resources, no additional permissions are required for Data Protection.
Encrypted Database Scanning
Cloud Exposure supports DSPM scanning of encrypted resources such as databases and object storage, utilizing Cloud Service Provider (CSP) encryption options. However, Customer-Managed Keys (CMKs) are not currently supported for scanning.
Troubleshooting Scan Statuses
If the tooltip for the failed scan indicates missing permissions, review the required permissions for data scanning and ensure they are granted at the resource level.
Not Supported status indicates the resource cannot currently be scanned due to its configuration, encryption method, or service tier. If you believe support should be added for this type of resource, you can submit a request{target=_blank} for our product team to review. For more details, see How Tenable Scans Your Data.
Disabled status means data scanning has been turned off for the resource—either from scan settings for specific account scopes or via a data scan exclusion. To re-enable scanning, review your scanning scope and check the Data Scan Exclusions tab to see if a rule is targeting that specific resource.
To resolve permission issues for Blob Containers, ensure that:
- The Tenable data role and the required built-in roles are granted at the resource level.
- Data access is not prevented by a deny assignment{target=_blank} on the Blob Container, its resource group, or the subscription.
- The storage account's network access is not set to restricted. If it is, consider enabling private network access.
Test and Synthetic Data
Cloud Exposure is designed to detect real-world sensitive data. Test values (e.g., 1234-1234-1234-1234, [email protected]) or known test patterns such as public credit card test numbers are not classified. Similarly, synthetic data—data that follows the structure of sensitive values but does not contain actual identifiers—is also excluded from classification.
This helps ensure high accuracy and reduce false positives. If you're testing the platform, we recommend using actual (but non-sensitive) data samples that resemble real-world content.
Scheduled Scans and Maintenance
Cloud Exposure uses a scheduled task in Snowflake to automatically connect newly discovered databases. Disabling or removing the task will stop scans from running, preventing Tenable from updating Data Protection findings for the account.
If the account status is Missing Data Protection permissions:
- Re-run the intergration script to reapply the required roles and permissions.
- Make sure network access is correctly configured to allow Tenable IP addresses. For more details, see Connect Snowflake.
Database Scope and Discovery
Yes. When the scheduled task is enabled, Cloud Exposure automatically detects and connects newly created databases in Snowflake, including those shared through the Marketplace or from other accounts.
If you connect a new Snowflake account, you must grant the required permissions and complete the integration process for that account separately.
No. In-account scanning is not currently supported for Snowflake. All scans are performed externally by Tenable from the relevant cloud region.
Architecture and Regional Behavior
Data Protection scans are always performed from the same cloud provider and region as your Snowflake account.
For example, if your Snowflake account is located in AWS us-east-1, then Tenable will scan from AWS us-east-1. This ensures region parity and supports data residency requirements.
Data Boundaries and Monitoring Data Sprawl
You can use Custom Policies in Cloud Exposure to define and enforce data boundaries. These policies help detect when sensitive data is stored in locations where it should not reside, either outside defined boundaries or within restricted boundaries, such as in development accounts, public storage, or other unauthorized environments.
To monitor data sprawl, create a custom policy using one of the following templates under the Monitor Sensitive Data category:
- This sensitive data should not reside in these resources: Generates findings when sensitive data is found within the defined boundaries where it should not reside.
- This sensitive data should reside only in these resources: Generates findings when sensitive data is found outside the defined boundaries.
- Go to Risks > Cloud Policies and open the Custom tab.
- Click Add Custom Policy.
- In the Choose Policy Template screen, select Monitor Sensitive Data.
- Choose the relevant template, and click Next.
- Enter a policy Name, optional Description.
- Select a Severity. This is the severity of the finding when generated.
- Under Sensitive Data, choose what kind of data the policy applies to (for example, specific categories such as PCI or PII).
- Under Resources, define the data boundaries by selecting resources such as specific data resources, resource types, resources by tags, or resources by labels.
- Click Done to save the policy.
Once created, the policy continuously evaluates your cloud environment and generates findings when detecting sensitive data that is stored in locations where it should not reside, according to the selected template.
Licensing
Snowflake scanning is available with the Enterprise license only. If your organization uses a different license tier and you’d like to enable Snowflake support, contact your Tenable representative. For details, see the Licensing page.
No. Virtual machines and virtual machine images are billed as scan-based billable resources when Workload Protection scanning is enabled. Enabling data scanning on those virtual machines uses the same underlying scan and does not increase the number of billable resources.
In other words, data scanning is included as part of the existing virtual machine vulnerability scan when Workload Protection is enabled.
For more information about scan-based billable resources, see Licensing.
Virtual Machine Data Scanning
Yes. Tenable can scan both active virtual machines and virtual machine images for sensitive data, including secrets and credentials like passwords, API keys, and tokens. For more information, see How Tenable Scans Your Data.
Data scanning for VMs is tied to your Workload Protection settings. You can enable data scanning for:
When a scan identifies sensitive data, such as passwords, API keys, or tokens, on a virtual machine or image, only data types with Restricted sensitivity are classified. Findings are handled as follows:
- Existing findings — The severity level is raised by one level but is capped at High. For example:
- Medium findings are escalated to High.
- The severity level for High and Critical findings remain as they are.
- New findings — A finding is only generated if the detected data triggers a Custom Policy using a Monitor Sensitive Data template. In this case, the finding is created with the severity level defined in that specific policy.

