Log Data Center Traffic That Matches No Interzone Rules

By default, the firewall denies traffic between data center zones (interzone traffic) that matches no Security policy allow rule. Log and examine this traffic to identify attempted attacks and also traffic you may want to allow.
Traffic that doesn’t match any of the Security policy rules you configure matches the predefined interzone-default rule at the bottom of the rulebase and is denied. To gain visibility into traffic that doesn’t match a rule you explicitly configured, enable logging on the interzone-default rule. Logging this traffic gives you the opportunity to examine access attempts that you have not explicitly allowed, which may identify attack attempts or traffic for which you want to modify an allow rule.
  1. Select the interzone-default row in the rulebase and click
    to enable editing the rule.
  2. Select the
    rule name to edit the rule.
  3. On the Actions tab, select
    Log at Session End
    and click
  4. Create a custom report to monitor traffic that hits this rule.
    1. Select
      Manage Custom Reports
    2. Add
      a report and give it a descriptive
      . In this example, the name is
      Log Interzone-Default Rule
    3. Set the
      Traffic Summary
    4. Select the
    5. From
      Available Columns
      , add
      Risk of App
      , and
      to the
      Selected Columns
      list. If there are other types of information you want to monitor, select those as well.
    6. Set the desired
      Time Frame
      Sort By
      , and
      Group By
      values. In this example, the selected values are
      App Category
      , respectively.
    7. Define the query to match traffic that matches the interzone-default rule:
      (rule eq interzone-default)
      The resulting custom report settings look like this:
    8. Commit
      the changes.

Recommended For You