Skip to content
Guides & References

IP Infusion OcNOS policy templates

The IP Infusion OcNOS policy templates in rconfig/pro-policy-definitions v1.5.0: what each rule checks, minimum versions, references and framework files.

Policy LibraryUpdated
On this page

IP Infusion OcNOS policy templates

Policy templates for IP Infusion OcNOS, from the ip-infusion/ folder. They check the configuration as returned by show running-config: top-level commands in column 0, sub-commands indented one space, and blocks separated by ! lines. Many lines end with vrf management. This page documents release v1.5.0. See importing a policy template to load one into rConfig.

The rules were written against an OcNOS-SP 7.0.0 router (a UfiSpace S9510-28DC-B), using command forms from the OcNOS 6.3 to 6.5 and current SP and DC command references. They have not been tried on the OcNOS-DC edition or on other hardware.

For worked examples of these rules, with a passing and a failing config for each, see the IP Infusion OcNOS platform pages.

Hardening definitions

Every OcNOS rule is an unscoped regular expression in the /.../m form, so ^ and $ match at each line of the config. See known limitations below for why no rule is scoped to a section.

OcNOS management access

pro-policy-definitions / ip-infusion /ocnos-management-access.policyView on GitHub
Kind
Hardening
Rules
3
Minimum rConfig
8.0.2
Release
v1.5.0

No Telnet, SSH enabled on the management VRF, and a custom login banner.

Rule Method What it checks
Telnet is not enabled (fails on feature telnet) must_not_match_regex No line starts with feature telnet.
SSH is enabled on the management VRF (feature ssh vrf management) must_match_regex A line reads exactly feature ssh vrf management, with trailing spaces allowed.
A custom login banner is configured (banner motd, other than banner motd default) must_match_regex A banner motd line has text other than default.

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 feature telnet) AC-17 164.312(a)(1) A.8.5
SSH is enabled on the management VRF (feature ssh vrf management) AC-17 164.312(a)(1) A.8.24
A custom login banner is configured (banner motd, other than banner motd default) None None A.8.5

Known limitations

  • Telnet is off by default and OcNOS prints nothing when it is off, so the Telnet rule fails only on a feature telnet line.
  • A router with factory settings prints feature ssh vrf management. SSH on another VRF only does not pass the SSH rule.
  • banner motd default puts back the banner that shows the software version, so the banner rule does not count it. banner motd takes one line of text.

OcNOS AAA

pro-policy-definitions / ip-infusion /ocnos-aaa.policyView on GitHub
Kind
Hardening
Rules
2
Minimum rConfig
8.0.0
Release
v1.5.0

Login authentication through a TACACS+ or RADIUS server group, and a TACACS+ server with a key.

Rule Method What it checks
Login authentication uses a TACACS+ or RADIUS server group (aaa authentication login default … group) must_match_regex A line starts with aaa authentication login default, an optional vrf name, then group and a group name.
A TACACS+ server is configured with a key (tacacs-server login host … key) must_match_regex A tacacs-server login host line contains the word key.

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
Login authentication uses a TACACS+ or RADIUS server group (aaa authentication login default … group) AC-2 164.312(a)(1) PR.AC-1 A.8.5
A TACACS+ server is configured with a key (tacacs-server login host … key) None None None A.8.5

Known limitations

  • The server rule checks TACACS+ only. The printed form of radius-server login host ... key is not known, so a router that uses only RADIUS fails it.

OcNOS SNMP

pro-policy-definitions / ip-infusion /ocnos-snmp.policyView on GitHub
Kind
Hardening
Rules
1
Minimum rConfig
8.0.2
Release
v1.5.0

No SNMPv1 or SNMPv2c community.

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 .

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

Known limitations

  • There is no SNMPv3 user rule. The printed form of an snmp-server user line with auth sha and priv aes is not known.

OcNOS logging

pro-policy-definitions / ip-infusion /ocnos-logging.policyView on GitHub
Kind
Hardening
Rules
2
Minimum rConfig
8.0.2
Release
v1.5.0

