Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
The Log View tab allows you tocentrally view and filter the events of the activity and threat log of every connected CloudGen Firewall, thereby helping you to keep track of both actions performed by the firewall devices and threats. Use various filters, as described below, to tailor the information to your needs.
The information on the Log View page is divided into columns. To expand the view, drag the column header. You can also delete columns by clicking the delete icon (x) to the right of the header.
Accessing Firewall Information
The FIREWALL INFO column in the log window provides the following details related to access and application rules configured on firewalls:
OK – Normal operation
Fail – Connection failed
Terminate – Connection terminated
Drop – Packet dropped
Block – Connection blocked
Deny – Connection denied
Scan – Scan performed
Application Block – Application blocked
Expand the following section for detailed information:
To show events, go to LOG VIEW, and click MORE FILTERS on the top right.
The following filters are available:
Time Frame – Either choose a time frame from the drop-down menu to specify the time frame you want to show the data for, or specify a custom time frame. For a custom time frame, choose Custom from the drop-down menu, and enter the start and end date next to Start and End.
Devices – Select the devices you want to show the logs for.
Log Type – Choose between Threats / Webfilter and Firewall Connection History from the drop-down menu.
Additional Filters
Use the additional filters to narrow down the selection according to different criteria such as source, destination, protocol, and/or extended box descriptors. Filters are case insensitive and dependent on the field type. Wildcards are supported for all filter operators except IP Protocol, which only supports the equals (=) and not equals (≠) operators.
String/Text Fields
String/text fields (e.g., Firewall Rule, User, etc.) are case insensitive and dependent on the field type. Wildcards are supported for all operators. * or % indicates any quantity of bytes (including zero characters), so, in principle, 0-n characters. ? or _ indicates any one byte., in other words, exactly one character.
Examples:
ex*e will match 'Example', as does e%m%
examp?e will match 'Example', but ex_le will not match 'Example'
When you choose the equals operator (=) and enter Null as filter value, the field is not checked for the string 'Null', but if the field is Null. For example, if you choose Firewall Rule = NULL as filter, it is checked if fw_rule IS NULL. You can also choose the 'not equals' operator (≠) and enter Null (or null) as filter value. In this case, it is checked if the field is not null (e.g., fw_rule IS NOT NULL).
For string fields, the supported filters are as follows:
Filter
Description
equals (=)
Value must exactly match the filter (when no wildcards are used).
not equals (≠)
Value does not exactly match the filter (when no wildcards are used).
contains
Value contains the filter, e.g., 'example' contains the string 'xam'.
not contains
Value does not contain the filter, e.g., 'example' does not contain the string 'hello'.
starts with
Value must start with the filter, e.g., 'example' starts with 'exam'. This can also be achieved when using the equals operator with the * wildcard, e.g., exam*.
ends with
Value must end with the filter, e.g., 'example' ends with 'mple'. This can also be achieved when using the equals operator with the * wildcard, e.g., *mple.
Number Fields
Number fields (e.g., Port, Threat Severity, etc.) support only positive integer values, such as '1', '73', '8323', etc, but not '-12' or '7.3' or '8,2'. No wild cards are allowed. Checking for NULL/IS NOT NULL is possible when using the equals or not equals operator (see above section).
For number fields, the supporting filters are as follows:
Filter
Description
equals (=)
Value must exactly match the filter.
not equals (≠)
Value does not exactly match the filter.
greater than (>)
Value is greater than the filter.
less than (<)
Value is less than the filter.
A 'between' can be put into effect when using 'greater than' and 'less than' connected with an 'AND' conjunction (and one or two equals if you want the edge values to be shown).
