IOS XR services
Rules that keep unneeded services and risky IP features turned off. They come from the iosxr-services policy template.
Every example on this page was checked with rConfig Pro's policy engine on Each of the 10 configs below was run through rConfig Pro’s evaluator with the rule above it, and gave the result shown. The configs are sanitised excerpts of the sample configs that come with the template.
All the rules come from iosxr-services.policy in the policy templates (v1.5.0). Import the whole file with Import Templates (see importing a policy template), or copy one rule into your own definition. The Cisco IOS XR templates page lists the file’s known limitations. Run the rules against show running-config.
| Rule | Method | Since |
|---|---|---|
| No TFTP server | must_not_match_regex |
8.0.2 |
| No IPv4 source routing | must_not_match_regex |
8.0.2 |
| No directed broadcast | must_not_match_regex |
8.0.2 |
| No proxy ARP | must_not_match_regex |
8.0.2 |
| No ICMP redirects | must_not_match_regex |
8.0.2 |
No TFTP server
TFTP has no authentication, so anyone who can reach the router can fetch files from it. This rule fails on any tftp ipv4 server or tftp ipv6 server line, with or without a VRF.
// The TFTP server is not enabled (fails on tftp ipv4 or ipv6 server)#[must_not_match_regex]/^tftp (vrf \S+ )?ipv[46] server /mlldp!ssh client vrf MGMTssh server loggingssh server rate-limit 60ssh server session-limit 10ssh server v2ssh server vrf MGMTssh timeout 60endWhy: No TFTP server line.
lldp!telnet vrf default ipv4 server max-servers 10tftp ipv4 server homedir disk0:ssh client vrf MGMTssh server loggingssh server rate-limit 60ssh server session-limit 10ssh server vrf MGMTssh timeout 60endWhy: A TFTP server serves disk0:.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | CM-7 |
| HIPAA (45 CFR) | 164.312(c)(1) |
| ISO/IEC 27001:2022 Annex A | A.8.9 |
Tested with: sample excerpts from IOS XR 7.9.2 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
No IPv4 source routing
Source routing lets the sender choose the path a packet takes, which can be used to get round filters. This rule fails on an ipv4 source-route line.
// IPv4 source routing is not enabled (fails on ipv4 source-route)#[must_not_match_regex]/^ipv4 source-route$/mdomain name example.comdomain name-server 192.0.2.30domain name-server 192.0.2.31domain lookup disabletacacs source-interface MgmtEth0/RSP0/CPU0/0 vrf MGMTWhy: Source routing is not turned on.
domain name example.comdomain lookup disableipv4 source-routetacacs source-interface MgmtEth0/RSP0/CPU0/0 vrf MGMTWhy: Source routing is turned on.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | SC-5 |
| ISO/IEC 27001:2022 Annex A | A.8.20 |
Tested with: sample excerpts from IOS XR 7.9.2 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
No directed broadcast
Directed broadcast forwards packets to every host on a subnet, which is used in smurf attacks. This rule fails on an indented ipv4 directed-broadcast line under any interface.
// Directed broadcast is not enabled on any interface (fails on ipv4 directed-broadcast)#[must_not_match_regex]/^\s+ipv4 directed-broadcast\b/minterface TenGigE0/0/0/2 description IXP peering LAN mtu 1514 ipv4 address 203.0.113.131 255.255.255.128 load-interval 30!Why: The interface has no directed broadcast.
interface TenGigE0/0/0/2 description IXP peering LAN mtu 1514 ipv4 address 203.0.113.131 255.255.255.128 ipv4 directed-broadcast proxy-arp ipv4 redirects load-interval 30!Why: Directed broadcast is on for TenGigE0/0/0/2.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | SC-7 |
| ISO/IEC 27001:2022 Annex A | A.8.20 |
Tested with: sample excerpts from IOS XR 7.9.2 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
No proxy ARP
With proxy ARP the router answers ARP requests for other hosts, which hides addressing mistakes and helps traffic go where it should not. This rule fails on an indented proxy-arp line.
// Proxy ARP is not enabled on any interface (fails on proxy-arp)#[must_not_match_regex]/^\s+proxy-arp$/minterface TenGigE0/0/0/2 description IXP peering LAN mtu 1514 ipv4 address 203.0.113.131 255.255.255.128 load-interval 30!Why: The interface has no proxy ARP.
interface TenGigE0/0/0/2 description IXP peering LAN mtu 1514 ipv4 address 203.0.113.131 255.255.255.128 ipv4 directed-broadcast proxy-arp ipv4 redirects load-interval 30!Why: Proxy ARP is on for TenGigE0/0/0/2.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| NIST SP 800-53 | SC-7 |
| ISO/IEC 27001:2022 Annex A | A.8.20 |
Tested with: sample excerpts from IOS XR 7.9.2 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
No ICMP redirects
ICMP redirects tell hosts to send traffic another way, and a forged one can steer traffic through an attacker. This rule fails on an indented ipv4 redirects line.
// ICMP redirects are not enabled on any interface (fails on ipv4 redirects)#[must_not_match_regex]/^\s+ipv4 redirects$/minterface TenGigE0/0/0/2 description IXP peering LAN mtu 1514 ipv4 address 203.0.113.131 255.255.255.128 load-interval 30!Why: The interface sends no redirects.
interface TenGigE0/0/0/2 description IXP peering LAN mtu 1514 ipv4 address 203.0.113.131 255.255.255.128 ipv4 directed-broadcast proxy-arp ipv4 redirects load-interval 30!Why: ICMP redirects are on for TenGigE0/0/0/2.
Expected result in rConfig, with this rule as the only rule in a definition:
| Config | Rule result | Overall result |
|---|---|---|
| Passing config | pass | PASS |
| Failing config | fail | FAIL |
Framework mapping. The rule provides evidence towards these controls. It does not certify anything.
| Framework | Reference |
|---|---|
| ISO/IEC 27001:2022 Annex A | A.8.20 |
Tested with: sample excerpts from IOS XR 7.9.2 (synthetic). Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.
Related reference
- Cisco IOS XR policy templates: every rule in
iosxr-services.policy, its references and known limitations. - Policy Definitions: the definition file format and every method.
- Policy Assignments: run a definition against your devices.
- Policy Compliance Results: read the pass and fail results.