Skip to content
Guides & References

OcNOS management access

Worked examples for the OcNOS management access template: no Telnet, SSH on the management VRF and a custom login banner.

Policy LibraryUpdated
Platform
ip-infusion-ocnos
Minimum version
rConfig 8.0.2
Editions
Pro, Vector, Enterprise
On this page

OcNOS management access

Rules for how people log in to the router: no Telnet, SSH turned on in the management VRF, and a warning banner before login. They come from the ocnos-management-access policy template.

Every example on this page was checked with rConfig Pro's policy engine on

Each of the 7 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. A card marked changed has one line edited to show a failure.

All the rules come from ocnos-management-access.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 IP Infusion OcNOS templates page lists the file’s known limitations. Run the rules against show running-config.

Rule Method Since
Telnet is not enabled must_not_match_regex 8.0.2
SSH is enabled on the management VRF must_match_regex 8.0.0
A custom login banner is configured must_match_regex 8.0.0

Telnet is not enabled

Telnet sends logins in clear text. OcNOS has Telnet off by default and prints nothing when it is off, so this rule cannot look for a “Telnet off” line. It fails only when a feature telnet line is present.

Definition
// Telnet is not enabled (fails on feature telnet)
#[must_not_match_regex]
/^feature telnet\b/m
passPassing config: Hardened S9510-28DC-B sample (OcNOS-SP 7.0.0, edited copy of the lab router sample)
feature ssh vrf management
feature tacacs+ vrf management
snmp-server enable snmp vrf management

Why: There is no feature telnet line.

failFailing config: Hardened S9510-28DC-B sample (OcNOS-SP 7.0.0, edited copy of the lab router sample), changed: feature telnet vrf management added
feature ssh vrf management
feature telnet vrf management
feature tacacs+ vrf management
snmp-server enable snmp vrf management

Why: Telnet is turned on in the management VRF.

Expected result in rConfig, with this rule as the only rule in a definition:

ConfigRule resultOverall result
Passing configpassPASS
Failing configfailFAIL

Framework mapping. The rule provides evidence towards these controls. It does not certify anything.

Framework Reference
NIST SP 800-53 AC-17
HIPAA (45 CFR) 164.312(a)(1)
ISO/IEC 27001:2022 Annex A A.8.5

Tested with: sample excerpts from OcNOS-SP 7.0.0. Minimum rConfig 8.0.2 (must_not_match_regex). Editions: Pro, Vector, Enterprise.


SSH is enabled on the management VRF

SSH is the safe way to manage the router. A router with factory settings prints feature ssh vrf management, so this rule looks for that exact line. Extra text after it, other than spaces, fails.

Definition
// SSH is enabled on the management VRF (feature ssh vrf management)
#[must_match_regex]
/^feature ssh vrf management[ \t]*$/m
passPassing config: Hardened S9510-28DC-B sample (OcNOS-SP 7.0.0, edited copy of the lab router sample)
errdisable cause stp-bpdu-guard
feature ssh vrf management
feature tacacs+ vrf management

Why: SSH is on in the management VRF.

failFailing config: Hardened S9510-28DC-B sample (OcNOS-SP 7.0.0, edited copy of the lab router sample), changed: feature ssh vrf management removed
errdisable cause stp-bpdu-guard
feature tacacs+ vrf management

Why: There is no feature ssh vrf management line, so SSH is off in the management VRF.

Expected result in rConfig, with this rule as the only rule in a definition:

ConfigRule resultOverall result
Passing configpassPASS
Failing configfailFAIL

Framework mapping. The rule provides evidence towards these controls. It does not certify anything.

Framework Reference
NIST SP 800-53 AC-17
HIPAA (45 CFR) 164.312(a)(1)
ISO/IEC 27001:2022 Annex A A.8.24

Tested with: sample excerpts from OcNOS-SP 7.0.0. Minimum rConfig 8.0.0 (must_match_regex). Editions: Pro, Vector, Enterprise.


A custom login banner is configured

A login banner warns people that access is restricted and monitored. The rule passes on any banner motd line with text, except banner motd default, which puts back the banner that shows the software version.

Definition
// A custom login banner is configured (banner motd, other than banner motd default)
#[must_match_regex]
/^banner motd (?!default[ \t]*$)\S/m
passPassing config: Hardened S9510-28DC-B sample (OcNOS-SP 7.0.0, edited copy of the lab router sample)
hostname dub-rtr01
banner motd Authorised access only. All activity is monitored and logged.
ip domain-lookup vrf management

Why: A custom banner is set.

failFailing config: S9510-28DC-B lab router sample (OcNOS-SP 7.0.0, sanitised)
ip domain-lookup vrf management
bridge 1 protocol rstp vlan-bridge
tfo Disable
errdisable cause stp-bpdu-guard
feature ssh vrf management

Why: There is no banner motd line. The lab router uses the default banner, which is not printed.

failFailing config: Hardened S9510-28DC-B sample (OcNOS-SP 7.0.0, edited copy of the lab router sample), changed: banner motd default instead of the custom text
hostname dub-rtr01
banner motd default
ip domain-lookup vrf management

Why: banner motd default puts back the version-string banner, so it does not count.

Expected result in rConfig, with this rule as the only rule in a definition:

ConfigRule resultOverall result
Passing configpassPASS
Failing config 1failFAIL
Failing config 2failFAIL

Framework mapping. The rule provides evidence towards these controls. It does not certify anything.

Framework Reference
ISO/IEC 27001:2022 Annex A A.8.5

Tested with: sample excerpts from OcNOS-SP 7.0.0. Minimum rConfig 8.0.0 (must_match_regex). Editions: Pro, Vector, Enterprise.


Type to search.