Skip to content
ConfigProof

All controls

ASA-SEC-005MediumCisco ASA

Entry covered by an earlier entry

At a glance

Base severity

Medium

Area

Security Policies

Platform

Cisco ASA

Evidence level

Derived0.90

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

The ASA applies the first entry that matches. An entry an earlier one covers is never evaluated, so a change made to it has no effect.

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 ASDM: Configuration > Firewall > Access Rules, delete the covered rule, or move it above the covering one if it was meant to win. Apply and save.
  2. On the CLI: no access-list <list> line <n> ..., or re-add it with access-list <list> line <n> above the covering entry, and write memory.

Command line

Cisco ASA CLI

configure terminalno access-list <access-list> line <line> <entry>endwrite memory

An example. Values in angle brackets are yours to supply; a finding on your own export fills in the names it read. Typed in configuration mode; write memory saves it, with no separate commit. Read every line first.

Read it back

show access-list <access-list>
Values to fill in3
<access-list>
The access list
<line>
The entry's line number in the list
<entry>
The entry's text after the line number, as the device shows it
Before you type it3
  • Written from the ASA 9.x command reference and not run on a device: read each line before you paste it.
  • In multiple context mode, type it in the context it applies to (changeto context <name>).
  • A configuration shows definitions and references, not traffic, so review this before you run it.

How to confirm the fix

  • Confirm the covering entry's logging is what the covered one intended.

Limits

  • Entries with source ports, time ranges, ICMP types or values the reading does not hold are not compared.

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