You can create your own notificationCommunication of an important event, typically through an email message or other desktop display. In USM Appliance, notifications are typically triggered by events, policies, and correlation directives, and in USM Anywhere, they are typically triggered by notification rules or directly from alarms. rules from the Orchestration Rules page or from the EventsAny traffic or data exchange detected by AlienVault products through a Sensor, or through external devices such as a firewall. details page, which the easiest way to configure the matching conditions.
To create a Notification Rule from the events page
- Navigate to ACTIVITY > EVENTS.
- Search the events which you want to include in the notification rule. See Searching Events for further information.
- Click on one of them.
- Click Create Rule > Create Notification Rule.
- Type a name for the rule.
- Select a notification method
- Amazon SNS. See Sending Notifications Through Amazon SNS for further information.
- Datadog. See Sending USM Anywhere Notifications to Datadog for further information.
- Email. This method sends the notification by email. You need to type an email subject and a destination email.
- PagerDuty. See Sending USM Anywhere Notifications to PagerDuty for further information.
- Slack. See Sending USM Anywhere Notifications to Slack for further information.
Note: These emails are sent through SNS. There is a quota of 200 notifications per day.
- You have already suggested property values to create a matching condition. If you want to add new property values, click Add Condition.
- You can click Add Group to group your conditions.
(Optional) To include a multiple occurrence parameter, click the More... link.
These options function together to specify the number of occurrences within a time period that will produce a match for the rule. For example, you can define a rule to trigger an alarmAlarms provide notification of an event or sequence of events that require attention or investigation. for an unauthorized accessAn incident-type categorization that may be a precursor to other actions or stages of an attack. attempt when a failed SSH Program to securely log into another computer over a network, to execute commands in a remote machine, and to move files from one machine to another through SCP.loginLog in (verb): Process in which an individual gains access to a computer system after providing sufficient credentials to authenticate their unique identity. Login (noun): User credentials, typically a username and matching password. occurs three times within a five minute window.
- Occurrences — Specify the number of event occurrences that produce a match on the conditional expression to trigger the rule. You can enter the number of occurrences or use the arrow to scroll the value up or down.
Length — Specify the length of the window used to identify a match for multiple occurrences. Enter the number and choose a time unit value of seconds, minutes, or hours.
This duration identifies the amount of time that transpires from the first occurrence to the last occurrence. If the number of occurrences is not met within this period, the rule is not a match.
In this example, the rule will apply when the configured conditions happen three times every five minutes.
- Click Save Rule.
Note: If the field is related to the name of a country, you should use the country code defined by the ISO 3166.
Note: Keep in mind that the Sources or Destinations field needs to match the UUID (Universally Unique Identifier) of the event or alarm. You can use Source Name(s) or Destination Name(s) instead.
Note: See Operators in the Orchestration Rules for further information.
The notification rule has been created. You can see it from SETTINGS > RULES, see Orchestration Rules for further information.