Workload
Configure the following settings on the Workload settings page.
Settings > Security > Workload
- Virtual Machine
- Virtual Machine Image
- Container Registry
- Scan Exclusions
- Vulnerabilities
- End-of-Life
- Malicious Files
This is a how-to guide for configuring workload settings.
- For a conceptual overview of workload protection capabilities in Tenable One Cloud Exposure, see Vulnerability Management.
- For how-to guides about viewing and managing workloads, see Virtual Machines, VM Images, Container Images, and Software.
- For frequently asked questions, see FAQ: Vulnerability Management.
Virtual Machine Settings
Configure the following settings to fine-tune how Cloud Exposure scans virtual machines in your environment.
- Whether to exclude accounts from scans
- Whether to enable data disk scanning
- Whether to exclude virtual machines from scans
- Whether to exclude virtual machines from policies
- Maximum Virtual Machine Disk Size
Exclude Accounts from Virtual Machine Scan
By default, Cloud Exposure scans all instances in any account where you grant workload scanning permissions. However, you may want to fine-tune this to exclude specific accounts or account scopes from the scanning process. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
To exclude accounts from the scan:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Virtual Machines.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Virtual Machine Vulnerability Scanning section, choose whether to:
Inherit the configuration of the parent-level account scope (default).
Note: If you selected the entire Organization as the scope, the Inherit option is not available.- Override the configuration of the parent-level scope with a unique configuration (Enabled/Disabled) for this account scope. The unique configuration will remain on the child-level scope, regardless of any changes made in the parent-level scope.
Enable Virtual Machine Data Disk Scanning
By default, Tenable scans the root volume and all eligible non-root volumes attached to a virtual machine. Applications and databases installed on separate disks are included in the vulnerability assessment. However, you may want to fine-tune this to exclude specific accounts or account scopes from the scanning process.
To enable data disk scanning:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Virtual Machines > Virtual Machine Data Disk Scanning.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Virtual Machine Data Disk Scanning section, choose whether to:
Inherit the configuration of the parent-level account scope (default).
Note: If you selected the entire Organization as the scope, the Inherit option is not available.- Override the configuration of the parent-level scope with a unique configuration (Enabled/Disabled) for this account scope. The unique configuration will remain on the child-level scope, regardless of any changes made in the parent-level scope.
Exclude Virtual Machines from Policies
By default, Cloud Exposure policies apply to all resources within the scope of the policy. To fine-tune this, you can Exclude Resources from Policies to prevent any potential findings associated with the resources from being created. For example, you can:
- Exclude a specific virtual machine from being scanned for vulnerabilities
- Exclude a set of virtual machine from being scanned for vulnerabilities by defining an exclusion pattern.
Maximum Virtual Machine Disk Size
Workload Protection is enabled for virtual machines with a disk size up to 600 GiB. Contact Technical Support for more information or to change this value.
Virtual Machine Image Settings
Configure the following settings to fine-tune how Cloud Exposure scans virtual machine images in your environment.
- Exclude accounts from scans
- Exclude virtual machine images from scans
- Exclude Virtual Machine Images from Policies
- Maximum Virtual Machine Image Disk Size
Exclude Accounts from Virtual Machine Image Scan
By default, Cloud Exposure scans all instances in any account where you grant workload scanning permissions. However, you may want to fine-tune this to exclude specific accounts or account scopes from the scanning process. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
To exclude accounts from the scan:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Virtual Machine Images > Virtual Machine Image Scanning.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Virtual Machine section, choose whether to:
Inherit the configuration of the parent-level account scope (default).
Note: If you selected the entire Organization as the scope, the Inherit option is not available.- Override the configuration of the parent-level scope with a unique configuration (Enabled/Disabled) for this account scope. The unique configuration will remain on the child-level scope, regardless of any changes made in the parent-level scope.
Exclude Virtual Machine Images from Policies
By default, Cloud Exposure policies apply to all resources within the scope of the policy. To fine-tune this, you can Exclude Resources from Policies to prevent any potential findings associated with the resources from being created. For example, you can:
- Exclude a specific virtual machine image from being scanned for vulnerabilities
- Exclude a set of virtual machine images from being scanned for vulnerabilities by defining an exclusion pattern.
Maximum Virtual Machine Image Disk Size
Workload Protection is enabled for virtual machine images with a disk size up to 600 GiB. Contact Technical Support for more information or to change this value.
Container Registry Settings
Configure the following settings to fine-tune how Cloud Exposure scans container registries in your environment.
Enable Container Registry Vulnerability Scanning in Tenable
By default, registry scanning is disabled in Cloud Exposure for your entire organization. You can enable scanning via Console settings, and can fine-tune to enable/disable the feature on specific accounts or account scopes. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
To enable container registry scanning:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Container Registries.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Container Registry Vulnerability Scanning section, choose whether to:
Inherit the configuration of the parent-level account scope (default).
Note: If you selected the entire Organization as the scope, the Inherit option is not available.- Override the configuration of the parent-level scope with a unique configuration (Enabled/Disabled) for this account scope. The unique configuration remains on the child-level scope, regardless of any changes made in the parent-level scope.
Maximum Container Image Size
Workload Protection is enabled for container images up to 2 GiB in size. Contact Technical Support for more information or to change this value.
Kubernetes Cluster
Configure Self-Managed Kubernetes Cluster Retention
Clusters connected only via Helm chart, which stops reporting, may have been deleted from your Kubernetes environment, or it may only be offline temporarily. To keep your console clean of stale clusters, clusters become inactive when they have not reported for 24 hours and are deleted after a retention period (30 days by default). For more information, see Cluster Lifecycle.
You can change the default retention period for individual scopes that removes these stale clusters from your environment, for example to remove short-lived test clusters sooner or to keep clusters that go offline for extended maintenance. See Cluster Column Data
To configure retention period settings:
- In the Cloud Exposure Console, go to Settings > Security > Workload > Kubernetes Cluster tab.
- From the top left in the Organization tree, select a scope from the dropdown to apply the retention period to.
-
Under Self-Managed Kubernetes Cluster Retention, select one of these:
- Enabled — Select to remove inactive self-managed clusters after the retention period.
- In Days, enter the number of days a cluster can remain inactive before it is deleted.
- Disabled — Select to turn off retention for this scope, and clusters will not be deleted.
- Enabled — Select to remove inactive self-managed clusters after the retention period.
Scan Exclusions
Use Scan Exclusions to define which virtual machines, virtual machine images, and container registries Cloud Exposure skips during workload 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 Scan Exclusions
The Scan Exclusions table provides a centralized view of all active and inactive exclusions.
- In the Cloud Exposure Console, click on Settings > Security > Workload > Scan Exclusions.
- Select an account scope in the Organization tree drop-down.
- 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.
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 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 are automatically excluded starting with the next scan cycle.
To create a scan exclusion:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Scan Exclusions.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
- Click + Add Scan Exclusion.
- Enter a Name and Description.
-
In the Excluded Resources section, use the query builder to select your targets:
- Find Resource — Select Workload Resource, or a specific type under it: Virtual Machine, Virtual Machine Image, or Container Image.
- 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.
Vulnerability Settings
Configure the following settings to fine-tune how Cloud Exposure scans vulnerabilities in your environment.
- Vulnerability Severity Metrics
- Minimum Vulnerability Severity for Findings
- Findings for Vulnerabilities without Fixes
Vulnerability Severity Metrics
To support diverse risk assessment needs, customers can choose their preferred vulnerability severity metric. The available options are:
- CVSS (Common Vulnerability Scoring System)
- VPR (Vulnerability Priority Rating)
By default, CVSS will be used unless otherwise specified. This flexibility enables organizations to align severity scoring with their internal prioritization strategies. All CVSS scores will be sourced exclusively from the Tenable Vulnerability Database (TVDB) to ensure consistency and reliability. When multiple CVSS versions are available for a given CVE, the score from the highest version will be selected by default. The severity rating of a vulnerability is based on the vendor-provided rating; if unavailable, the rating from the National Vulnerability Database (NVD) is used.
To select the vulnerability severity metric:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Vulnerabilities.
- Select the vulnerability severity metric.
Minimum Vulnerability Severity for Findings
Set the minimum severity for creating findings. By default, findings are created for critical vulnerabilities. Lowering the threshold may increase findings.
To configure the minimum severity for creating findings:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Vulnerabilities.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Minimum Vulnerability Severity for Findings section, choose a relevant severity level:
- Informational
- Low
- Medium
- High
- Critical
Findings for Vulnerabilities without Fixes
Configure how findings are created for critical vulnerabilities. You can potentially reduce the number of open findings by only creating findings for vulnerabilities with fixes.
To configure how findings are created for critical vulnerabilities:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Vulnerabilities.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Findings for Vulnerabilities Without Fixes section, choose a relevant option:
- Inherit the configuration of the parent-level account scope (default).
- Enabled (overrides parent-level configuration). Only create findings for critical vulnerabilities with fixes.
- Disabled (overrides parent-level configuration). Create findings for all critical vulnerabilities (including those without fixes).
Note: Selecting Enabled or Disabled will override the configuration of the parent-level scope with a unique configuration for this account scope. The unique configuration will remain on the child-level scope, regardless of any changes made in the parent-level scope. If you selected the entire Organization as the scope, the Inherit option is not available. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
End-of-Life Settings
Configure the following setting to fine-tune the OS EOL Finding Threshold.
Operating System End-of-Life Finding Threshold
You can set an Operating System (OS) End-of-Life (EOL) finding threshold for virtual machines, virtual machine images, and container images. This enhancement, supported by Tenable, allows users to define a threshold that triggers findings when resources are at or near their OS EOL, improving visibility and enabling proactive risk management.
To set the threshold:
- In the Cloud Exposure Console, navigate to Settings > Security > Workload > End-of-Life.
- Set the required EOL threshold.
Malicious File Settings
Configure the following settings to fine-tune how Cloud Exposure scans malicious files in your environment:
Exclude Accounts from Scan
By default, Cloud Exposure scans all workloads in any account where you grant workload scanning permissions. However, you may want to fine-tune this to exclude specific accounts or account scopes from the scanning process. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
To exclude accounts from the scan:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Malicious Files.
- Select an account scope in the Organization tree drop-down. By default, the entire Organization (all accounts) is selected.
-
In the Malware Scanning section, choose whether to:
Inherit the configuration of the parent-level account scope (default).
Note: If you selected the entire Organization as the scope, the Inherit option is not available.- Override the configuration of the parent-level scope with a unique configuration (Enabled/Disabled) for this account scope. The unique configuration remains on the child-level scope, regardless of any changes made in the parent-level scope.
Add Trusted Files
Specify SHA-256 hashes of files which will be considered trusted. You must be a user with the Administrator role in Cloud Exposure to configure this setting.
- Via the Malicious Files page.
- Via relevant findings in the Overview or Remediation tabs.
To add trusted files:
- In the Cloud Exposure Console, click on Settings > Security > Workload > Malicious Files.
- Select an account scope in the Organization tree on the left to determine on which accounts the exclusion applies. By default, the entire Organization (all accounts) is selected.
- In the Trusted File SHA-256 Hashes section, click Add.
- Enter the SHA-256 hash for the file.
- (Optional) Enter a Comment.
- Click Add. The entry appears in the table.
- To delete an entry, click on the three dots next to the entry and then click Delete.