The Observations page describes the runtime events that do not violate a policy or that are not considered to be an attack. These can be normal runtime behavior where the events may impact the security, but any malicious intent is not determined. For example, an application opening a file outside the application directory causes Observed state. You can use this information in investigating incidents to understand the historical behavior of an application and in defining the runtime policy.
The Observations page includes these details:
Name | Description |
---|---|
ID | The ID of the corresponding Observation. Cisco Secure Application generates this ID. You can modify this ID on the Observation details page. To view the Observation details page, click the desired row. Click this field to sort the ID alphabetically. |
Source | The source of the corresponding Observation. This provides information on these types of the observation:
Click this field to sort the values alphabetically. |
Events | The type of the observation and count of that observation type. |
Observation Type | Observation types include:
|
Application | The application affected by the observation. |
Tier (Nodes) | The tier name and the number of nodes. You can click to launch the application flow map in the |
Last Detected | The time that is elapsed since the last event within the observation. Click this field to sort the values in ascending or descending order. |
You can click the Export button to download the table data. It downloads all of the rows, columns, and related data in a .csv
file. A separate .json
file includes the following: link to the Cisco Secure Application website where the table is exported from, global filters (if any) applied to the pages, and search filters applied to the columns. These two files are compressed into a .zip
file for downloading. The maximum number of rows that can be exported is 10,000. If table data exceeds 10,000 rows you may apply filters to narrow your search, or export the first 10,000 results.