Arista EOS policy templates
Policy templates for Arista switches running EOS, from the arista/ folder. They check the configuration as returned by show running-config: top-level commands in column 0, sub-commands indented three spaces per level, and each block closed by a ! line. This page documents release v1.5.0. See importing a policy template to load one into rConfig.
For worked examples of these rules, with a passing and a failing config for each, see the Arista EOS platform pages.
Hardening definitions
EOS management access
pro-policy-definitions / arista /eos-management-access.policyView on GitHub- Kind
- Hardening
- Rules
- 4
- Minimum rConfig
- 8.3.0
- Release
- v1.5.0
No Telnet, an SSH idle timeout of 1 to 10 minutes, no weak SSH cipher or MAC, and a login banner.
| Rule | Method | What it checks |
|---|---|---|
| Telnet is not enabled (fails on no shutdown under management telnet) | must_not_match_regex |
No management telnet block has an indented no shutdown line, including under a vrf inside it. A switch that prints no management telnet block passes. |
| The SSH idle timeout is 1 to 10 minutes (idle-timeout under management ssh) | evaluate_block |
The management ssh block has an idle-timeout line with a value from 1 to 10. A switch with no management ssh block fails. |
| No SSH cipher or MAC line selects a CBC, 3DES, arcfour, blowfish, MD5 or SHA-1 algorithm (cipher, mac) | must_not_match_regex |
No indented cipher line names a CBC, 3DES, arcfour or blowfish cipher, and no indented mac line names hmac-md5 or hmac-sha1. |
| A login banner is configured (banner login) | must_match_regex |
The config has a banner login line. |
References
Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.
| Rule | NIST SP 800-53 | HIPAA (45 CFR) | ISO/IEC 27001:2022 |
|---|---|---|---|
| Telnet is not enabled (fails on no shutdown under management telnet) | AC-17 | 164.312(a)(1) | A.8.5 |
| The SSH idle timeout is 1 to 10 minutes (idle-timeout under management ssh) | AC-3 | None | A.8.5 |
| No SSH cipher or MAC line selects a CBC, 3DES, arcfour, blowfish, MD5 or SHA-1 algorithm (cipher, mac) | None | None | A.8.24 |
| A login banner is configured (banner login) | None | None | A.8.5 |
Known limitations
- rConfig ends a scoped block at the first line that is
!once trimmed, including the indented!that closes a nested sub-block. The idle timeout rule works because EOS printsidle-timeoutbefore thevrfsub-block undermanagement ssh. If it were printed after that sub-block, the rule would fail on a compliant switch. Check the order on one of your own switches. - The SSH idle timeout default is 0 (no timeout) and is not printed, so the rule needs an explicit
idle-timeout. - The EOS manual does not give the default cipher and MAC list, so the cipher rule fails only on an explicit weak
cipherormacline. It does not catch a weak algorithm in an unprinted default list on an older release. - The banner rule matches the
banner loginline only. EOS prints the banner text on the lines after it, ending withEOF.
EOS AAA
pro-policy-definitions / arista /eos-aaa.policyView on GitHub- Kind
- Hardening
- Rules
- 4
- Minimum rConfig
- 8.0.2
- Release
- v1.5.0
The root account disabled, login authentication through a server group with local fallback, no local user without a password, and command accounting to a server group.
| Rule | Method | What it checks |
|---|---|---|
| The root account is not enabled (fails on an aaa root line) | must_not_match_regex |
No line starts with aaa root , for example aaa root secret ... or aaa root nopassword. no aaa root passes, and so does a config that prints neither. |
| Login authentication uses a remote server group with local fallback (aaa authentication login default group … local) | must_match_regex |
An aaa authentication login default line names at least one group and ends with local. |
| No local user is configured without a password (fails on username … nopassword) | must_not_match_regex |
No username line contains nopassword. |
| All commands are sent to a remote accounting group (aaa accounting commands all default … group) | must_match_regex |
An aaa accounting commands all default line uses start-stop or stop-only and sends to a group. |
References
Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.
| Rule | NIST SP 800-53 | HIPAA (45 CFR) | NIST CSF 1.1 | ISO/IEC 27001:2022 |
|---|---|---|---|---|
| The root account is not enabled (fails on an aaa root line) | AC-2 | None | None | A.8.2 |
| Login authentication uses a remote server group with local fallback (aaa authentication login default group … local) | AC-2 | 164.312(a)(1) | PR.AC-1 | A.8.5 |
| No local user is configured without a password (fails on username … nopassword) | IA-5 | None | None | A.5.17 |
| All commands are sent to a remote accounting group (aaa accounting commands all default … group) | AU-2 | 164.312(b) | None | A.8.15 |
Known limitations
- The login rule needs
localas the last method. A line with only server groups, and no local fallback, fails.
EOS SNMP
pro-policy-definitions / arista /eos-snmp.policyView on GitHub- Kind
- Hardening
- Rules
- 3
- Minimum rConfig
- 8.0.2
- Release
- v1.5.0
No SNMPv1 or SNMPv2c communities, an SNMPv3 authPriv group, and no SNMPv3 user with MD5 authentication or DES privacy.
| Rule | Method | What it checks |
|---|---|---|
| No SNMPv1 or SNMPv2c community is configured (fails on snmp-server community) | must_not_match_regex |
No line starts with snmp-server community . |
| An SNMPv3 group uses authPriv (snmp-server group … v3 priv) | must_match_regex |
At least one snmp-server group line is at v3 priv. |
| No SNMPv3 user uses MD5 authentication or DES privacy (fails on snmp-server user … auth md5 or priv des) | must_not_match_regex |
No snmp-server user line contains auth md5, priv des or priv 3des. |
References
Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.
| Rule | NIST SP 800-53 | HIPAA (45 CFR) | ISO/IEC 27001:2022 |
|---|---|---|---|
| No SNMPv1 or SNMPv2c community is configured (fails on snmp-server community) | SC-12 | 164.312(e)(1) | A.8.5 |
| An SNMPv3 group uses authPriv (snmp-server group … v3 priv) | SC-12 | 164.312(e)(1) | A.8.5, A.8.24 |
| No SNMPv3 user uses MD5 authentication or DES privacy (fails on snmp-server user … auth md5 or priv des) | SC-12 | 164.312(e)(1) | A.8.5, A.8.24 |
Known limitations
- Unlike IOS, EOS prints SNMPv3 users in
show running-config, in the localized formsnmp-server user <user> <group> v3 localized <engine ID> auth ... priv .... Older 4.2x releases may print them differently.
EOS logging
pro-policy-definitions / arista /eos-logging.policyView on GitHub- Kind
- Hardening
- Rules
- 2
- Minimum rConfig
- 8.0.0
- Release
- v1.5.0
A remote syslog host and high-resolution log timestamps.
| Rule | Method | What it checks |
|---|---|---|
| A remote syslog host is configured (logging host, in any VRF) | must_match_regex |
At least one logging host or logging vrf <name> host line. |
| Log timestamps use high resolution (logging format timestamp high-resolution) | must_match_regex |
The config has logging format timestamp high-resolution. |
References
Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.
| Rule | NIST SP 800-53 | HIPAA (45 CFR) | ISO/IEC 27001:2022 |
|---|---|---|---|
| A remote syslog host is configured (logging host, in any VRF) | AU-2 | 164.312(b) | A.8.15 |
| Log timestamps use high resolution (logging format timestamp high-resolution) | AU-3 | 164.312(b) | A.8.15 |
Known limitations
- There is no syslog trap level rule. The EOS manual does not state the default trap level, so the printed form could not be settled. Check it on your own switch with
show running-config all | include logging trap.
EOS services
pro-policy-definitions / arista /eos-services.policyView on GitHub- Kind
- Hardening
- Rules
- 1
- Minimum rConfig
- 8.0.2
- Release
- v1.5.0
The eAPI does not serve plain HTTP.
| Rule | Method | What it checks |
|---|---|---|
| The eAPI does not serve plain HTTP (fails on protocol http under management api http-commands) | must_not_match_regex |
No indented protocol http line, with or without a port. protocol https passes. |
References
Published references recorded in the sidecar. A rule provides evidence towards a control; it does not make a device compliant with it.
| Rule | NIST SP 800-53 | ISO/IEC 27001:2022 |
|---|---|---|
| The eAPI does not serve plain HTTP (fails on protocol http under management api http-commands) | CM-7 | A.8.9 |
Known limitations
- The rule is unscoped, so an indented
protocol httpline anywhere in the config fails it, not only undermanagement api http-commands.
Framework files
Framework files are generated from the hardening files above. Each one collects every hardening rule that lists a reference for one framework, copied unchanged, with the control reference added to the start of its description (for example NIST AC-17: ...). The rule tables, references and known limitations are in the topic sections linked below.
| Framework | File | Rules | Minimum rConfig | Collects rules from |
|---|---|---|---|---|
| NIST SP 800-53 | eos-nist-800-53.policy |
12 | 8.3.0 | EOS AAA, EOS logging, EOS management access, EOS services, EOS SNMP |
| NIST CSF 1.1 | eos-nist-csf.policy |
1 | 8.0.0 | EOS AAA |
| HIPAA Security Rule (45 CFR 164.312) | eos-hipaa.policy |
8 | 8.0.2 | EOS AAA, EOS logging, EOS management access, EOS SNMP |
| ISO/IEC 27001:2022 Annex A | eos-iso27001.policy |
14 | 8.3.0 | EOS AAA, EOS logging, EOS management access, EOS services, EOS SNMP |
A framework file lists checks relevant to that framework. It is not a certification or a full assessment, and a device that passes it is not certified against the framework.
Operational standards
EOS operational standards
pro-policy-definitions / arista /eos-operational-standards.policyView on GitHub- Kind
- Operational standards
- Rules
- 7
- Minimum rConfig
- 8.3.0
- Release
- v1.5.0
Checks drift from your own operational standard, not a hardening baseline: standard NTP, syslog and DNS servers, a login banner, a description on every interface that is not shut down, a hostname naming pattern and an SNMP location. Replace the example values (RFC 5737 addresses such as 192.0.2.10, and the hostname pattern) with your own before use.
| Rule | Method | What it checks |
|---|---|---|
| NTP servers are set to your standard (replace 192.0.2.10 and 192.0.2.11) | evaluate_block |
Both ntp server 192.0.2.10 and ntp server 192.0.2.11 lines, with or without vrf <name>. |
| Syslog servers are set to your standard (replace 192.0.2.20 and 192.0.2.21) | evaluate_block |
Both logging host 192.0.2.20 and logging host 192.0.2.21 lines, with or without vrf <name>. |
| DNS servers are set to your standard (replace 192.0.2.30 and 192.0.2.31) | evaluate_block |
Both ip name-server 192.0.2.30 and ip name-server 192.0.2.31 lines, with or without vrf <name>. |
| A login banner is set (banner login, any text; nothing to replace) | must_match_regex |
The config has a banner login line. |
| Every interface that is not shut down has a description (nothing to replace) | evaluate_block |
Every interface block has a shutdown line or a non-empty description. |
The hostname follows your naming pattern (replace the example pattern [a-z]{3}-(rtr|sw)[0-9]{2}, for example dub-sw01) |
must_match_regex |
The hostname line matches the pattern exactly. |
| An SNMP location is set (snmp-server location, any text; nothing to replace) | must_match_regex |
The config has an snmp-server location line with some text. |
Known limitations
- The NTP, syslog and DNS rules check that each standard server is configured, not that no other server is. They are regular expressions: escape the dots when you replace an address, for example
192\.0\.2\.10. - EOS prints unused Ethernet ports as a bare
interface EthernetNblock, so they fail the interface rule until you shut them down or describe them. Loopback, Management and Vxlan interfaces are checked too.