Investigation: Navigate View

Document created by RSA Information Design and Development on Jul 28, 2016
Version 1Show Document
  • View in full screen mode
 

The Navigate view displays the activity and values for the selected service in accordance with the Investigation options in the Options panel: profile, time range, meta group, and query. As analysts investigate events of interest, the meta keys and values are displayed.

To access the Navigate view, select Investigation > Navigate in the Security Analytics menu. When a service investigation is open, the view is similar to the figure below.

NavVwBrok.png

Features

The Navigate view consists of these:

  • Toolbar
  • Pause/reload button and breadcrumb
  • Time banner
  • Optional debug information.
  • Collapsible Visualization panel
  • Values panel

Toolbar

NavVwTb.png

The toolbar provides a way to:

  • Change the service being investigated.
  • Control the range of data displayed: You can select use profiles, set a time range, use meta groups, and create queries to apply to the data.
  • Set the quantification method and sorting method for data in the Values panel.
  • Perform actions on the results. You can export and print results, navigate to an event for which you have an event ID, and pass a query to Informer.
  • Configure Investigation settings without navigating away from the Investigation views.

Some of the toolbar options are labeled with the default value or the selected value rather than displaying the name of the option. For example, the time range option in the example above is labeled Last 3 Hours to reflect the currently selected value. The following table describes the tool bar options.

                                        
OptionDescription
ServIcon.pngDisplays the selected service name next to the icon. Clicking the icon opens the Investigate a Service dialog, in which you can select a service to investigate and set the default service to investigate (see Begin an Investigation). Changing the service does not cause a reload of the data.
Time RangeDisplays the Time Range options; the currently selected option is displayed in the toolbar (see Set the Time Range for an Investigation). Possible choices are:
  • All Data
  • Last 5, 10, 15, or 30 Minutes
  • Last Hour, Last 3, 6, 12, or 24 Hours
  • Last 2 or 5 Days
  • Early Morning
  • Morning
  • Afternoon
  • Evening
  • All Day
  • Yesterday
  • This Week
  • Last Week
  • Custom 

Note: If you specify custom start or end times in seconds, the value for start time in seconds will always default to :00, and the value for end time in seconds will always default to :59. For example, if you are using time to drill down into an issue, the drill time will be interpreted as "HH:MM:00 - HH:MM:59." Seconds display in this format in Investigation > Navigate functions.

QueryDisplays the Query dialog, in which you can enter a custom query directly instead of drilling down the data. See Query Dialog for a description of the dialog.
ProfileDisplays the Profile menu; the currently selected profile is displayed in the toolbar. A profile allows you to manage and use profiles that can include custom meta groups, a default column group, and a beginning query. The Profiles apply to the Navigate view (meta groups and queries) and the Events view (column groups and queries). See Use Investigation Profiles to Encapsulate Custom Views for more information.
MetaDisplays the Meta Group menu. You can use Default Meta Keys or a custom Meta Group. You also have the option to make changes to both group types (see Manage User-Defined Meta Groups).
Sort FieldDisplays the Sort Field menu; the currently selected option is displayed in the toolbar. The menu has two options: Order by Total and Order by Value. The Sort Field is a complement to the Sort Order option; the data for each meta key is ordered based on the total (green number) or the meta value (blue text) (see Set Quantification Method and Sort Sequence of Meta Key Results).
Sort OrderDisplays the Sort Order menu; the currently selected option is displayed in the toolbar. The menu has two options: Sort in Ascending Order and Sort in Descending. The Sort Order is a complement to the Sort Field option; the selected field for each meta key is ordered in ascending or descending order (see Set Quantification Method and Sort Sequence of Meta Key Results).
Quantification MethodDisplays the Quantification Method menu; the currently selected option is displayed in the toolbar. The drop-down menu contains three options for calculating the quantity (green number in parentheses) for a meta value: Quantify by Event Count, Quantify by Event Size, and Quantify by Packet Count (see Set Quantification Method and Sort Sequence of Meta Key Results).

These are applied differently depending on the type of data in view.

For packet data:
  • Quantify by Event Count shows the number of sessions.
  • Quantify by Event Size shows the size in bytes.
  • Quantify by Packet Count shows the number of packets.
For log data:
  • Quantify by Event Count shows the number of logs.
  • Quantity by Event Size shows the size in bytes.
  • Quantify by Packet Count shows the number of logs.
