CPSA ยท Network device management and Layer 2/3 protocols
TACACS+ for device AAA
AAA for network devices, what is encrypted, key weaknesses and comparison with RADIUS.
Key points
- TACACS+: centralised authentication, authorization and accounting, TCP port 49.
- Separates the three, enabling per-command authorization; RADIUS combines authentication and authorization over UDP.
- 12-byte header in clear text; only the body is obfuscated with an MD5-derived pad and shared key.
- Weak keys can be brute-forced from a capture; never use the unencrypted flag in production.
- Use long keys, protect the path to the server.
Source: https://www.rfc-editor.org/rfc/rfc8907.html
Practice questions
Which transport and port does TACACS+ use?
- UDP 1812
- TCP 49
- UDP 49
- TCP 389
Show answer
Answer: B. TCP 49
TACACS+ uses TCP port 49. RADIUS is the one associated with UDP.
Which statements about TACACS+ compared with RADIUS are correct?
- TACACS+ runs over TCP
- TACACS+ separates authentication from authorization
- TACACS+ is carried over UDP 1812
- TACACS+ can only authorize at login, never per command
- TACACS+ has no accounting function
Show answer
Answer: A. TACACS+ runs over TCP, B. TACACS+ separates authentication from authorization
TACACS+ runs over TCP and separates authentication, authorization and accounting. It does not use UDP 1812 and does not authorize only at login.
TACACS+ encrypts the whole packet, including its header, with a strong cipher.
Show answer
Answer: False
False. The header is sent in clear text, and the body is obfuscated with an MD5 derived pad, which the specification does not treat as strong protection.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
