IOS XR AAA and local credentials
Rules for who can log in and how their passwords are stored: logins go to a TACACS+ or RADIUS server group, and local break-glass accounts use a strong hash. They come from the iosxr-aaa policy template.
Every example on this page was checked with rConfig Pro's policy engine on Each of the 6 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-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 Cisco IOS XR templates page lists the file’s known limitations. Run the rules against show running-config.
| Rule | Method | Since |
|---|---|---|
| Login through a server group | must_match_regex |
8.0.0 |
| No reversible local passwords | evaluate_block |
8.3.0 |
| No MD5 local secrets | must_not_match_regex |
8.0.2 |
Login through a server group
Central authentication means each person has their own account and you can turn it off in one place. This rule passes when aaa authentication login default starts with group and a server group name. local can still follow as a fallback.
// Login authentication uses a TACACS+ or RADIUS server group (aaa authentication login default group ...)#[must_match_regex]/^aaa authentication login default group \S+/maaa group server tacacs+ TACACS vrf MGMT server 192.0.2.32 server 192.0.2.33!aaa authorization exec default group TACACS localaaa authorization commands default group TACACS noneaaa authentication login default group TACACS localWhy: Logins go to the TACACS group first.
aaa group server tacacs+ TACACS vrf MGMT server 192.0.2.32 server 192.0.2.33!aaa authorization exec default group TACACS localaaa authorization commands default group TACACS noneaaa authentication login default localWhy: Logins use local accounts only, even though a TACACS group exists.
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 IOS XR 7.9.2 (synthetic). Minimum rConfig 8.0.0 (must_match_regex). Editions: Pro, Vector, Enterprise.
No reversible local passwords
Under a username, password stores a type 7 value that anyone can decode. Use secret instead. This rule looks inside each username block and fails if any of them has a password line.
// No local user has a reversible password (fails on password under a username)#[evaluate_block]scope: ^usernamenot: regex: '/^\s+password /m'username breakglass group root-lr group cisco-support secret 10 $6$e0d02e17b0ad6e7f$e579eda3c78e1623fc7dbd6c1e0aee4ce5d9fa28aec!Why: The account uses a type 10 (SHA-512) secret.
username breakglass group root-lr group cisco-support password 7 0822455D0A165B5A!Why: The account has a type 7 password, which can be decoded.
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 | IA-5 |
| ISO/IEC 27001:2022 Annex A | A.5.17 |
Tested with: sample excerpts from IOS XR 7.9.2 (synthetic). Minimum rConfig 8.3.0 (evaluate_block). Editions: Pro, Vector, Enterprise.
No MD5 local secrets
secret 5 is an MD5 hash, which is quick to crack. IOS XR supports type 8, 9 and 10 secrets. This rule fails on any indented secret 5 line.
// No local user secret uses an MD5 hash (fails on secret 5)#[must_not_match_regex]/^\s+secret 5 /musername breakglass group root-lr group cisco-support secret 10 $6$e0d02e17b0ad6e7f$e579eda3c78e1623fc7dbd6c1e0aee4ce5d9fa28aec!Why: The only secret is type 10.
username operator group operator secret 5 $1$Xk3p$Q1u9aZqfF0p2n7HcV1mWt/!Why: The operator account has an MD5 secret.
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 | IA-5 |
| ISO/IEC 27001:2022 Annex A | A.5.17 |
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-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.