ActionsThe Actions menu includes various actions (Visualize, Go To Event, and Print) that you can perform in the Navigate view (see Act on a Drill Point in the Navigate View).
Save EventsDisplays the Save Events menu, in which you can use options to:  extract files associated with an event, export the current drill point as a PCAP file, and export the current drill point as a log file (see Export a Drill Point).
SettingsDisplays the Investigation settings for the Navigate view (which are also editable in the Profile view) so that you can change Investigation settings without navigating away from the Navigate view. When you change a setting In the Navigate view the setting is also changed in the Profile view (see Configure Navigate View and Events View).

Pause/Reload Button and Breadcrumb

The breadcrumb tracks each query as you drill down through the metadata for the service. Each query is listed with a drop-down menu in a pipe separated string. The last point is the current point, also called the tip. The icon in front of the breadcrumb allows you to pause the loading of meta values and to reload meta values.

The breadcrumb does not include the service name and appears only if a query is in effect. If too many drill points exist for display, the overflow is shown as double angle brackets, >>, at the end of the breadcrumb.

Each drop-down menu in the breadcrumb is the same, with slight variation based on the position of the crumb.

104BCMenuEnd.png

The following table describes the controls and menu options in the breadcrumb.

                               
FeatureDescription
104LoadVis.png
Pause and Reload button
Controls the loading of data in the view. It has three possible functions: pause loading, continue loading, and reload.
Navigate HereOpens the selected drill point in the current Values panel.
Navigate Here (new tab)Opens the selected drill point in a new tab.
Insert BeforeInserts a query before the current drill point. The Create Filter dialog opens and you can define a custom query to insert in the breadcrumb (see Create a Custom Query).
AppendAppends a query after the current drill point. The Create Filter dialog opens and you can define a custom query to append to the end of the breadcrumb (see Create a Custom Query).
RemoveRemoves the selected drill point from the breadcrumb.
EditOpens the selected drill point in the Create Filter dialog so that you can edit the query.
>>Clicking the angle brackets displays a drop-down menu of the breadcrumb overflow.

(Optional) Debug Information

If you have activated the Show Debug Information setting and the service you are navigating is a 10.4 Broker, Security Analytics displays the debug information beneath the breadcrumb.

104debuginfo.png

The debug information is the where clause from the current query. The only time there is no where clause is when the time range is all data and there are no drill points. If the Broker has at least one aggregate service that is offline, the debug information also lists the offline service.

For example:
(attachment exists)&&(tcp.dstport = '80')&&(risk.info exists)$$time='2014-05-04 18:50:00"-"2014-05-09 18:59:59(attachment exists) && (tcp.dstport = '80') && (risk.info exists) && time="2014-05-04 18:50:00"-"2014-05-09 18:50:59"

In addition, the time to load is displayed at the end of each meta key in the Values panel.

Time Banner

Just below the breadcrumb and debug information (if present), the time banner shows the time range used to create the chart.

104timebanner.png

Visualizations

At the top of the Navigate view is a visualization of the current drill point. You can use this to drill into data from the Visualization panel (see Drill into Data in the Navigate View Time Chart). You can show or hide the visualization, and choose one of the the visualization options: Timeline or Coordinates. The Visualization opens initially to the last saved Visualization.

Timeline Chart

The timeline displays activity for the specified service and time range, as a line chart or a bar chart based on your choice in the Options menu. The second figure illustrates a line chart and third figure illustrates a bar chart.

VisOptTimeLineDg.png

timelineLIneChart.png

timelineBarChart.png

                            
FeatureDescription
Number of Events (Timeline)The Y axis of the chart based on thousands of events.
Time Line (Timeline)The X axis of the chart based on the time the events occurred.
Event point (Timeline)If you want to explore a specific section, simply select the range from the chart. The new time range will be reflected in the chart.
Investigate (Timeline)Displays the meta values for the selected subset.
Reset Zoom (Timeline)To return to the original time range, click Reset Zoom.
OptionsDisplays the Visualization Options dialog. Data points can be displayed as a Line chart (default), a Bar chart, or Coordinates chart. When a chart type is select, the relevant options are displayed.
HideCollapses the chart.

Parallel Coordinates Chart

The Parallel Coordinates chart is one of the choices in the Options menu for visualizing the current drill point. With Coordinates selected in the Visualization Options dialog, you can select the meta data to be displayed (see Visualize Metadata as Parallel Coordinates).

