During a network security audit, an enterprise engineering team is reviewing AAA operations across campus switches and routers. Match each specific administrative operation or security scenario on the left with its corresponding AAA component or protocol mechanism on the right.
- Evaluating whether an authenticated administrator possesses the privilege level to execute specific CLI commands such as reload or configure terminal.Command-Level Authorization (TACACS+)
- Authenticating 802.1X wireless or wired client network access requests while encrypting only the user password in transit over UDP port 1812.Network Access Authentication (RADIUS)
- Tracking administrative activity by logging session start/stop timestamps, executed CLI commands, and total bytes transferred for compliance auditing.AAA Accounting
- Authenticating router console logins using a locally defined database user account when centralized TACACS+ servers become unreachable.Local AAA Authentication Fallback
Cevap
Evaluating command execution privileges maps to Command-Level Authorization (TACACS+); authenticating 802.1X client access over UDP port 1812 with password-only encryption maps to Network Access Authentication (RADIUS); tracking session activity and logged commands maps to AAA Accounting; and authenticating against a local database during server outages maps to Local AAA Authentication Fallback.
Evaluating CLI command privileges requires per-command authorization, which is a native capability of TACACS+ (Command-Level Authorization). Authenticating 802.1X clients over UDP port 1812 with password-only encryption describes standard RADIUS operation for network access control. Collecting log metrics such as command usage, duration, and session timestamps is the core responsibility of AAA Accounting. Falling back to an on-box database when central AAA servers fail represents Local AAA Authentication Fallback.
Adım Adım Çözüm
Anahtar Kavram
AAA Framework Pillars and Operational Protocol Mechanisms (TACACS+ vs RADIUS)
Tahmini Süre:2m 0s