OcNOS AAA
Rules for central login: users are checked against a TACACS+ or RADIUS server, not only local accounts, and the TACACS+ server has a shared key. They come from the ocnos-aaa policy template.
Every example on this page was checked with rConfig Pro's policy engine on Each of the 4 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 ocnos-aaa.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 |
|---|---|---|
| Login uses a TACACS+ or RADIUS server group | must_match_regex |
8.0.0 |
| A TACACS+ server has a key | must_match_regex |
8.0.0 |
Login uses a TACACS+ or RADIUS server group
Central login gives each person their own account and one place to remove access. The rule looks for aaa authentication login default followed by group, with or without a vrf name in between. Any group name passes.
// Login authentication uses a TACACS+ or RADIUS server group (aaa authentication login default ... group)#[must_match_regex]/^aaa authentication login default (vrf \S+ )?group \S+/mfeature ssh vrf managementfeature tacacs+ vrf managementtacacs-server login host 198.51.100.232 vrf management seq-num 1 key 7 0x5e1c7a90b3d24f68aaa authentication login default vrf management group tacacs+Why: Login uses the tacacs+ group in the management VRF.
feature ssh vrf managementsnmp-server enable snmp vrf managementsnmp-server view all .1 included vrf managementWhy: There is no aaa authentication login line, so only local accounts are used.
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 | AC-2 |
| NIST CSF 1.1 | PR.AC-1 |
| 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.0 (must_match_regex). Editions: Pro, Vector, Enterprise.
A TACACS+ server has a key
The key encrypts traffic between the router and the TACACS+ server. The rule looks for a tacacs-server login host line with the word key on it. It checks TACACS+ only, because the printed form of a RADIUS server line is not known.
// A TACACS+ server is configured with a key (tacacs-server login host ... key)#[must_match_regex]/^tacacs-server login host \S+ .*\bkey\b/mfeature tacacs+ vrf managementtacacs-server login host 198.51.100.232 vrf management seq-num 1 key 7 0x5e1c7a90b3d24f68aaa authentication login default vrf management group tacacs+Why: The TACACS+ server has a key. The key shown is made up.
feature ssh vrf managementsnmp-server enable snmp vrf managementsnmp-server view all .1 included vrf managementWhy: There is no TACACS+ server.
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.5 |
Tested with: sample excerpts from OcNOS-SP 7.0.0. Minimum rConfig 8.0.0 (must_match_regex). Editions: Pro, Vector, Enterprise.
Related reference
- IP Infusion OcNOS policy templates: every rule in
ocnos-aaa.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.