Splunk® Enterprise Security

Use Splunk Enterprise Security

Acrobat logo Download manual as PDF


This documentation does not apply to the most recent version of Splunk® Enterprise Security. For documentation on the most recent version, go to the latest release.
Acrobat logo Download topic as PDF

General Settings

The Splunk App for Enterprise Security provides several configuration panels for functions of the app. Select Configure > All Configurations to view the options listed under the General configuration panel.

Credential Management

Click Credential Management to view and edit the stored user credentials for Enterprise Security App data inputs.

Es app config cred mgmt 3.0.png

The Credential Management page shows stored credentials for objects such as threat lists or lookups that run as scripted or modular inputs. An input that has been configured with a credential tries to find the credential values here.


Add a new credential for an input

1. Click New Credential to add a new user credential.

2. Use the edit panel to add the user name and password for the new credential.

Es create credential.png

3. Add the user name and password. The Realm field is optional, and can be used to differentiate between multiple credentials that have the same user name.

4. Select the Application for the credential.

5. Click Save. The new credential appears in the Credential Management list.

It may take several minutes for new Splunk users added to Enterprise Security to be reflected in Enterprise Security dashboards.

Edit an existing input credential

1. Click Edit next to the credential name.

2. Use the editor to change the user name, password, or application for the credential. You cannot change the realm setting after it has been applied to a credential. You must create a new credential to have a different realm.

Es credential mgmt edit 3.0.png

3. Click Save when you are done with your changes.

Delete an existing input credential

Use the REST API to delete an existing credential from the Credential Management page. See "DELETE storage passwords" in the Splunk Enterprise REST API Reference Manual.

Navigation

The Navigation editor is used to arrange and expose the domains and dashboards displayed in the Splunk App for Enterprise Security menu bar. Browse to Configure > General > Navigation to open the Navigation Editor.

Es nav editor 3.0.png

You must have Enterprise Security administrator privileges to modify menu bar settings.

Edit the default menus

Select items and add to an existing menu or create a new menu item. Removing domains or dashboards from the menu bar disables the navigation and display of that item only.

1. You may disable individual items or an entire menu using the Navigation editor.

  • To disable a domain or dashboard, click the "X" on the main menu panel.
  • To disable a single menu item, select the item (a check mark shows that the item is selected) and then click the "X" next to the item.

2. To rearrange display of the menus, select and drag them into a new order.

3. When you complete your changes, click Save.

An unused, disabled, or removed objects are shown in the Unused Reports list on the left of the Navigation editor.

Add new dashboards to a menu

  1. From the Navigation editor, select the new item from the list of Unused Reports at the left.
  2. Drag the report into the menu area and place it under a menu title. The existing menu items will shift to make room for the new item.
  3. Click Save.

For the list of dashboards that may be added to the menu bar using the Navigation editor, see the "Dashboard to data model" topic in this manual.

Custom Searches page

The Splunk App for Enterprise Security provides a wide range of searches for security analysis and management. Some search types are unique to the Enterprise Security app. The Custom Searches page is a status page used to display and configure all correlation, key indicator, and entity investigator searches.

Note: Some searches use a lot of memory. In order to reduce the amount of memory, remove the notable index (or summary index) from the list of indexes to be searched by default. See "Configure multiple indexes" in the Enterprise Security Installation and Configuration Manual for more information.


Actions

Browse to Configure > General > Custom Searches. Use the Actions column on the Custom Searches page to:

  • Enable or disable a correlation search
  • Change the default search type of a correlation search between scheduled and real-time.
  • Accelerate a key indicator search

Exporting Search content

The Custom Searches page provides an Export option that wraps the selected searches into an custom app for downloading. Use the Export option to migrate customized searches from a development or testing environment into production. The option to export content is restricted to the admin user by default. To add the export capability to another role, see "Custom capabilities" in the Installation and Configuration Manual.

1. Select the search content for export by clicking the selection box next to each search object.

2. At the bottom of the Custom Searches page, select Export.

3. On the Export Searches Into An App page, define the App Name, Label, Version, and Build number prerequisites.

4. Select the Export button.

5. When the dialog box states "Content successfully exported", choose the Download app now link to retrieve the app. The app is an archive file with the extension .spl.

6. Choose Close to return to the Custom Searches page.

Limitations to exported content

Exported content will only include the savedsearches.conf, correlationsearches.conf, and governance.conf settings for the selected objects. Any other artifacts referenced directly or indirectly will not be included.

Examples:

  • Exported content will include all defined alert actions, such as risk assignments, script names, and email addresses.
  • Exported content will remain on the search head after downloading, stored in the path: $SPLUNK_HOME/etc/apps/SA-Utils/local/data/appmaker/*.
  • Exported content will not include macros, script files, lookups, or any binary files referenced by the search object.
  • Exported content will not include Extreme Search objects, such as the context generating search, the contexts, or the concepts referenced by the search object.
  • Exported content may not work on older versions of the Enterprise Security app.
Last modified on 28 March, 2017
PREVIOUS
Key indicators
  NEXT
Security Posture dashboard

This documentation applies to the following versions of Splunk® Enterprise Security: 3.3.0, 3.3.1, 3.3.2, 3.3.3


Was this documentation topic helpful?


You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters