The Splunk Product Best Practices team helped produce this response. Read more about example use cases in the Splunk Platform Use Cases manual.
In this use case, we'll explore how to use Splunk Enterprise Security to alert on high volume email activity by a user to non-corporate domains.
This use case depends on the email data model as defined by the Common Information Model (CIM). For simplicity, this example only uses email data from the Splunk Add-on for Microsoft Exchange but any data properly normalized for the email data model works well. It’s a best practice to use the CIM to normalize data at search time, but before you put in effort to create new knowledge objects, check Splunkbase to see if such a CIM-compatible app or add-on already exists.
Follow the instructions for the Splunk Add-on for Microsoft Exchange. Specifically, the
MessageTracking monitor stanzas within the TA-Exchange-HubTransport and TA-Exchange-Mailbox add-ons bundled with the Splunk Add-on for Microsoft Exchange. Don't forget to deploy the add-ons to the search heads to use Common Information Model to normalize data at search time.
Review the Overview of Incident Review in Splunk Enterprise Security in Splunk docs for guidance on how to triage and act on resulting incidents. If no results appear, there may not be any notable notable events. However, you may need to enable correlation searches or you may need to deploy the add-ons to the search heads to use the knowledge objects necessary for simple searching.
Watch the following video to see how the Use Case Library in Splunk Enterprise Security can strengthen your security posture and reduce risk with readily available, usable, and relevant content.