Skip navigation
All Places > Products > RSA NetWitness Platform > RSA NetWitness Platform Online Documentation > Documents
Log in to create and rate content, and to follow, bookmark, and share content with other members.

Investigate: Events View

Document created by RSA Information Design and Development Employee on Sep 18, 2017Last modified by RSA Information Design and Development Employee on Sep 8, 2020
Version 27Show Document
  • View in full screen mode
 

In the Events view analysts can view a sequential list of network, log and endpoint events, select an event for reconstruction and analysis, and view the raw event and metadata with interactive features that enhance the ability to see meaningful patterns in the data. In Version 11.5 and later, you can drill into metadata for the listed events. The Events view offers packet, file, host, text, log, and email reconstruction. When you open a web reconstruction of an event, the same web reconstruction used in the Legacy Events view is displayed.

Workflow

The following figure is a high-level workflow illustrating the tasks you can do in NetWitness Investigate, with the Events view tasks highlighted in red.

 

What do you want to do?

                                                               
User RoleI want to ...Show me how

Incident Responder or Threat Hunter

review detections and signals seen in my environment

NetWitness Platform Getting Started Guide

Incident Responder

review critical incidents or alerts

NetWitness Respond User Guide

Threat Hunterquery a service, metadata, and time range*

Begin an Investigation in the Events View

Begin an Investigation in the Navigate or Legacy Events View

Threat Hunter

view metadata*

Filter Results in the Navigate View

Drill into Metadata in the Events View (BETA)

Threat Hunter

view sequential events*

Filter Results in the Events View

Filter Results in the Legacy Events View

Threat Hunter

reconstruct and analyze an event*

Examine Event Details in the Events View

Reconstruct an Event in the Legacy Events View

Threat Hunterexamine files and associated hosts*

Download Data in the Events View

Export or Print a Drill Point in the Navigate View

Export Events in the Legacy Events View

Threat Hunterperform lookups*

Look Up Additional Context for Results

Launch a Lookup of a Meta Key

Threat Huntercreate an incident or add to an incident*

Add Events to an Incident in the Legacy Events View

Add Events to an Incident in the Events View

Threat Hunter

add a meta value to a Context Hub list*

Look Up Additional Context for Results

*You can perform this task in the current view.

Related Topics

Quick Look

There are multiple access points to this view, which are described in Begin an Investigation in the Events View. If you access the Events view from the Respond view, you can see the analysis for a selected event in an incident. The options are a subset of the options available when you open an event from within the Investigate view. To get complete functionality and examine other events, you can go to the Event view directly (INVESTIGATE > Event ).

The Events view lists events in ascending order by time in the Events panel. The events displayed can be results for the drill point in the Navigate view or Legacy Events view, or results for a query entered in the Events view query bar.

Input fields for a query are displayed so that you can select a service and time range, and type an optional query. When you submit a query, the service being investigated counts the results up to a limit of 10,000 events, and 10,000 network, log, and endpoint events are loaded in the Events panel. Different columns are displayed, depending on the selected column group. You can rearrange and resize the columns, choose a built-in or custom column group, and choose individual columns that you want to see. When you find an event of interest, clicking the event opens the reconstruction in a new panel (Packet, Text , or File).

Note: For versions earlier than 11.3, the first 100 events are loaded. You can scroll through the list and click Show Next 100 Events at the bottom of the list. If the next page contains fewer than 100 events, the button changes to reflect the number of remaining events.

The following figure highlights the major features of the Events view for Versions 11.4.1 and later.

This figure illustrates the changed elements in Version 11.5 and later.

Version 11.5 updates to the Events view

                                                                 
1Query Bar: When a service is selected, displays the service selector, time range selector, and the queries you have entered. You can select a service as described in Begin an Investigation in the Events View and refine the query as described in Filter Results in the Events View. Clicking the submit query icon submits the query and sends a request to the selected service to load the data. In Version 11.3 and later, clicking the the query console icon (console icon) opens the query console, where detailed status of the query is provided (see Events View below).
2

The type of event being analyzed and the type of reconstruction are reflected in the heading.

  • These are the event types: Network Event Details, Log Event Details, or Endpoint Event Details.
  • The types of analysis available for the event type are Text, Packet, File, Host, Email, and Web. Network events can use all types of analysis: text, packet, file, and email (Version 11.4.1 and later). Log and endpoint events use only text analysis. The email (Version 11.4.0.x and earlier) type and web type open the current event as an email or web reconstruction in the Events view. For details, see Examine Event Details in the Events View.
