Splunk SPLK-3001 - Splunk Enterprise Security Certified Admin Exam

 According to the Splunk Enterprise Security documentation, the Default Account Activity Detected correlation search uses the Local User Intel lookup table to flag known default accounts. The Local User Intel lookup table contains a list of default usernames and passwords for various systems and applications, such as admin, root, guest, and others. The correlation search compares the authentication events from the Authentication data model with the usernames in the lookup table and generates a notable event if there is a match. The notable event indicates that a default account was used to access a system or application, which could be a sign of a brute force attack or a misconfiguration. Therefore, the correct answer is B. Local User Intel. References =

Default Account Activity Detected

Local User Intel

According to the Splunk Enterprise Security documentation, threat gen searches are searches that generate synthetic events in the threat activity index to simulate security threats. Threat gen searches are useful for testing and validating the correlation searches, notable events, and adaptive response actions in Splunk Enterprise Security. Threat gen searches produce events in the threat activity index, which is a dedicated index for storing the synthetic events. The events in the threat activity index have the sourcetype of threatgen and the tag of threat. You can use the Threat Activity dashboard to view and analyze the events in the threat activity index. See Threat gen searches for more details.

The other options are not correct, because threat gen searches do not produce them. Threat gen searches do not produce threat intel in KV Store collections, which are key-value pairs of data that store and manage threat intelligence in Splunk Enterprise Security. Threat gen searches do not produce threat correlation searches, which are searches that correlate events with threat intelligence and generate notable events in Splunk Enterprise Security. Threat gen searches do not produce threat notables in the notable index, which are alerts or tasks that indicate potential security incidents or threats in Splunk Enterprise Security. Therefore, the correct answer is D. Events in the threat activity index. References = Threat gen searches.

Upping the Auditing Game for Correlation Searches Within ... - Splunk

The summariesonly=true option is a macro that modifies a correlation search to search only accelerated data. Accelerated data is the summary data that is generated by the data model acceleration process. Data model acceleration is a feature that speeds up searches and reports that use data models by pre-computing and storing the results of the data model queries. By using the summariesonly=true option, a correlation search can run faster and more efficiently, as it does not need to scan the raw events or the index time field extractions. However, the summariesonly=true option also requires that the data model acceleration is enabled and complete for the data model that the correlation search uses. Otherwise, the correlation search may not return any results or may miss some events that are not accelerated. References =

Use the summariesonly macro in Splunk Enterprise Security

Data model acceleration

When exporting and importing updates to ES content, you should follow the best practices described in the Splunk Enterprise Security Admin documentation1. One of the best practices is to avoid overwriting existing content on the destination system. To do this, you have two options: either use new app names each time you export content, or always include both existing and new content in each export. This way, you can preserve the original content and avoid conflicts or data loss. The other options, A, B, and C, are not correct. Using new app names each time content is exported is only one of the options, not the only one. Using the .spl extension when naming an export is not a problem, as it is the default extension for Splunk apps. Including only new content for each export is not a good practice, as it may overwrite existing content on the destination system. References =

Export content from Splunk Enterprise Security as an app

The Status Configuration window in Splunk Enterprise Security allows you to manage and customize the investigation statuses and the status transitions for notable events. You can specify which roles can change the status of a notable event from one status to another. For example, you can restrict the ess_user role from changing the status of Resolved notable events to Closed by removing the ess_user role from the status transitions for the Closed status. This way, only the roles that have the permission to change the status to Closed can close the Resolved notable events. References =

Manage and customize investigation statuses in Splunk Enterprise Security

 The Risk Analysis dashboard provides tools to analyze the risk scores and risk modifiers of various objects, such as systems, users, hashes, and network artifacts. The dashboard shows the risk score by object, the most active sources of risk, the risk score by category, the risk score over time, and the risk modifiers by object. The dashboard also allows you to create ad hoc risk entries, view the risk details of an object, and export the risk data as a CSV file. The other options, A, B, and D, are not correct. The Risk Analysis dashboard does not provide tools to show high risk threats, notable event domains, or key indicators of correlation searches. These are features of other dashboards in Splunk Enterprise Security, such as the Threat Activity dashboard, the Domain Analysis dashboard, and the Correlation Search Audit dashboard. References =

Analyze risk in Splunk Enterprise Security

Risk Analysis dashboard

According to the Splunk Enterprise Security documentation, the first step when preparing to install ES is to determine the size and scope of installation. This involves estimating the amount of data that you plan to ingest, the number of users that will access ES, the number of search heads and indexers that you need, and the hardware requirements for each component. This step helps you plan your deployment architecture and ensure optimal performance and scalability of ES. Therefore, the correct answer is D. Determine the size and scope of installation. References = Deployment planning.

The Splunk Add-on Builder helps you create technology add-ons, which are specialized add-ons that help to collect, transform, and normalize data feeds from specific sources in your environment. Technology add-ons are often referred to as TAs, and they start with the prefix TA-12. References = 1: Splunk Add-on Builder User Guide - About the Splunk Add-on Builder 2: Splunk Developer Portal - Develop Splunk Apps

 Adaptive response action history is stored in the cim_modactions index. This index contains the events generated by the adaptive response actions that are triggered by correlation searches or run manually from Incident Review. You can use this index to search, audit, and report on the adaptive response actions that have been executed in your environment. You can also view the adaptive response action history on the Adaptive Response dashboard in Enterprise Security1. References =

Adaptive Response dashboard - Splunk Documentation