Use the audit dashboards to validate the security and integrity of the data in Enterprise Security. Ensure that forwarders are functioning, that data has not been tampered with and is secured in transmission, and that analysts are reviewing the notable events detected by correlation searches.
Incident Review Audit
The Incident Review Audit dashboard provides an overview of incident review activity. The panels display how many incidents are being reviewed and by which user, along with a list of the most recently reviewed events. The metrics on this dashboard allow security managers to review the activities of analysts.
|Review Activity by Reviewer||Displays the numbers of events reviewed by each user. This panel is useful for determining which user is performing the incident reviews and if the total number of incidents reviewed is changing over time. The drilldown opens a search with all activity by the selected reviewer.|
|Top Reviewers||Displays the top users that have performed incident reviews. The panel includes details for each user, including the date they first performed an incident review, the date they last performed a review, and the total number of incidents reviewed. The drilldown opens a search with all activity by the selected reviewer.|
|Notable Events By Status - Last 48 Hours||Displays the status, count, and urgency for all notable events in the last 48 hours. This panel is useful for determining if the incident review users are keeping up with incidents, or whether a backlog of unreviewed incidents is forming. The drilldown opens the Incident Review dashboard and searches on the selected urgency and status over the lat 48 hours.|
|Notable Events By Owner - Last 48 Hours||Displays the owner, count, and urgency for all notable events in the last 48 hours. This panel is useful for determining how many events are assigned to a user and the urgency of the events. The drilldown opens the Incident Review dashboard and searches on the selected urgency over the lat 48 hours.|
|Mean Time to Triage - Last 14 days||Displays the average time it took for a notable event to be triaged after it was created over the last 14 days, split by the name of the notable event. This panel is useful for determining how quickly analysts are triaging notable events, or whether certain types of events take longer to triage than others. The drilldown opens the Incident Review dashboard and searches on the matching notable event names over the last 14 days.|
|Mean Time to Closure - Last 60 days||Displays the average time it took for a notable event to be closed after it was created over the last 60 days, split by the name of the notable event. This panel is useful for determining how long it takes to close certain types of notable event investigations. The drilldown opens the Incident Review dashboard and searches on the matching notable event names that have a status of closed from the last 60 days.|
|Recent Review Activity||Displays the 10 most recent changes on the incident review dashboard, such as triage actions. The drilldown opens a search with the selected rule ID.|
To audit data from Incident Review from Enterprise Security prior to version 3.2, you must perform an ad hoc search like this example.
index=_audit sourcetype=incident_review | rex field=_raw "^(?<end_time>[^,]*),(?<rule_id>[^,]*),(?<owner>[^,]*),(?<urgency>[^,]*),(?<status>[^,]*),(?<comment>[^,]*),(?<user>[^,]*),(?<rule_name>[^,]*)"
The reports in the Incident Review Audit dashboard reference fields in the notable index and the incident review objects in a KVStore collection. See Notable index on the Splunk dev portal for more on the notable index.
The Investigation Overview dashboard gives insight into investigations, including monitoring open investigations, time to completion, and number of collaborators. You can filter by investigations where you're a collaborator or by investigations that exist on the system. you can use the All filter only if you have the "manage_all_investigations" capability.
In the descriptions that follow, there are references to "progress state" and "end state." Depending on your configuration, progress states can include statuses such as new, pending, and resolved. These states are considered unclosed because there is more work to do on the investigations. Also depending on your configuration, end states can include statuses such as closed, withdrawn, and fixed. These states are considered closed because there is no more work to do on the investigations.
|Unclosed Investigations||Displays the number of investigations in a progress state during the time set in the time range picker. This includes investigations that were closed yesterday but are reopened today, as the only states that are included in this panel are progress states.|
|Investigations Created||Displays the number of investigations created in the time set in the time range picker.|
|Investigations Closed||Displays the number of investigations that have reached an end state during the time set in the time range picker. This does not include investigations that were closed yesterday but are reopened today, as the only states that are included in this panel are current end states.|
|Oldest Unclosed Investigations||Displays the age of the investigations in a progress state during the time set in the time range picker. The investigations are sorted by create time. This is the list of investigations that corresponds to the number shown in the Unclosed Investigations panel.|
|Total Time Spent On Investigations||Displays the investigations, which were created in the time set in the time range picker, that spent the most cumulative time in a progress state.|
|Time Unclosed (In Days)||Displays the average and median number of days that investigations spent in a progress state during the time set in the time range picker.|
|Time To Complete (In Days)||Displays the average and median number of days for investigations to reach an end state during the time set in the time range picker. This includes the total lifetime from when the investigation started, went through states of progress, and even if it reached an end state, then was opened and completed again.|
|Investigations Unclosed Per Collaborator||Displays the number of investigations in a progress state for each collaborator during the time set in the time range picker, and the status of the investigations.|
|Investigations Unclosed Per Creator||Displays the number of investigations in a progress state for each person who created an investigation during the time set in the time range picker.|
|Investigations Unclosed Per Status||Displays the number of investigations in a progress state for each status during the time set in the time range picker.|
|Number of Collaborators Per Unclosed Investigation||Displays the number of people working on investigations in a progress state during the time set in the time range picker.|
|Longest Inactive Investigation (Unclosed)||Displays the investigations in a progress state that haven't been modified during the time set in the time range picker. These are investigations that are underway, but are not being actively worked on.|
|Most Often Reopened||Displays the investigations that have been completed and reopened the most amount of times during the time set in the time range picker.|
|Investigations Created Per Day||Displays the investigations created each day during the time set in the time range picker.|
The Suppression Audit dashboard provides an overview of notable event suppression activity. This dashboard shows how many events are being suppressed, and by whom, so that notable event suppression can be audited and reported on.
The metrics on this dashboard allow security managers to review the activities of analysts, which is useful for tuning correlation searches. You can identify correlation search rules that are generating more events than your analysts are capable of looking at, and tune them accordingly.
|Suppressed Events Over Time - Last 24 Hours||Displays notable events suppressed in the last 24 hours.|
|Suppression History Over Time - Last 30 Days||Displays the history of suppressed notable events.|
|Suppression Management Activity||Displays suppression management activity for the time period.|
|Expired Suppressions||Displays expired suppressions.|
The reports in the Suppression Audit dashboard reference events in the Notable index.
Per-Panel Filter Audit
The Per-Panel Filter Audit dashboard provides information about the filters currently in use in your deployment.
The following table describes the panels for this dashboard.
|Per-Panel By Reviewer||Displays the count of updates to per-panel filters by user|
|Top Users||Shows users, sparkline for trends, number of views, and first and last time viewed.|
|Recent Filter Activity||Activity by time, user, action, and filename|
Adaptive Response Action Center
The Adaptive Response Action Center dashboard provides an overview of the response actions initiated by adaptive response actions, including notable event creation and risk scoring.
|Action Invocations Over Time By Name||Displays a time chart of the adaptive response actions triggered by name.|
|Top Actions By Name||Displays the top adaptive response actions by name.|
|Top Actions By Search||Displays the top adaptive response actions by search.|
|Recent Response Actions||Displays the most recent adaptive response actions.|
The reports in the Adaptive Response Action Center dashboard reference fields in the Audit data model. For a list of data model objects and constraints, see Splunk Audit Logs in the Common Information Model Add-on manual.
Threat Intelligence Audit
The Threat Intelligence Audit dashboard tracks and displays the current status of all threat and generic intelligence sources. As an analyst, you can review this dashboard to determine if threat and generic intelligence sources are current, and troubleshoot issues connecting to threat and generic intelligence sources.
|Intelligence Downloads||Displays the status of all intelligence sources defined on the Intelligence Downloads configuration page. Use the filters to sort by status or download location.|
|Intelligence Audit Events||Displays log events related to intelligence downloads configured on the Intelligence Downloads configuration page and modular inputs configured on the Threat Intelligence Manager configuration page. Use the filters to sort and filter the events displayed.|
If an intelligence download fails, a search automatically creates a system message. See Troubleshoot intelligence downloads in Splunk Enterprise Security.
The reports in the Threat Intelligence Audit dashboard reference events in the
_internal index and state information from the
/services/data/inputs/threatlist REST endpoint.
Machine Learning Audit
The Machine Learning Audit dashboard displays information related to usage of the Machine Learning Toolkit (MLTK).
|Machine Learning Toolkit Errors and
Failed Fit and Apply Searches - Last 7 days
|Machine Learning Models||The list shows the names of the MLTK models. If you click on a model name to drill-down into the details, it opens a custom search that helps audit your model generating searches and the corresponding rules that apply them. See Audit searches using an MLTK Model.|
|List of Model Generating Searches||The button shows all the MLTK model generating searches and their statuses.|
ES Configuration Health
Use the ES Configuration Health dashboard to compare the latest installed version of Enterprise Security to prior releases and identify configuration anomalies. The dashboard does not report changes to add-ons (TA.) Select the previous version of Enterprise Security installed in your environment using the Previous ES Version filter.
|Unshipped||The Unshipped setting compares the latest installed version of Enterprise Security with the content in the ES installation package. Any item that was not provided as part of the Enterprise Security installation, such as files or scripts used for customization, is labeled as an Unshipped item. Review Unshipped items to evaluate their use, determine if they are still needed, and reconcile if necessary. The Unshipped setting ignores the Previous ES Version filter.|
|Removed Stanzas||The Removed Stanzas setting compares the latest installed version of Enterprise Security with the version that you select in the filter. Removed Stanzas are configuration stanzas that changed between versions, such as a deprecated threat list or input. Review Removed Stanzas to evaluate their use, determine if they are still needed, and reconcile if necessary.|
|Local Overrides||The Local Overrides setting compares the installed version of Enterprise Security with the version that you select in the filter. A setting that conflicts with or overrides the installed version of Enterprise Security is labeled as a Local Override. Review any Local Override settings to evaluate their use, determine if they are still needed, and reconcile if necessary.|
Data Model Audit
The Data Model Audit dashboard displays information about the state of data model accelerations in your environment.
|Field Name Panel||Description|
|Top Accelerations By Size||Displays the accelerated data models sorted in descending order by MB on disk|
|Top Accelerations By Run Duration||Displays the accelerated data models sorted in descending order by the time spent on running acceleration tasks.|
|Accelerations Details||Displays a table of the accelerated data models with additional information.|
Data model acceleration can be in progress and 100% complete at the same time. The process running and the status completing are not directly tied together.
The reports in the Data Model Audit dashboard reference fields in the Splunk Audit data model. For a list of data model objects and constraints, see Splunk Audit Logs in the Common Information Model Add-on Manual.
The Forwarder Audit dashboard reports on hosts forwarding data to Splunk Enterprise.
Use the search filters and time range selector to focus on groups of forwarders or an individual forwarder.
|Show only expected hosts||An expected host is a host defined in ES by the expected host field
||Drop-down, select to filter by|
|Host||Filter by the host field in the Asset table.||Text field. Wildcard with an asterisk (*)|
|Business Unit||Filter by the business unit
||Text field. Wildcard with an asterisk (*)|
|Category||Filter by the category field in the Asset table.||Drop-down, select to filter by|
|Event Count Over Time By Host||Displays the number of events reported over the time period selected in the filter. The events are split by host.|
|Hosts By Last Report Time||Displays a list of hosts, ordered by the last time they reported an event.|
|Splunkd Process Utilization||Displays the resource utilization of the forwarder's Splunk daemon |
|Splunk Service Start Mode||Displays the host names that are forwarding events, but are not configured to have |
Relevant data sources for the Forwarder Audit dashboard include data from all forwarders in your Splunk environment and the Application_State data model. See the Common Information Model Add-on Manual for more information. The Common Information Model fields
category are derived by automatic identity lookup, and do not need to be mapped directly.
The Indexing Audit dashboard is designed to help administrators estimate the volume of event data being indexed by Splunk Enterprise. The dashboard displays use EPD (Events Per Day) as a metric to track the event volume per index, and the rate of change in the total event counts per index over time. The EPD applies only to event counts, and is unrelated to the Volume Per Day metric used for licensing.
|Key Indicators||The key indicators on this dashboard are scoped to "All Time," not the "Last 24 hours".|
|Events Per Day Over Time||Displays a column chart representing the event counts per day.|
|Events Per Day||Displays a table representing event counts per day and the average eps.|
|Events Per Index (Last Day)||Displays a table of event counts per index for the last day.|
The reports in the Indexing Audit dashboard reference data generated by the
Audit - Events Per Day - Lookup Gen saved search and are stored within a KVStore collection.
The Search Audit dashboard provides information about the searches being executed in Splunk Enterprise. This dashboard is useful for identifying long running searches, and tracking search activity by user.
|Searches Over Time by Type||Shows the number of searches executed over time by type, such as ad-hoc, scheduled, or real-time. Helps determine whether Splunk's performance is being affected by excessive numbers of searches.|
|Searches Over Time by User||Shows the number of searches executed by each user. Helps determine when a particular user is executing an excessive number of searches. The |
|Top Searches by Run Time||Lists the most expensive searches in terms of duration. Helps to identify specific searches that may be adversely affecting Splunk performance.|
The reports in the Search Audit dashboard reference scheduled search auditing events from the
The View Audit dashboard reports on the most active views in Enterprise Security. View Audit enables tracking of views that are being accessed on a daily basis and helps to identify any errors triggered when users review dashboard panels.
|View Activity Over Time||Displays the Enterprise Security views that have the greatest access counts over time. The drilldown opens a search view of all page activity for the time selected.|
|Expected View Activity||Lists the views set up in the Expected View lookup. You want to review these views on a daily basis for your deployment. Select a dashboard to see details in the Expected View Scorecard panel below. See Manage internal lookups in Splunk Enterprise Security.|
|Web Service Errors||Displays errors that occurred while loading the web interface. Helps identify custom views that contain errors or an underlying issue that need to be escalated to Splunk.|
The reports in the View Audit dashboard reference fields in the Splunk Audit data model. For a list of data model objects and constraints, see Splunk Audit Logs in the Common Information Model Add-on Manual.
Managed Lookups Audit
The Managed Lookups Audit dashboard reports on managed lookups and collections such as services, data, transforms, KV Store lookups, and CSV lookups in Enterprise Security. Managed Lookups Audit shows the growth of lookups over time and the markers for anomalous growth. You can use this to help determine if any managed lookups are growing too large for your particular environment's performance and need to be pruned.
|Name||Displays the name of the Enterprise Security lookup. The drill-down takes you to all the contributing events for this particular lookup name from the audit_summary index.|
|Growth||Lists the lookup size over time as measured via a saved search that writes to the audit_summary index, running every 24 hours, displayed as a sparkline.|
|Count||Displays the estimated number of rows in the lookup file.|
|Size||Displays the size of the file in megabytes, sorted by the largest first.|
The Data Protection dashboard reports on the the status of the data integrity controls.
|Data Integrity Control By Index||Displays a view of all indexes with data protection enabled, sorted by search peer. For more information on configuring and validating data integrity, see Manage data integrity in Securing Splunk Enterprise. If you use Splunk Cloud Platform, file a support case to request enablement of data integrity control.|
|Sensitive Data||Displays the count of events with sensitive data. This panel requires enabling the Personally Identifiable Information Detected correlation search. For more information on how the IIN and the LUHN lookups are leveraged by correlation searches and displayed on the Data Protection dashboard, see Internal lookups that you can modify.|
Security Posture dashboard
Predictive Analytics dashboard
This documentation applies to the following versions of Splunk® Enterprise Security: 6.0.1, 6.0.2, 6.1.0, 6.1.1, 6.2.0, 6.3.0 Cloud only, 6.4.0, 6.4.1, 6.5.0 Cloud only, 6.5.1 Cloud only, 6.6.0, 6.6.2
Feedback submitted, thanks!