Match each enterprise AAA protocol mechanism or access control payload on the left with its corresponding functional role and operational process on the right.
- RADIUS payload containing Acct-Status-Type = Stop and Acct-Input-Octets = 4194304Resource Usage & Session Metric Logging (Accounting)
- TACACS+ packet authorization phase sending AUTHOR_REQUEST for command 'configure terminal'Per-Command Privilege Scoping & Execution Filtering (Authorization)
- SAML 2.0 Response payload containing a digitally signed Assertion issued by an Identity Provider (IdP)Federated Identity Verification & Assertion Delivery (Authentication)
- IEEE 802.1X EAP-TLS handshake exchanging X.509 client and server certificatesMutual Cryptographic Identity Verification (Authentication)
Answer
RADIUS payload with Acct-Status-Type pairs with Resource Usage & Session Metric Logging (Accounting). TACACS+ AUTHOR_REQUEST pairs with Per-Command Privilege Scoping & Execution Filtering (Authorization). SAML 2.0 Assertion pairs with Federated Identity Verification & Assertion Delivery (Authentication). IEEE 802.1X EAP-TLS handshake pairs with Mutual Cryptographic Identity Verification (Authentication).
The correct pairings evaluate the specific AAA functional domain of each enterprise protocol packet. RADIUS accounting attributes collect metric logs for session auditing. TACACS+ decouples authorization to inspect per-command execution rights. SAML assertions transmit federated identity authentication results across web domains. EAP-TLS enforces mutual authentication using digital certificate handshakes.
Step-by-Step Solution
Key Concept
Authentication, Authorization, and Accounting (AAA) Protocol Functional Separation
Estimated Time:3m 0s