Skip to content
ConfigProof

All controls

FTD-SEC-002MediumCisco FTD

Default action does not log

At a glance

Base severity

Medium

Area

Security Policies

Platform

Cisco FTD

Evidence level

Fact1.00

Benchmark reference

Reads the export, not the device

ConfigProof reads a configuration export. This control is evaluated against the objects in that file, and it reports what the file says. It does not connect to the device and sees no traffic, so a finding here describes the configuration, not what the firewall is doing right now.

Why it matters

Connections the default action drops or allows leave no event, so blocked attacks and gaps in the rules cannot be seen or investigated.

How to fix it

Web interface

The steps below are written for the web interface. A finding raised on your own export carries the same steps with your object names filled in.

  1. In FMC (or cdFMC): Policies > Access Control > edit the policy > logging icon beside Default Action > Log at Beginning of Connection (Block) or End (Allow) > Event Viewer and/or Syslog Server. Save, Deploy.
  2. In FDM: Policies > Access Control > Default Action > Connection Events: log at beginning or end, then Deploy.

Command line

This analyzer version writes no command text for this control. The steps above are the remediation it offers.

How to confirm the fix

  • On the FTD CLI (read only): show access-control-config, and confirm the default action's logging is enabled.

Limits

  • No limitation is recorded for this control beyond the one that applies to all of them: it reads a configuration export.

Compliance references

No benchmark recommendation is mapped to this control in this version.

More in Security Policies

See it on your own firewall

One complete analysis of one firewall costs nothing. A card is required and nothing is charged.

Start a free analysis