To navigate to the ES graphical Navigation Bar editor, you need to click the Configure menu in the ES app bar, then select General, and then select Navigation. The Navigation page allows you to customize the navigation bar of the ES app by adding, removing, or reordering the menu items. You can also edit the labels, icons, and links of the menu items. You can use the graphical editor to drag and drop the menu items, or you can edit the navigation XML directly.  For more information, see Customize the navigation bar in Splunk Enterprise Security 1 . The other options, A, C, and D, are not correct. There is no Navigation Menu option under the Configure menu. The Settings menu does not allow you to edit the navigation bar of the ES app. The Settings menu only allows you to edit the navigation menus of the Splunk platform, such as the app launcher and the user menu. References =

Customize the navigation bar in Splunk Enterprise Security

Design navigation graphs | Android Developers 1

Design navigation graphs | Android Developers

When exporting and importing updates to ES content, you should follow the best practices described in the Splunk Enterprise Security Admin documentation 1 . 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

A network anomaly notable is a type of notable event that indicates a possible network attack or misconfiguration. It is generated by the Network - Anomaly Detection - Rule correlation search, which uses the Splunk Stream app to monitor network traffic and detect anomalies based on predefined thresholds. A security analyst who is investigating a network anomaly notable would use the Protocol intelligence dashboard to gain more insight into the network activity and protocols involved in the anomaly. The Protocol intelligence dashboard provides a summary of network traffic by protocol, such as TCP, UDP, ICMP, and others. It also shows the top sources, destinations, ports, and applications for each protocol. The dashboard allows the analyst to filter the data by time range, protocol, source, destination, port, and application. The dashboard also provides drilldown links to other dashboards, such as the Network Resolution dashboard and the Traffic Size Analysis dashboard, for further analysis. Therefore, the correct answer is D. Protocol intelligence dashboard. References =

Network - Anomaly Detection - Rule

Protocol intelligence dashboard

Splunk Stream app

After installing the add-ons necessary for normalizing data, you should configure the add-ons according to their README or documentation. The add-ons that are included in the Splunk Enterprise Security package are preconfigured and do not require additional steps. However, the add-ons that are downloaded separately from Splunkbase may require additional configuration steps, such as enabling inputs, setting up credentials, or modifying props and transforms. You should review the README or documentation for each add-on to determine the specific configuration requirements and follow the instructions accordingly. References =

Deploy add-ons to Splunk Enterprise Security

About installing Splunk add-ons

 According to the Splunk Enterprise Security documentation, the Status Configuration window allows you to customize the status values and transitions for notable events. You can define which roles can change the status of a notable event from one value to another, and which roles can view the notable events with a specific status. To restrict the users with the ess_user role from being able to change the status of Resolved notable events to closed, you need to do the following steps:

On the Enterprise Security menu bar, select Configure > Incident Management > Status Configuration.

In the Status Configuration window, select the Resolved status from the list of values.

In the Status Transitions section, find the row for the closed status and click the Edit icon.

In the Edit Status Transition dialog box, remove the ess_user role from the Roles field and click Save.

Click Save Changes to apply the changes to the Status Configuration window.

This will prevent the users with the ess_user role from changing the status of any notable event from Resolved to closed. They will still be able to change the status of other notable events to closed, if they have the permission to do so. Therefore, the correct answer is A. From the Status Configuration window select the Resolved status. Remove ess_user from the status transitions for the closed status. References =  Customize status values and transitions for notable events .

According to the Splunk Lantern article on Managing data models in Enterprise Security, accelerated data requires approximately 3.4 times the daily data volume of additional storage space per year 1 . This means that if the daily input volume is 100 GB, the accelerated data model storage per year would be 100 GB x 3.4 = 340 GB. This estimate may vary depending on the data model configuration, the data retention policy, and the indexer cluster replication factor. References =

Managing data models in Enterprise Security

The data models that are used by Splunk Enterprise Security are the ones that are defined and provided by the Common Information Model add-on (Splunk_SA_CIM) and the Enterprise Security-specific data models.  The Common Information Model add-on contains 12 data models that cover various domains of security data, such as Web, Authentication, Network Traffic, Change, DLP, Email, Endpoint, Intrusion Detection, Malware, Performance, Ticket Management, and Vulnerabilities 1 .  The Enterprise Security-specific data models are Anomalies, Audit, Business Context, Data Loss Prevention, Identity Management, Risk, Threat Intelligence, and Web Proxy 2 .  Therefore, the data models that are used by ES are Web, Authentication, Network Traffic, and Anomalies, among others.  References  =  1 : Overview of the Splunk Common Information Model - Splunk Documentation - Data models included with the Splunk Common Information Model Add-on.  2 : Data models in Splunk Enterprise Security - Splunk Documentation - Enterprise Security-specific data models.

Removing throttling fields would not reduce the number of false positives from a correlation search. Throttling fields are the fields that are used to group events and suppress duplicate alerts. For example, if you use src and dest as throttling fields, then the correlation search will only generate one alert per unique pair of src and dest values within the throt tling window. This can help reduce the number of false positives by avoiding repeated alerts for the same issue. Removing throttling fields would increase the number of alerts generated by the correlation search, which could include more false positives. The other actions could help reduce the number of false positives by making the correlation search less sensitive or less frequent. Reducing the severity would lower the priority of the alerts and make them less visible. Increasing the throttling window would increase the time interval between alerts for the same issue. Increasing threshold sensitivity would make the correlation search more selective and require more evidence to trigger an alert. References =

Configure correlation searches in Splunk Enterprise Security

Optimizing correlation searches in 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