A security assessment of an enterprise edge router reveals that while SSH access is enabled, administrative commands executed by engineers are logged under a single shared local account without individual accountability or granular command restriction. To eliminate this security risk and enforce centralized command-level authorization and per-user accounting, which solution should the network administrator implement?
- Implement a TACACS+ server architecture and enable AAA command authorization and accounting on the router.Answer
- BImplement a RADIUS server architecture and configure 802.1X network access control on the router management interfaces.
- CApply an extended IPv4 Access Control List on the VTY lines allowing SSH access only from administrative IP subnets.
- DConfigure switchport port security with sticky MAC address learning on the router interface.
Answer
Implement a TACACS+ server architecture and enable AAA command authorization and accounting on the router.
The option advocating TACACS+ server integration with AAA command authorization and accounting is correct because TACACS+ decouples authentication, authorization, and accounting. This architecture enables administrators to validate each CLI command against a central server policy before execution and maintains individual user accounting records.
Step-by-Step Solution
Key Concept
Device Access Mitigation using AAA and TACACS+ vs RADIUS