An enterprise security architect is reviewing identity and access management (IAM) controls across network access servers, policy engines, and central logging services. Match each security mechanism on the left with the specific AAA function or protocol capability on the right that best describes its primary operational purpose.
- EAP-TLS protocol negotiation during an 802.1X network access request using X.509 digital certificatesMutual Authentication
- XACML policy decision point (PDP) evaluating user attributes, environmental context, and object sensitivityAttribute-Based Authorization
- TACACS+ daemon capturing individual privilege shell commands executed by network engineersAdministrative Command Accounting
- RADIUS start, interim-update, and stop messages logging connection duration and byte countsResource Usage Accounting
Answer
EAP-TLS pairs with Mutual Authentication; XACML PDP pairs with Attribute-Based Authorization; TACACS+ command logging pairs with Administrative Command Accounting; RADIUS start/stop metrics pair with Resource Usage Accounting.
Matching each security control to its primary operational capability correctly distinguishes between authentication methods, authorization policy models, and distinct accounting mechanism granularity.
Step-by-Step Solution
Key Concept
Core Pillars and Implementations of AAA (Authentication, Authorization, and Accounting)
Estimated Time:2m 0s