Connect Data Resources
To enable Data Protection on a given account, you need to connect the account to Tenable One Cloud Exposure and grant Tenable Data Protection permissions for that account. You can enable this feature for the following cloud providers:
AWS: Grant Data Protection Permissions
Required License: Data Scanning for this provider is available with Standard and Enterprise licenses. See Licensing for more information.
Grant Cloud Exposure permissions to scan data resources via a custom, inline policy added to the Tenable IAM role. These permissions are granted as part of the AWS integration process in the Tenable wizard via the Data Resources Scanning permission, but, depending on when you connected your accounts, may not have been granted yet.
- If you already connected the AWS account where you want to scan for sensitive data, but haven’t yet added Data Resources Scanning permissions, follow the procedure below.
- If you did not yet connect the AWS account where you want to scan for sensitive data, follow the procedure documented in AWS Overview.
To verify whether or not you have already added Data Resources Scanning permissions, navigate to Settings > Accounts > AWS in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Connected with issues, and the tooltip indicates that data protection permissions have not been granted, follow the procedure below.
To grant data protection permissions:
- In the Cloud Exposure Console, navigate to Settings > Accounts > AWS.
- Locate the relevant account and click Edit.
- Navigate to step 2 (Permissions) of the wizard, enable the Data Resources Scanning (Data Protection) permission, and then click Next.
- In step 3 (IAM Role), copy the inline policy for Data Resources Scanning Permission Policy (Data Protection).
- In the AWS Management Console of the relevant account, navigate to IAM > Roles and open the role that you created for Tenable during account integration.
- In the Permissions tab, click Add permissions > Create inline policy.
- Paste the policy that you copied earlier into the JSON tab to replace the existing text. See AWS Data Protection Policy to view the policy in JSON format.
- Click Review policy.
- Enter a name for the policy (for example, TenableDataProtection) and then click Create policy.
- In the Cloud Exposure Console, navigate to Accounts > AWS, and verify that the Status of the account is Connected.
AWS Data Protection Policy
JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"dynamodb:Scan",
"kms:CreateGrant",
"kms:Decrypt",
"kms:Encrypt",
"kms:GenerateDataKeyWithoutPlaintext",
"kms:ReEncryptFrom",
"kms:ReEncryptTo",
"rds:CopyDBClusterSnapshot",
"rds:CopyDBSnapshot",
"rds:CreateDBClusterSnapshot",
"rds:CreateDBSnapshot",
"rds:ModifyDBClusterSnapshotAttribute",
"rds:ModifyDBSnapshotAttribute",
"s3:GetObject",
"s3:ListBucket"
],
"Resource": "*"
},
{
"Effect": "Allow",
"Action": "rds:AddTagsToResource",
"Resource": [
"arn:aws:rds:*:*:snapshot:*",
"arn:aws:rds:*:*:cluster-snapshot:*"
],
"Condition": {
"StringEquals": {
"aws:RequestTag/TenableContext": "DataAnalysis"
}
}
},
{
"Effect": "Allow",
"Action": "rds:DeleteDBSnapshot",
"Resource": "*",
"Condition": {
"StringEquals": {
"rds:snapshot-tag/TenableContext": "DataAnalysis"
}
}
},
{
"Effect": "Allow",
"Action": "rds:DeleteDBClusterSnapshot",
"Resource": "*",
"Condition": {
"StringEquals": {
"rds:cluster-snapshot-tag/TenableContext": "DataAnalysis"
}
}
}
]
}
Azure: Grant Data Protection Permissions
Required License: Data Scanning for this provider is available with Standard and Enterprise licenses. See Licensing for more information.
Grant Cloud Exposure permissions to scan objects in Storage Account Blob Containers for sensitive data via the following roles.
- Storage Blob Data Reader built-in role.
- Tenable Data Scanning custom role.
- 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. This permission is only used if Private Network Access is enabled in the Settings page.
- Data scanning is not supported for a storage account with such network restrictions if an Azure Authorization Lock is configured. A lock can be applied at the storage account, resource group, or subscription level. In such cases, Tenable cannot remove the connection after scanning. To enable scanning, remove the lock.
These permissions are granted as part of the Azure integration process in the Tenable wizard, but, depending on when you connected your organization/project, may not have been granted yet.
- If you already connected the Azure subscription where you want to scan for sensitive data, but haven’t yet added Data Protection Scanning permissions, follow the procedure below.
- If you did not yet connect the Azure subscription where you want to scan for sensitive data, follow the procedure documented in connect Azure.
To verify whether or not you have already added data protection permissions, navigate to Settings > Accounts > Azure in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Data protection permissions not granted follow the procedure below to add the missing permissions.
To grant data protection permissions:
-
In the Azure portal, navigate to one of the following, depending on what you want to connect:
- Organization — The root Management group page of the organization.
- Subscription — The Subscriptions page, and then click on the relevant subscription.
- Create a custom role:
- Click Access control (IAM), and then click Add > Add custom role.
- For the Custom role name, enter Tenable Data Scanning.
- For the Baseline permissions, choose Start from scratch and then click Next.
-
Click Add permission and then search for and select the following permission:
- Microsoft.Storage/storageAccounts/privateEndpointConnections/write
- Microsoft.Sql/servers/databases/write
- Under Actions, select Write : Put Private Endpoint Connection and then click Add.
- Finish creating the custom role.
- Add role assignments. Assign both the Storage Blob Data Reader built in role and the Tenable Data Scanning custom role to the Cloud Exposure Connector App by performing the following steps for each role:
- Click Access control (IAM), and then click Add > Add role assignment.
-
On the Add role assignment page, search for and select one of the following roles, and then click Next:
- Storage Blob Data Reader built in role
- Tenable Data Scanning custom role
- Under Assign access to, leave the default selection as User, group, or service principal.
- Under Members, click +Select members.
- Search for and select Cloud Exposure Connector App, and then click Select.
- Click Next, review the new role, and then click Review + assign.
- Repeat these steps for the other role.
- In the Cloud Exposure Console, navigate to Accounts > Azure, and verify that the Status of the account is Connected.
GCP: Grant Data Protection Permissions
Required License: Data Scanning for this provider is available with Standard and Enterprise licenses. See Licensing for more information.
Grant Cloud Exposure permissions to scan objects in Storage Buckets for sensitive data via a custom policy. These permissions are granted as part of the GCP integration process in the Tenable wizard, but, depending on when you connected your organization/project, may not have been granted yet.
- If you already connected the GCP organization/project where you want to scan for sensitive data, but haven’t yet added data protection permissions, follow the procedure below.
- If you did not yet connect the GCP organization/project where you want to scan for sensitive data, follow the procedure documented in connect a GCP Environment.
To verify whether or not you have already added data protection permissions, navigate to Settings > Accounts > GCP in the Cloud Exposure Console, and check the status of the account.
- If the status is Connected, the required permissions have already been granted.
- If the status is Missing data protection permissions follow the procedure below to add the missing permissions.
To grant data protection permissions:
- In the GCP console of the relevant environment, go to the organization scope.
- Click the 3 line menu on the top left, and then IAM & Admin > Roles.
- In the table filter, enter the service account email that you used during initial GCP intergration.
- Click CREATE ROLE.
- Change the Title to Tenable Data Scanning.
- Change the ID to tenabledatascanning.
- Click ADD PERMISSIONS.
-
For each of the following permissions, use the filter to search for and select the permission, and then click ADD.
- bigquery.datasets.get
- bigquery.datasets.getIamPolicy
- bigquery.models.export
- bigquery.models.getData
- bigquery.models.getMetadata
- bigquery.models.list
- bigquery.routines.get
- bigquery.routines.list
- bigquery.tables.createSnapshot
- bigquery.tables.export
- bigquery.tables.get
- bigquery.tables.getData
- bigquery.tables.getIamPolicy
- bigquery.tables.list
- bigquery.tables.replicateData
- cloudsql.backupRuns.create
- cloudsql.backupRuns.delete
- cloudsql.backupRuns.get
- cloudsql.backupRuns.list
- cloudsql.instances.get
- dataplex.projects.search
- resourcemanager.projects.get
- resourcemanager.projects.list
- storage.folders.get
- storage.folders.list
- storage.managedFolders.get
- storage.managedFolders.list
- storage.objects.get
- storage.objects.list
- When finished, click CREATE.
-
Retrieve the service account name from the Cloud Exposure Console:
- In the Cloud Exposure Console, navigate to Settings > Integrations > GCP Organization, find the relevant organization and click Edit under the three dots menu.
- In the wizard that displays, click Next to navigate to Step 4 (Assign Roles).
- Click on the Manual (Google Cloud Console) tab.
- Copy the service account value that appears.
- In the GCP console, click on IAM in the left hand menu.
- Click + Grant Access.
- Paste the service account value that you copied in the Add Principals section.
- In the Assign Roles section, filter for and select the custom role you created earlier.
- Click SAVE.
OCI: Grant Data Protection Permissions
Required License: Data Scanning for this provider is available with Standard and Enterprise licenses. See Licensing for more information.
To grant Cloud Exposure permissions to scan Object Storage resources for sensitive data, complete the standard OCI account integration process. No additional roles, policies, or permission grants are required beyond integration.
After integration, verify that the required permissions have been granted. In the Cloud Exposure Console, go to Settings > Accounts > OCI and confirm that the account status is Connected. This indicates that all necessary permissions were successfully applied. No further action is needed.
Snowflake: Grant Data Protection Permissions
Required License: Data Scanning for this provider is available with the Enterprise license. See Licensing for more information.
To grant Cloud Exposure permissions to scan data in Snowflake, complete the standard Snowflake integration process. All required permissions are granted during the integration process—no additional configuration is needed.
After integration, verify that the required permissions were granted. In the Cloud Exposure Console, go to Settings > Accounts > Snowflake and confirm that the account status is Connected. This indicates that all necessary permissions were successfully applied. No further action is needed.
Required Permissions in Snowflake
To support Data Protection, Tenable requires the following read-only permissions in Snowflake:
- MONITOR USAGE on the account — Allows Tenable to view account-level usage information.
- MONITOR on the account — Allows Tenable to view the operational status and metadata of account resources.
- USAGE on the Tenable dedicated warehouse — Grants access to the compute resource used for scanning.
- IMPORT SHARE on the account — Allows the integration to import shared data at the account level. This permission is granted automatically during DSPM onboarding.
- IMPORTED PRIVILEGES on the database — Enables access to shared databases after the account-level IMPORT SHARE permission is granted.
- USAGE on the database and all current and future schemas: Allows visibility into the database structure.
- SELECT on all current and future tables in the database: Required to read data values for classification.
- SNOWFLAKE.GOVERNANCE_VIEWER on the database — Required to inspect applied object tags, masking policies, and row access policies.
- SNOWFLAKE.OBJECT_VIEWER on the database — Grants account-wide visibility into object metadata for comprehensive asset discovery and inventory.
- SNOWFLAKE.SECURITY_VIEWER on the database — Enables analysis of user roles, privileges, and network configurations to identify security risks.
These permissions are granted automatically during integration. No further configuration is needed unless the integration process was incomplete.