3Reopens the Events panel if you have closed it. For details, see Analyze Events in the Events View.
4Sets preferences for the Event view (see Configure the Events View).
5

The Events panel title.

  • In Version 11.3 and later, the Events panel title is slightly different than the title in prior versions, and a row number indicator has been added. The title lists the number of events and sort order; for example, 24,000 Events (Asc) means that 24,000 events were found and they are listed in ascending order by time. If more than 10,000 events are found, only the oldest 10,000 events are displayed in ascending order, and an amber triangle highlights the fact that not all events were loaded. This may indicate that you need to refine the query. For more information about refining the events listed here, see Filter Results in the Events View.
  • Versions prior to 11.3 simply list the number of events found, and you can load 100 of them at a time. In Version 11.4 and later, clicking the search button opens the Find Text in Table dialog.
6The Column Group drop-down lists built-in and custom column groups that you can apply to the Events panel. Built-in column groups are sometimes updated between one version and the next. Some examples of built-in column groups are Email, Endpoint Analysis, Malware Analysis, Outbound HTTP, Outbound SSL/TLS, and Summary List. Summary List is the default column group. For details, see Use Columns and Column Groups in the Events List.
7The Download drop-down menu lists the available options for downloading event data. The options are Log, Visible Meta, and Network (see Downloading and Acting Upon Results. You can change the preferred format of the event type data in the Event Preferences dialog (see Configure the Events View).
8

The Create Incident button enables you to create incidents from events. The Add to Incident button enables you to add selected events to an open and existing incident (see Add Events to an Incident in the Events View and Add Events to an Incident in the Legacy Events View).

9 Displays the column selection settings to select the individual columns displayed in the Events panel. For details, see Use Columns and Column Groups in the Events List.
10

Controls to show or hide the Event Header, show or hide requests and responses, and open the Event Meta panel. For details, see Analyze Events in the Events View.

11 Controls to change the size of the panel and close the panel. For details, see Analyze Events in the Events View.
12

The Event Header provides summary information about the event you are currently analyzing. The selected event is highlighted in the Events panel with a blue background. The summary information is different for the different event types (packet, log, and endpoint). In Version 11.5, the redundant NW Service is removed.

13

The event data for the event you are currently analyzing.

14

The Event Meta panel is redesigned in Version 11.5, but has the same functions as in Version 11.4. The Event Meta panel lists the meta keys and values found in the data. This data can be sorted in two ways - Alphabets or Sequence. Some metadata are searchable; they have a binoculars icon, which you can click to see the associated data highlighted in the event data (see Analyze Events in the Events View).

  • For a packet, the data is called a payload and is displayed in the form of a request and response.
  • For a log event, the data is a line of text from the raw log.
  • For an endpoint event, the event data is relevant to data from the NetWitness Endpoint agents running on hosts in the network. It may be a single process, driver, DLL, file (executable), service, or autorun, and information related to logged-in users. (See the NetWitness Endpoint User Guide for complete information about endpoint event data.)
15The Version 11.5 main menu for RSA NetWitness Platform has relocated Hosts, Files, and Users (Entities) options for easier access.

Filter Events Panel

The Filter Events panel is a beta feature added to Version 11.5. Clicking the Filter button (the Filter button) in the Events panel. opens the panel to provide a view of meta keys and meta values found in the data set. See Drill into Metadata in the Events View (BETA) for more information about drilling into metadata.

Note: Sometimes the total event counts differ between Filter Events panel and Events panel. TheFilter Events paneluses only index data to produce counts of events, and the event count is less accurate than the event count in the Events panel. The Events panel results are filtered for exact matches on data retrieved from the meta database, which takes longer to process. At worst the difference is in false positives in the Filter Events panel, not false negatives; so you will not miss an event."

 

The initial view of the Filter Events panel

                     
Meta Groups Menu

With the Filter Events panel open, you can select a meta group to define the meta keys displayed in the Filter Events panel.The Default Meta Keys meta group is in effect the first time you log in. If you selected a different meta group the last time you logged in, it remains in effect until browser cache is cleared. See Use Meta Groups to Focus on Relevant Meta Keys for details about meta groups.

Ordering Menu

With the Filter Events panel open, you can look at two parameters for each value: the event count or the event size. Each meta key entry includes either the event count or the event size in parentheses after the value. In both cases, there are four options for ordering:

  • By default, the meta keys are displayed using the Event Count > Descending by Total Count method. When showing the event count for each value, you can order by Descending by Total Count, Ascending by Total Count, Ascending by Value, and Descending by Value.
  • When you prefer to see the size of the event that contains the value, you can use one of the four Event Size ordering options: Descending by Total Size, Ascending by Total Size, Ascending by Value, and Descending by Value.
Meta Key options button
(
the Meta Key options)

The Meta Key options button offers actions that you can take on an individual meta key. In Version 11.5, the only action is to copy all of the visible meta values for a meta key.

Meta Key List

An icon before each meta key name identifies the indexing method for the key. The indexing method determines the types of interactions and queries possible using that meta key.

  • This meta key is indexed by value: a meta key indexed by value. The green color indicates that the all available interactions and queries are supported. You can see the available interactions in the context menu by right-clicking the meta value.
  • This meta key is indexed by meta key: a meta key indexed by meta key. The yellow color is a clue that a subset of available interactions is supported, and queries on this meta key may take longer than meta keys that are indexed by value. You can see the available interactions in the context menu by right-clicking the meta value.
  • This meta key is not indexed: a non-indexed meta key. Values for non-indexed meta keys cannot be used to query. If you want to query a meta key that is not indexed, your administrator needs to edit the index file for the service to index the meta key by value or meta key.

Query Console

Clicking the query console icon (the console icon) opens the query console, where detailed status of the query is provided.

example of the query console after a query has completed

In the query console, you can see which service, time range, and metadata was queried as well as real-time information about the status of the query and the services being queried. A progress bar indicates the query's completion percentage at the bottom of the console. The statuses let you know details about what is happening; for example, you can tell when the query is executing, queued, reading the index file for the queried service, retrieving events, and complete. All statuses and non-fatal messages are displayed as they come in, and the border color changes if a non-fatal error occurs. View Status of a Query provides additional details on this subject.

Several messages that may be displayed in the query console require additional explanation.

Message: Maximum value limit (valueMax) of %1% reached on meta key %2% in index slice %3%

Explanation: The valueMax property on the specified meta key has been reached in the index being queried. An administrator configures this inside the index files available in ADMIN > Services > [Service Name] > Files > index-[service type].xml or index-[service type]-custom.xml. As an example, the statement below from the index file states the meta key called client has a limit of 250,000 values by default.

<key description="Client Application" level="IndexValues" name="client" format="Text" valueMax="250000" />

Message: The query on channel %2% was auto-canceled by the system for exceeding time usage limits. Check timeout values.

The server has a per-operation limit on execution time, and the requested operation exceeded the limit. To avoid this error, split the operation into smaller pieces, such as smaller time ranges.

Memory limit of %1% reached, controlled by setting max.query.memory

The server has a per-operation limit on memory utilization, and the requested operation exceeded the limit. The limit is related to the amount of memory in the server, which an administrator can adjust in ADMIN > Services > [Service Name] > sdk > config. To avoid this error, split the operation into smaller pieces, such as smaller time ranges.

Quick Look for Version 11.0.0.x (End-Of-Life)

The following figure highlights the major features of the Event Analysis view for Version 11.0.0.x.

the Event Analysis view in Version 11.0

                                                 
1 The read-only breadcrumb displays the selected service, time range, and query entered in the Navigate view or Events view.
2This is a read-only list of events based on the query made in the Navigate or Events view. The Events panel includes a count of the events. You can rearrange and resize columns. You can scroll to the bottom of the list, and load more events (see Analyze Events in the Events View).
3, 8Controls to change the size of the panel and close the panel.
4The type of event being analyzed is reflected in the heading: Network Event Details, Log Event Details, or Endpoint Event Details. Each view is discussed in detail in Analyze Events in the Events View.
5The types of analysis available for the event type. Network events can use all three types of analysis: text, packet, and file. Log and endpoint events use only text analysis.
6These options vary for the different types of analysis. They are discussed in detail in Analyze Events in the Events View.
7

Controls to show or hide the Event Header, show or hide requests and responses, and open the Event Meta panel (12). These controls are described in Analyze Events in the Events View.

9Reopens the Events panel or the Event Meta panel if you have closed it.
10The Event Header provides summary information about the event. This information is different for the different event types (packet, log, and endpoint).
11The event data (sometimes called a payload for packets). The event data for a log event or endpoint event is typically a line of text from the raw log rather than request and response shown for a packet.
12The Event Meta panel lists the meta keys and values found in the data. Some meta data are searchable; they have a binoculars icon, which you can click to see the associated data highlighted in the event data (see Analyze Events in the Events View.

You are here
Table of Contents > Investigate Reference Materials > Events View

Attachments

    Outcomes