Automations
Required Tenable One Cloud Exposure User Role: Administrator. For more information, see Users and Groups.
Create automation rules that send push notifications to integrated third-party tools in the following situations:
- When specific risks (findings or threat stories) are identified in Cloud Exposure. See Send Risk Data to Third-Party Tools.
- When user actions are performed in Cloud Exposure. See Send Audit Data to Third-Party Tools.
Send Risk Data to Third-Party Tools
Create automation rules that send push notifications to integrated third-party tools when Cloud Exposure identifies specific risks. A risk automation rule can apply to cloud findings, IaC findings, or threat stories, depending on the Type you select.
The following core elements are defined for each risk automation rule:
- Target scope — The specific account scope for which you want to trigger the automation.
- Type — The category of risk the automation applies to: Cloud Findings, IaC Findings, or Threat Stories. The type determines which fields and default filters are available in the automation query.
- Automation query — An Explorer-based query that defines the specific risks (by severity, status, resource type, actor, threat detection, etc.) that trigger the rule.
- Delivery methods — One or more third-party tool integrations where notifications or tickets will be sent.
To add a new automation rule:
- In the Cloud Exposure console, navigate to Operations > Risk Automations.
- (Optional) Select a scope in the Organization dropdown. The automation is accessible to users with permissions in the selected scope.
- Click Create Automation.
-
Configure automation settings:
- Enter a Name and an optional Description that accurately describes the automation rule.
- For Status, select either Enabled or Disabled.
For Type, select Cloud Findings (the default), IaC Findings, or Threat Stories.
Note: Only the types your license and permissions cover appear in the dropdown.-
Choose an existing query by clicking Select query, or build one from scratch. The query builder applies default filters based on the selected Type.
- Linked queries cannot be deleted, made private, or edited with unsupported syntax.
- If you selected an existing query and want to edit it, open the three-dot menu and click Unlink to modify the filters. The policy will no longer be synced with the original query.
- For Target Scopes, select the scopes for which you want to trigger the automation. Select an entire folder to trigger automations for all existing and future accounts within the folder.
Choose whether to apply to existing risks. Enabling this applies the automation to all current risks of the selected type, in addition to any new risks detected moving forward.
Note: This option is only available when creating a new automation, or if the automation was previously disabled.For Delivery, click Add Method to configure where you want to send notifications to. You must first integrate with third-party tools for a specific delivery method to appear in the integrations list (except for Email address, which appears automatically).
The setup steps below are the same regardless of Type. What changes is the content sent to each channel: a Jira ticket created for a threat story carries threat-specific fields (Actor, Threat Detection), while a ticket for a cloud or IaC finding carries resource and severity fields instead.
Email addressSelect Specify recipients to enter one or more email addresses manually, or Extract recipients from custom property to send risks to resource owners.
- Specify recipients — Enter one or more email addresses in the To field.
- Extract recipients from custom property. Select an Owner Custom Property to resolve recipient email addresses from resource owner data. You must also enter Fallback recipients, used when no valid email address is found in the custom property. Fallback recipients receive all risks for all owners whose addresses could not be resolved.
A CC field is available for both options.
Each email delivery method supports one Owner Custom Property. To cover multiple properties, add additional email delivery methods. You cannot select the same Owner Custom Property in more than one delivery method.
Note: When using Extract recipients from custom property, Cloud Exposure sends each owner only the risks associated with their resources, not all risks in the automation scope.
SlackSelect a Workspace (single selection), then configure recipients:
- Specify recipients — Select one or more channels from the selected workspace.
- Extract recipients from custom property. Select an Owner Custom Property to send risks directly to the resource owner as a Slack user. Specify Fallback channels for cases where the owner cannot be resolved.
Note: When using Extract recipients from custom property, Cloud Exposure sends each owner only the risks associated with their resources.
Microsoft TeamsSelect an Organization (single selection), then configure recipients:
- Specify recipients — Select one or more channels from the selected organization.
- Extract recipients from custom property. Select an Owner Custom Property to send risks directly to the resource owner as a Teams user. Specify Fallback channels for cases where the owner cannot be resolved.
Note: When using Extract recipients from custom property, Cloud Exposure sends each owner only the risks associated with their resources.
JiraEnable the integration, and then select a Project, Issue Type, Labels, Epic (optional), and Environment (URL of Jira instance). For labels, you can either choose from a list of labels already configured in the Jira instance, or manually add new labels, which will be sent to Jira. Label names cannot contain spaces.
For the assignee, choose one of the following:
- Specify Assignee — Select a Jira user from a dropdown. This field is optional if the Assignee field is optional in your Jira project.
- Extract assignee from custom property. Select an Owner Custom Property to resolve the assignee from resource owner data. You can optionally specify a Fallback assignee for cases where the owner email address cannot be resolved. This option is also optional if the Assignee field is optional in Jira.
ServiceNowEnable the integration, select an Instance, and then configure the assignee:
- Assign to — Select an Assignment group (displayed only if required in your ServiceNow instance) and an Assigned to user from that group.
- Extract addresses from custom property. Select an Owner Custom Property to resolve the assignee from resource owner data. If the assignment group is required in your ServiceNow instance, a Fallback Assignment Group field also appears and must be specified.
Datadog organizations
QRadar servers
SQS queues
Splunk event collectors
Webhooks
-
Build and preview the query:
Note: Building a query is only relevant if you selected Standalone query earlier. The system automatically populates the query builder with a baseline filter that matches the selected Type.- Use the query builder to define your risk criteria. For more information, see Explorer.
- Review the table below the builder to see a real-time preview of risks that currently match your query logic.
- Click Create.
Send Audit Data to Third-Party Tools
Create automation rules to send Cloud Exposure audit data to any of the following third-party tools when user actions are performed in Cloud Exposure:
-
SIEM tools:
- Datadog
- Splunk
- QRadar
-
Notification tools:
- Slack
- Microsoft Teams
- Other third-party tools, via webhooks
The following core elements are defined for each audit-based automation rule:
- A specific account scope for which you want to trigger the automation. See Account Hierarchy and Folders for more information.
- A set of user actions for which you want to trigger the automation.
- Automation target/s, depending on which third-party tools you have integrated with Tenable.
To add a new automation rule:
- In the Cloud Exposure Console, navigate to Operations > Audit Automations.
- (Optional) Select a scope in the Organization dropdown. The automation is accessible to users with permissions in the selected scope.
- Click Add Rule.
- Enter a Name and Description (optional) that accurately describes the automation rule.
- Status: Select either Enabled or Disabled, and then click Save.
- Select the cloud account Targets for which you want to trigger the automation. Select an entire folder to trigger automations for all existing and future accounts within the folder.
-
Select any user Actions that you want to trigger the automation rule:
- All — Includes all user actions, and any future actions added by Tenable in the future.
- Specific actions — Select one or more individual user actions, organized by category:
- Platform.
- JIT Eligibilities. See Add Eligibilities in the JIT documentation for more information.
- JIT Access Requests. See Request Access in the JIT documentation for more information.
- Choose whether to also include system-generated actions.
-
Click Add Delivery Method to configure where you want to send notifications to. You must first integrate with third-party tools for a specific delivery method to appear in the list of integrations (except for Email address, which appears automatically).
- Datadog organizations
- Splunk event collectors
- QRadar servers
- SQS queues
- Slack channels
- Teams channels
- Webhooks
Enable or Disable an Automation
Enable or disable automation rules, giving you the flexibility to temporarily pause automated workflows without losing your configurations. When you're ready to resume sending data or notifications, you can toggle the rule back on.
To enable or disable an automation:
-
In the Cloud Exposure Console, navigate to either:
- Operations > Risk Automations
- Operations > Audit Automations
- (Optional) Select an account scope in the Organization dropdown. The automation is accessible to users with permissions in the selected scope.
- In the table, click the three dots menu next to the relevant automation and then click Edit.
- For the Status, select either Enabled or Disabled, and then click Save.
Duplicate an Existing Automation
Duplicate any previously generated automation (risk or audit data) to use as a baseline for creating a new automation. This allows you to quickly create a new automation with the same configuration as a previous one, saving you time and effort. For example, if you have a ServiceNow automation for AWS findings and need a similar one for Azure, duplicate the report and change the scope to your Azure environment.
When you duplicate an item, any associated configurations are handled based on their original scope:
- This applies to configurations like delivery methods and labels.
- If an associated configuration was set up on a narrower scope than your current one, it won't be duplicated with the item.
- For example, if you duplicate an item from a specific scope into your broader Organization scope, any configurations tied only to that narrower scope won't carry over.
This helps prevent irrelevant or misconfigured data from being created in your new scope. If you need these specific configurations, you'll have to reconfigure them manually within your current scope.
To duplicate an existing automation:
-
In the Cloud Exposure Console, navigate to either:
- Operations > Risk Automations
- Operations > Audit Automations
- (Optional) Select an account scope in the Organization dropdown. The automation is accessible to users with permissions in the selected scope.
- In the table, click the three dots menu next to the relevant automation and then click Duplicate.
- Modify the automation as needed and then click Add.