2023-10-31 11:16 PM
I have configured the esa alert below to trigger when our Palo Alto Firewalls detect a network scan attempt.
The issue is, if say I run a nmap scan, the Palo Alto will generate at least 4 events which results in 4 emails being sent.
I'd prefer to only have 1 email so I'd like to group the events together say over a 30 second window and then send the alert after that 30 second period.
There may be times when the palo alto generates multiple events so I can't always be sure how many events will be generated hence why I want to alert after that 30 second window.
SELECT * FROM Event(
/* Statement: Palo Alto Recon Detection */
(device_type IN ( 'paloaltonetworks' ) AND ec_theme IN ( 'tev' ) AND policy_name.toLowerCase() LIKE '%scan%')
2023-11-09 07:11 AM - edited 2023-11-09 07:12 AM
2023-11-01 02:20 PM
JeremyKerwin,
Based on what is in the Alerting with ESA Correlation Rules User Guide (https://community.netwitness.com/t5/netwitness-platform-online/alerting-with-esa-correlation-rules-user-guide-for-11-7/ta-p/654977) on page 93 it talks about using notification suppression to help limit the number of emails the ESA is sending out per alert. Please review this section to see if this is what you are looking for. I am currently not aware of any other way of restricting the email frequency.
2023-11-09 07:11 AM - edited 2023-11-09 07:12 AM
2023-11-14 05:31 AM
Thanks @EduCarbonell , this is what I was hoping to learn, exactly what I was looking for.
@JohnKisner Thanks, I'll certainly look into the limiting of emails for other alerts, in this case the use of the esa alert was what I hoping for.