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 uncover high volume web uploads by a user to non-corporate domains.
This use case depends on the Web data as defined by the Common Information Model (CIM). Although the focus is on web data from Microsoft IIS, Apache Web Server, and NGINX, any data properly normalized for the Web datamodel 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.
Deploy the appropriate add-ons for Splunk Add-on for Microsoft IIS, Splunk Add-on for Apache Web Server, or Splunk Add-on for NGINX and enable the necessary inputs listed in the add-ons respective documentation. Pay special attention to the distributed deployment instructions to properly use the accompanying knowledge objects such as tags, fields, that are required for this use case.
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 or you may need to enable correlation searches.
If no results appear, you may need to deploy the add-ons to the search heads to use the knowledge objects necessary for simple searching.