Security

How to read a device's management access posture

Management exposure is not one setting. It is the sum of which services answer, whether they are encrypted, whether they are confined to a management VRF, whether logging in is authenticated centrally, and whether an idle session ever closes. Read individually those checks look like housekeeping. Read together for one device they describe how someone would get in, and that is the reading worth learning.

The same procedure as a recording, subtitled in English and French.
Before you start

What you need

  • Module required: compliance.
  • Permission required: view_audit.
  • All benchmarked platforms; check names and counts differ by vendor

1. Open the worst-scoring device

app.nactrack.com/compliance/device/12122
Open the worst-scoring device
This one fails every check that was run against it. That pattern is characteristic: it is not a device that drifted, it is a device that was never brought onto the standard build in the first place.

2. Read the checks together

app.nactrack.com/compliance/report
Read the checks together
Note which way this check points. It does not say a service should be turned off; it says the SSH server should be enabled and is not. Combine that with the Telnet server being active and you have the whole story: the only way onto this device is the unencrypted one.

3. Follow it to the terminal lines

app.nactrack.com/compliance/report
Follow it to the terminal lines
The terminal lines confirm it. This check wants the VTY sessions restricted to SSH alone, and it is failing, so the lines accept whatever the device offers. Three findings that each look minor on their own have now described a complete path in.
The limits

What this view does not tell you

  • A benchmark is a shipped opinion about a platform, not your organisation's policy. A device that deliberately runs a service your standard permits will still be reported as failing until the check is waived.
  • Check counts are not comparable between vendors. One platform's benchmark may run thirty checks and another sixty, so a lower score does not automatically mean a worse device - compare a device against its own platform's baseline.