The idea of enriching events helps filter out false positives — events that pose no real risk to a network. False positives can obviously — and do — waste many hours of a security analysts time (been there, done that!).
Having to manually search through security events is also very time consuming (and boring!). Automation can be helpful in alerting when only an event of significance is seen.
In this post I will walkthrough how to set up Slack alerts (although you can use another channel, including email) in Splunk for MHN events that match against Threatstream IOCs, and thus likely need further investigation.
You have a Splunk instance with Modern Honey Network data being matched against Threatstream IOCs. Here’s a walkthrough detailing how to do this.
Alerts will be sent from Splunk to Slack. Login to your Slack team and select: Apps & Integrations > Incoming Webhook. Then follow the instructions to add a new webhook.
In the last post I used all MHN data that had Threatstream IOC matches using the following search:
source=”*mhn-splunk.log*” | lookup tsi_ip lookup_key_value AS src OUTPUTNEW confidence AS ts_confidence, itype AS ts_itype, detail AS ts_detail | search ts_confidence=”*”
All Splunk alerts are based on events returned by searches. You can customise the search and time range to further filter results if needed.
Once you’ve created and run the search you want to use, select: Save as > Alert.
You can choose either a real-time or scheduled alert and set the conditions that will trigger the alert. For example, for a scheduled alert you might only want to see alerts when MHN events that match the search increase by 20%.
Under “triggered actions” select “outgoing webhook” and enter the Slack webhook URL (created during step one). If you don’t want to use Slack you can choose another action, perhaps email.
Every time the conditions of the alert are met, an message will be posted to Slack. The Slack message will provide you with a Splunk link to the events that triggered the search so you can start your investigation.
You should get familiar with Splunk’s search language so you can create additional search constraints to improve the quality of the alerts that are triggered.
Over the next few weeks I will be posting a series of guides about how to get value out of the data being generated by your honeypots. You can get updated about new MHN posts by Anomali on Twitter.
David is a Product Manager at Anomali. He's responsible for developing and executing strategy for integrations to and from the ThreatStream platform, working closely with Anomali customers to help them realize the value that threat intelligence can deliver to their business.