NavVwVisCoord.png

                         
FeatureDescription
AxesEach axis is a meta key. The number of meta keys affects the load time for the chart. All meta keys are loaded, but it there the number of events per meta key is limited.
LineLines represent events and they connect values on the axes to show the correlation between multiple meta keys.
OptionsDisplays the Visualization Options dialog. Data points can be displayed as a Line chart (default), a Bar chart, or Coordinates chart. When a chart type is select, the relevant options are displayed.
Only a subset of events is displayed.This message is a notification that not all events in the values panel are drawn in the chart. Removing axes or filtering the data in the Values panel can help to display all events.
Events Found | Unique PathsDisplays the total number of events charted versus the number of unique paths charted. Setting the All Meta Keys Must Exist in an Event option  redraws the chart so that it is more targeted and legible.
DNEIndicates that there is no values for this meta key in the event. 

In the Visualization Options dialog for Coordinates, you can select the meta keys to chart.

VisOptDgInfo.png

                                  
FeatureDescription
Visualization selectionDisplays a drop-down list of visualization types: Timeline and Coordinates
All Meta Keys Must Exist in an EventLimits the data represented in the visualization to only those events that include all selected meta keys. This can result in a cleaner, more targeted visualization.
Icon-Add.pngDisplays the Add Keys to Parallel Coordinates Visualization dialog so that you can add axes to the visualization. This is useful if you are looking for relationships between the default meta keys and some additional ones.
ic-delete.pngDeletes the selected keys so that they do not appear as axes in the visualization. This can help to make the visualization less cluttered and allow for more data points to be included in the visualization.
ic-Revert.pngReverts to the default meta keys for visualization, which consist of all meta keys in the current drill point.
ic-info2.pngControls the display of additional information about the number of selected axes versus the recommended count. This helps to make you aware of possible performance improvements by removing axes.
Axes listLists the meta keys selected as axes in the visualization.
CancelCancels any changes made to the visualization options.
ApplySaves the changes made to the visualization options and applies to the current visualization.

In the Add Keys to Parallel Coordinates Visualization dialog, you can select the meta keys or meta groups to use as axes the Parallel Coordinates visualization.

AddKeysPCDg.png

                   
FeatureDescription
Select Keys:Two options for selecting meta keys are:
  • From Default Meta Keys
  • From Meta Groups
Each option offers a drop-down list from which to select.
With the Selected Meta Keys...The options for the method of adding meta keys allow you to:
  • Replace the current list of keys
  • Append to the current list of keys
  • Insert at beginning of the current list of keys
CancelCloses the dialog and does not add any keys.
AddCloses the dialog and adds the selected keys as specified.

Values Panel

The major feature of the Navigate view is the Values panel, which you can use to analyze data (see Drill into Data in the Navigate View Time Chart). The first figure below illustrates the Values panel in normal mode; the second figure illustrates the added information when the Show Debug Information setting is active.
NavVwNoDebug.png

NavVwShowDebug.png

The default view is for the last 3 hours of collection, using the default meta keys and non-indexed meta keys closed. The meta keys within the meta groups are displayed in the order that Security Analytics queries the keys. As the data loads into the Values panel, Security Analytics is optimized to show partial results, loading progress, and service status as the data loads.

The loading behavior is determined by several configuration settings. The highest level settings are configured by the administrator for each user. These are:

  • The maximum amount of time allowed for this user to run a query (Query Timeout).
  • The limit at which Security Analytics stops counting the number of meta values in a session (Session Threshold). If a threshold is set for a session, the Navigation view shows that the threshold was reached and the percentage of query time used to reach the threshold.

Note: The values for non-indexed meta keys take longer to load in the Values panel. To optimize loading, Security Analytics does not open non-indexed meta keys by default. Refer to Manage and Apply Default Meta Keys in an Investigation for a detailed description of non-indexed meta keys in Investigation.

When you have launched an investigation of a service, Security Analytics displays results in the Values panel.

  1. Security Analytics loads meta keys and meta values in the Values panel. For each meta key load, the stages of load are:
    1. Waiting to Be Loaded or Closed. If Closed, no data for that key is loaded.
    2. Loading
      1. Loading progress: Security Analytics is receiving and displaying progress messages.
      2. Partial results: Security Analytics is receiving values messages and partial results are displayed in the Values panel.
    3. Load Complete:  All results are finished loading.
  2. As each meta key load is completed, and final values are displayed, the next meta key is started. The number or values rendered for each meta key is specified by the Render Threads value in the Investigation Preference settings. Loading continues until all keys to be loaded have finished.
  3. If Show Debug Information is active and the service you are navigating is a 10.4 Broker, Security Analytics displays load time information beneath the values for each meta key and displays additional load details for the aggregated services. Security Analytics also displays the debug information beneath the breadcrumb.

