Setting Alert Actions
This page explains all the actions you can configure for each alert rule.
List on Activity Page
Adds the alert to the search index used for the Activity > Alerts page.
Send Email
Triggered alerts send email notifications, based on the configured alert schedule. The system sends the email through the AWS Simple Email Service (SES).
Forward Syslog
Forwards the matched events to a specified Syslog destination.
Note: Security Analytics supports only secure syslog. When you configure the connection to the destination syslog server, specify the remote server external IP address and listening port. You must also upload the destination server CA certificate (cert.pem). The maximum certificate file size is 24 KB.
Contact your syslog administrator to obtain the external IP address, listening port, and cert.pem file required to complete the configuration.
Forward to Splunk HTTP Event Collector
Forwards matched events to a specified Splunk HTTP Event Collector (HEC) destination. Anomali recommends forwarding alerts to Splunk HEC instead of Splunk syslog TCP input.
Webhook
Forwards matched events to a third-party service as a customizable JSON payload through an HTTP POST request. For example, you can use a webhook connection to create a ServiceNow ticket after Security Analytics triggers an alert. To set up a webhook connection:
-
Navigate to Manage > Alerting > Alert Rules.
-
Click Add.
-
Configure the following alert specifications:
-
Name and description
-
Search type — Saved Search or Custom search
-
Event time range
-
Alert schedule
-
Alert trigger condition
-
Throttle conditions
-
-
Set Alert Actions: Add a new webhook alert action, by providing the following information:
-
Select Webhook as the action.
-
Specify the URL to send the JSON payload through an HTTP POST request.
-
(Optional) Provide an Authorization Header.
-
(Optional) Provide any Custom Header.
-
Enter the Payload the webhook will share in JSON format.
-
Select Trigger for every match to make a single call for every alert trigger and for the third-party service to send one webhook call for each match in the results set.
-
Click Save.
-
-
Click Save to finish creating the alert.
-
Here's an example of the JSON payload customization:
The user configures an alert for the search query:
eventlog | fields event_time, sourcetype, action, user | limit 10You can configure the JSON payload while setting up the webhook connection as follows:
Option 1: Trigger for every match unselected
{ "alert": "My event log alert", "time": "{{events[0].event_time}}", # Get the value of the field 'event_time' from the first record "source_type": "{{events[1].sourcetype}}", # Get the value of the field 'sourcetype' from the second record "user": "{{events[2].user}}" # Get the value of the field 'user' from the third record }Option 2: Trigger for every match selected (that is, a separate call per trigger)
{ "alert": "My event log alert", "time": "{{event.event_time}}", "source_type": "{{event.sourcetype}}", "user": "{{event.user}}" }
Forward to Azure
Forward the matched events to an Azure Sentinel instance.
Note: To configure forwarding the matched events to an Azure Sentinel instance, ensure you meet the following prerequisites:
-
A Microsoft Entra application used for authentication, with a generated client secret.
-
A Data Collection Endpoint.
-
A custom table in the Log Analytics workspace.
-
A Data Collection Rule (DCR) with a defined alert JSON schema.
-
Permissions that allow the Microsoft Entra application to use the Data Collection Rule.
See the Microsoft documentation for more information about how log ingestion works.
When the alert triggers and Security Analytics sends the alert JSON to Azure, the alert appears in the Azure table. Azure accepts up to 1,000 alerts.
Fields that are absent from the schema are not ingested. If you need to update the schema, update it in Azure and wait for the changes to apply.
Note: DCRs allow you to customize actual field names, data types, and table structures as per the guidelines of your SIEM. Confirm the mappings against active DCR of your organization before final implementation.