Connect Workloads
To enable Workload Protection on a given account/s, you need to onboard the account to Tenable One Cloud Exposure and grant Tenable workload scanning permissions for that account.
AWS: EC2 Instance and Internal AMI Scanning (Workload Protection)
Grant Cloud Exposure permissions to scan AWS workloads 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 EC2 Instance Scanning permission, but, depending on when you onboarded your account/s, may not have been granted yet.
- If you already onboarded the AWS account where you want to scan workloads, but haven’t yet added EC2 Instance Scanning permissions, follow the procedure below.
- If you did not yet onboard the AWS account where you want to scan workloads, follow the procedure documented in Connect an AWS Account.
To verify whether or not you have already added EC2 Instance 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 workload protection permissions have not been granted, follow the procedure below.
To grant EC2 Instance and Internal AMI scanning permissions:
- In the AWS Management Console of the relevant account, navigate to IAM > Roles and open the role that you created for Tenable during account onboarding.
- In the Permissions tab, click Add permissions > Create inline policy.
- Copy the policy provided in step 3 (IAM Role) of the AWS Add Account wizard in the Cloud Exposure Console, and paste it into the JSON tab to replace the existing text. See AWS EC2 Instance Scanning Workload Protection Policy to view the policy in JSON format.
- Click Review policy.
- Enter a name for the policy (for example, TenableWorkloadProtection) and then click Create policy.
- In the Cloud Exposure Console, navigate to Settings > Accounts > AWS, and verify that the Status of the account is Connected.
AWS EC2 Instance Scanning Workload Protection Policy
JSON
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": "ec2:CreateSnapshot",
"Resource": "arn:aws:ec2:*:*:volume/*"
},
{
"Effect": "Allow",
"Action": "kms:CreateAlias",
"Resource": "arn:aws:kms:*:*:alias/*"
},
{
"Effect": "Allow",
"Action": [
"ec2:CopySnapshot",
"ec2:CreateSnapshot",
"ec2:CreateTags",
"kms:CreateKey",
"kms:TagResource"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:RequestTag/ErmeticContext": "WorkloadAnalysis"
}
}
},
{
"Effect": "Deny",
"Action": "kms:TagResource",
"Resource": "*",
"Condition": {
"Null": {
"aws:ResourceTag/ErmeticContext": "true"
}
}
},
{
"Effect": "Allow",
"Action": "ec2:CopySnapshot",
"Resource": "arn:aws:ec2:*::snapshot/snap-*"
},
{
"Effect": "Allow",
"Action": [
"ec2:CopySnapshot",
"ec2:DeleteSnapshot",
"ec2:ModifySnapshotAttribute",
"kms:CreateAlias",
"kms:CreateGrant",
"kms:Decrypt",
"kms:EnableKeyRotation",
"kms:GenerateDataKeyWithoutPlaintext",
"kms:ReEncryptFrom",
"kms:ReEncryptTo",
"kms:RevokeGrant",
"kms:ScheduleKeyDeletion"
],
"Resource": "*",
"Condition": {
"StringEquals": {
"aws:ResourceTag/ErmeticContext": "WorkloadAnalysis"
}
}
},
{
"Effect": "Allow",
"Action": [
"kms:CreateGrant",
"kms:Decrypt",
"kms:ReEncryptFrom"
],
"Resource": "*",
"Condition": {
"StringLike": {
"kms:ViaService": "ec2.*.amazonaws.com"
}
}
}
]
}
Azure: Grant Virtual Machine Scanning Permissions
Grant Cloud Exposure the necessary permissions to scan Azure workloads by assigning the Disk Snapshot Contributor role. These permissions are typically granted as part of the Azure onboarding process in Tenable wizard. However, depending on when your organization or subscriptions were onboarded, the permissions may not have been granted yet.
- If you already onboarded the Azure subscription where you want to scan workloads, but haven’t yet added Virtual Machine Scanning permissions, follow the procedure below.
- If you did not yet onboard the Azure subscription where you want to scan workloads, follow the procedure documented in Connect an Azure Subscription.
To grant virtual machine scanning permissions:
- In the Azure portal, navigate to the Subscriptions page, and then click on the relevant subscription.
- Click Access control (IAM), and then click Add > Add role assignment.
-
On the Add role assignment page, search for and select the Disk Snapshot Contributor role, and then click Next. Alternatively, you can grant specific Azure permissions via a custom role.
Grant Windows Permissions via Built-in Role
- To support scanning Windows virtual machines with BitLocker or Linux virtual machines with DM-Crypt (supported only on Ubuntu) disk encryption, you need to grant Tenable the Key Vault Secrets User role.
- To support scanning Windows virtual machines with BitLocker encryption secret with a key from the key vault (KEK), you also need to grant Tenable the Key Vault Crypto User role.
- These permissions can be granted per subscription or per key vault.
- If permissions weren't granted, relevant virtual machines will have a scan status of Disabled.
- After granting permissions, the virtual machine will not be scanned immediately. Tenable attempts to scan every virtual machine as soon as 24 hours have elapsed from the previous scan.
- 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.
Grant Specific Azure Permissions via Custom Role
As an alternative to granting Cloud Exposure permissions to scan Azure workloads via the Disk Snapshot Contributor role, you can use a custom role to grant a more limited set of permissions. See Azure Required Permissions for the full list of custom role permissions, including the additional Key Vault permissions required to scan encrypted virtual machines.
To grant specific Azure permissions via a custom role:
- Create a custom role with the permissions listed in Azure Required Permissions.
- Follow the instructions in Grant Virtual Machine Scanning Permissions, but instead of selecting the Disk Snapshot Contributor role, select the custom role that you created.
GCP: Grant Workload Protection Permissions
Grant Cloud Exposure permissions to scan GCP workloads via a custom policy. These permissions are granted as part of the GCP onboarding process in the Tenable wizard, but, depending on when you onboarded your organization/project, may not have been granted yet.
- If you already onboarded the GCP organization/project where you want to scan workloads, but haven’t yet added workload protection permissions, follow the procedure below.
- If you did not yet onboard the GCP organization/project where you want to scan workloads, follow the procedure documented in Connect a Google Workspace.
To verify whether or not you have already added workload 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 workload protection permissions follow the procedure below to add the missing permissions.
To grant workload 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 > IAM.
- Click on Roles in the left hand menu.
- Click + CREATE ROLE
- Enter a meaningful Title, Description, and ID for the role. For example, you can enter Tenable Workload Scanning Permissions as the Title.
- Click + ADD PERMISSIONS.
-
Add the permissions listed in Google Required Permissions under Workload Protection. Use the filter to search for and select each permission, and then click ADD.
When finished, you should see that all seven permissions are assigned.
- Click CREATE.
- Click on IAM in the left hand menu.
- Click + Grant Access.
- Copy the service account that appears in Step 4 (Grant Workload Scanning Permissions) of the Tenable wizard and paste it in the Add Principals section
- In the Assign Roles section, filter for and select the custom role you created earlier.
- Click SAVE.
OCI: Grant Workload Protection Permissions
Grant Cloud Exposure permissions to scan OCI workloads by creating a new OCI policy and assigning the required permissions using policy statements.
To grant workload protection permissions:
- In the Cloud Exposure Console, make sure to enable the OCI Workload Protection toggle in the onboarding wizard.
- In the Oracle console, navigate to Identity & Security > Identity > Policies.
-
Click Create Policy and enter the following details:
- Name: Enter a meaningful name.
- Description: Enter a meaningful description
- Compartment: Select the root compartment
-
In the Policy Builder, click Show manual editor and add the statements listed in OCI Required Permissions.
Note: If you need to scan volumes encrypted with keys that you own and manage, also add the additional statements listed under Encrypted Volumes in the same article.
Alibaba Cloud: Grant Workload Protection Permissions
Grant Cloud Exposure permissions to scan Alibaba Cloud workloads via a custom, inline policy added to the Tenable RAM role. These permissions are granted as part of the Alibaba Cloud integration process in the Tenable wizard, but depending on when you onboarded your account, may not have been granted yet.
- If you already onboarded the Alibaba Cloud account where you want to scan workloads, but haven’t yet added workload protection permissions, follow the procedure below.
- If you did not yet onboard the Alibaba Cloud account where you want to scan workloads, follow the procedure documented in Connect an Alibaba Cloud Account.
To verify whether or not you have already added workload protection permissions, navigate to Settings > Organization > Accounts > Alibaba Cloud 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 workload protection permissions have not been granted, follow the procedure below.
To grant workload protection permissions:
- In the RAM console of the relevant account, navigate to Permissions > Policies
- Click Create Policy, and then select JSON Editor.
- Paste the policy from Alibaba Cloud Required Permissions in the JSON editor.
- Click OK.
- For Policy Name, enter tenable-workload-policy and click OK.
- Navigate to Identities > Roles and open the role that you created for Tenable during organization onboarding.
- Click Grant Permission.
- In the Policy section, select the policy you just created.
- Click OK and then Close.
- In the Cloud Exposure console, navigate to Settings > Organization > Accounts > Alibaba Cloud, and verify that the Status of the account is Connected.
Connect Your On-Premises Workloads
Grant Cloud Exposure permissions to scan on-premises workloads via Helm chart. See Connect a Cluster via Helm Chart for more information.