Iterative results

Iterative results provide feedback on the status of queries within the interfaces to provide additional context for how long the data load will take and if any service data is missing. For example, if you are querying a Broker that is aggregating from two Concentrators, Security Analytics starts displaying the results from the first Concentrator as soon as it is available, even if the second Concentrator is still waiting for results.
Iterative results also include a notification that service data is missing because the service is unreachable.

IterativeResu.png

Partial results

When partial values from the Core service are returned but not completed, a message at the end of the meta key listing shows the progress of values loaded. In the example below, Currently looking at 38 ip.src values 71% indicates that loading of values for the meta key is 71% complete.

104NavPartResults.png

Debug Information

If the Show Debug Information setting is in effect, a field at the end of the values displays the status for the different systems against which you are querying within Security Analytics. For example, when you are querying against a 10.4 broker pulling from multiple concentrators, Security Analytics displays the status of the query on each of the Concentrators, which provides insight into the relative speed of data loading from each of the Concentrators. Each service that participated in the query is listed with the total elapsed time for the query.

InvDebu.png

Each service that participated in the query is listed with the total elasped time for the query. In the example above, two services returned in 3.207 seconds, localhost:50005 took 2 seconds to return the results. In addition, the where clause of the query is displayed below the breadcrumb. You can copy this syntax directly into an application rule or Reporting Engine where clause of a rule.

Load Complete

This is an example of values that have finished loading.

InvNoDebug.png

For each meta key, there is a list of values (blue text) and counts (green text) found in the current drill point. When you click a value to drill down into a subset of the currently selected data, the display is updated and the new drill point is recorded in the breadcrumb. You can specify the sorting and quantification methods for the values list using the option in the toolbar.

Note: Title, values, and counts for non-indexed meta keys are not drillable; the Values and counts are shown in black. Refer to Manage and Apply Default Meta Keys in an Investigation for a detailed description of non-indexed meta keys in Investigation.

                                           
FeatureDescription
Meta KeyThe name of the meta that is listed, for example, Service Type is a meta key.
Number of values rendered vs number of values available to loadThe number or values rendered is specified by the Render Threads value in the Investigation Preference settings. In the example above, the meta key is Service Type, and 20 of 20+ values are currently displayed. You can display additional values by clicking ...show more.
104InvSearch.pngClicking 104InvSearch.png on an indexed meta key opens the Search dialog in which you can enter a filter for the current meta key. The search function is not available for non-indexed meta keys, and is based on the actual meta value rather than the alias. Drilling in the Search dialog using aliases is not supported.

NOTE: Check with your administrator to obtain a list of aliiases used for a meta key in Investigation. When an alias is used, this search dialog does not provide results. Instead, you must query the meta key using the Right-click query capability or the Query dialog.
104InvSearchDg.png
Offline Services: xxx.xxx.xxx.xxx:50004Lists offline services queried by a 10.4 Broker.

Meta Count, for example

The number of instances found for a particular meta in the session.

Meta Value, for example

The specific name associated with the found meta.
...show moreIf the number of meta values has been limited (for example, 20), clicking this displays additional meta values for the selected meta key.
Loaded in 0.418 secs. Total running time 0.434 secs. (localhost:50005 loaded in 1 secs....Debug stats display load times based on the Show Debug Information setting.

Meta Key Context Menus

The Meta Keys in the Values panel have context menus. Next to each meta label, a drop-down arrow displays the options that can apply to that item. You can use these to change the way the results for the meta key are displayed in the current view. Changes made to meta keys are displayed in the current view during drill points persist until you refresh the page or select a new service in the Navigate view toolbar. A refresh reverts the current view of meta keys as defined in the Manage Default Meta Keys dialog (see Manage and Apply Default Meta Keys in an Investigation). If you have never made modifications in the Manage Default Meta Keys dialog, Security Analytics restores the default meta keys from the core service.

  • More Results
  • Max Results
  • Hide Results
  • Meta Key Info
You are here: Investigation Reference Materials > Navigate View

Attachments

    Outcomes