An enterprise security engineer is auditing identity lifecycle management and access control workflows across the organization. Match each operational access activity on the left with its corresponding identity management or AAA (Authentication, Authorization, and Accounting) component on the right.
- A remote worker enters their user principal name (UPN) into a VPN client login window to claim an identity.Identification
- An Identity Provider verifies a user's identity by validating a FIDO2 hardware security key challenge-response.Authentication
- A network access server checks an Active Directory group membership policy to assign dynamic VLAN permissions to a connected device.Authorization
- A centralized SIEM ingests RADIUS session logs containing connection start times, total bytes transferred, and disconnect reasons.Accounting
Answer
Entering a UPN maps to Identification; validating FIDO2 credentials maps to Authentication; enforcing dynamic VLAN access rights maps to Authorization; and recording connection metrics and duration maps to Accounting.
Each operational scenario directly aligns with a specific phase in identity and access governance: entering a UPN claims an identity (Identification); verifying FIDO2 credentials proves the claim (Authentication); evaluating group policies to set network privileges grants access boundaries (Authorization); and recording session metrics to SIEM maintains an audit log (Accounting).
Step-by-Step Solution
Key Concept
Authentication, Authorization, and Accounting (AAA) Framework and Identification