Step 5: Enable Logging for Traffic that Doesn’t Match Any Rules

Traffic that does not match any of the rules you defined will match the predefined interzone-default rule at the bottom of the rulebase and be denied. For visibility into the traffic that is not matching any of the rules you created, enable logging on the interzone-default rule:

Select the interzone-default row in the rulebase and click

Override

to enable editing on this rule.

Select the

interzone-default

rule name to open the rule for editing.

On the

Actions

tab, select

Log at Session End

and click

Create a custom report to monitor traffic that hits this rule.

Select

Monitor

Manage Custom Reports

Add

a report and give it a descriptive

Name

Set the

Database

Traffic Summary

Select the

Scheduled

check box.

Add the following to the Selected Columns list:

Rule

Application

Bytes

Sessions

Set the desired

Time Frame

Sort By

and

Group By

fields.

Define the query to match traffic hitting the interzone-default rule:

(rule eq 'interzone-default')

Commit

the changes you made to the rulebase.

Document:Internet Gateway Best Practice Security Policy

Step 5: Enable Logging for Traffic that Doesn’t Match Any Rules

Table of Contents

Step 5: Enable Logging for Traffic that Doesn’t Match Any Rules

Most Popular

Recommended For You

Document:Internet Gateway Best Practice Security Policy

Step 5: Enable Logging for Traffic that Doesn’t Match Any Rules

Table of Contents

Step 5: Enable Logging for Traffic that Doesn’t Match Any Rules

Most Popular

Recommended For You

Recommended Videos