A remote syslog server, and log timestamps not set to seconds or none.

Rule Method What it checks
A remote syslog server is configured (logging remote server) must_match_regex A line starts with logging remote server and an address.
Log timestamps are not set to seconds or none (fails on logging timestamp seconds or none) must_not_match_regex No line reads logging timestamp seconds or logging timestamp none.

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 server is configured (logging remote server) AU-2 164.312(b) A.8.15
Log timestamps are not set to seconds or none (fails on logging timestamp seconds or none) AU-3 164.312(b) A.8.15

Known limitations

  • The remote server rule matches the stored form logging remote server <address> <severity> port <port> vrf management. Any address, severity, port or VRF passes.
  • There is no console logging rule. Console logging is not printed at the default, and the printed form of a change is not known.

OcNOS services

pro-policy-definitions / ip-infusion /ocnos-services.policyView on GitHub
Kind
Hardening
Rules
2
Minimum rConfig
8.3.0
Release
v1.5.0

NTP authentication with a trusted key, and password encryption.

Rule Method What it checks
NTP authentication is enabled with a trusted key (ntp authenticate, ntp trusted-key) evaluate_block Both an ntp authenticate line and an ntp trusted-key <number> line are present, each with an optional vrf name.
Password encryption is enabled (service password-encryption) must_match_regex A line reads exactly service password-encryption.

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
NTP authentication is enabled with a trusted key (ntp authenticate, ntp trusted-key) None A.8.17
Password encryption is enabled (service password-encryption) CM-6 A.5.17

Known limitations

  • The NTP rule checks that a trusted key is set, not that the key number matches an ntp authentication-key line.

Known limitations for every file

  • router bgp separates its address families with indented ! lines. rConfig’s block splitter ends a scoped block at any line that is ! once trimmed, so a rule scoped to ^router bgp would see only the lines before the first address family. Every OcNOS rule is therefore an unscoped regular expression.
  • OcNOS prints trailing spaces on some lines (for example logging level nsm 4 ). Every rule that ends at the end of a line allows for them with [ \t]*$.
  • These checks were proposed and left out, because their printed form could not be settled: SSH ciphers, exec-timeout on line vty and line console, SNMPv3 users, console logging and RADIUS servers.

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 ocnos-nist-800-53.policy 7 8.0.2 OcNOS AAA, OcNOS logging, OcNOS management access, OcNOS services, OcNOS SNMP
NIST CSF 1.1 ocnos-nist-csf.policy 1 8.0.0 OcNOS AAA
HIPAA Security Rule (45 CFR 164.312) ocnos-hipaa.policy 6 8.0.2 OcNOS AAA, OcNOS logging, OcNOS management access, OcNOS SNMP
ISO/IEC 27001:2022 Annex A ocnos-iso27001.policy 10 8.3.0 OcNOS AAA, OcNOS logging, OcNOS management access, OcNOS services, OcNOS 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

OcNOS operational standards

pro-policy-definitions / ip-infusion /ocnos-operational-standards.policyView on GitHub
Kind
Operational standards
Rules
4
Minimum rConfig
8.3.0
Release
v1.5.0

Checks drift from your own operational standard, not a hardening baseline: standard NTP and syslog servers, 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 are present, with any options after the address.
Syslog servers are set to your standard (replace 192.0.2.20 and 192.0.2.21) evaluate_block Both logging remote server 192.0.2.20 and logging remote server 192.0.2.21 lines are present, with any severity, port or VRF.
The hostname follows your naming pattern (replace the example pattern [a-z]{3}-(rtr|sw)[0-9]{2}, for example dub-rtr01) 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 An snmp-server location line has text, with or without vrf management first. A line with only the VRF fails.

Known limitations

  • The NTP and syslog rules check that each standard server is configured, not that no other server is.
  • The rules are regular expressions: escape the dots when you replace an address, for example 192\.0\.2\.10.
  • There is no interface description rule. OcNOS prints an interface block for every port, and unused ports are not shut down, so a rule that every interface is described or shut down would fail on every router.

Type to search.