Cisco NX-OS policy examples
Rules for Cisco Nexus switches running NX-OS, one page per topic. Every rule has a passing config and a failing config, with the result rConfig gives for each. Run the rules against the output of show running-config.
| Topic | What the rules check | Rules |
|---|---|---|
| Management access | No Telnet, SSH not turned off, exec-timeouts of 1 to 10 minutes on the VTY and console lines, a MOTD banner | 5 |
| AAA | Login and accounting through a server group, password strength checking left on, AES encryption of stored keys | 4 |
| SNMP | No SNMPv1 or v2c communities, no MD5 SNMP users, encryption enforced for every user | 3 |
| Logging | A remote syslog server, millisecond timestamps, console logging no more verbose than critical | 3 |
| Services | CDP off globally, no proxy ARP or directed broadcast on any interface | 3 |
| Operational standards | Your NTP and syslog servers, a MOTD banner, a hostname pattern, an SNMP location | 5 |
Where the examples come from
Every topic documents one file from the Cisco NX-OS policy templates at release v1.5.0, which you can import into rConfig. The configs are sanitised excerpts of the two sample configs that come with the templates: a hardened and an unhardened Nexus 93180YC-FX on NX-OS 10.3(4a). Every config shown was run through rConfig Pro’s evaluator with its rule, and gave the result shown.
From NX-OS 10.3(2)F the switch prints only values that differ from the default. Several rules are written around that: they fail on the line that changes an insecure default, or need a value that is never the default. The management access page explains how this works for Telnet, SSH and the exec-timeouts.
The framework files (NIST, HIPAA and ISO/IEC 27001) collect these same rules, so they have no pages of their own here. See compliance frameworks.
If you are new to policy definitions, start with your first policy.