Match each enterprise identity and access management scenario on the left with the corresponding core AAA phase or concept on the right.
- An employee enters a User Principal Name (UPN) at a web portal login prompt prior to presenting any credentials.Identification
- An identity provider validates a user's FIDO2 WebAuthn asymmetric key signature and hardware token PIN during session initialization.Authentication
- A security policy engine checks a user's SAML 2.0 role attributes and dynamic network risk score against an Access Control List (ACL) to grant microsegment access.Authorization
- A central network service logs TACACS+ session start/stop timestamps, executed CLI commands, and total bytes transferred by an administrator.Accounting
Cevap
Entering a User Principal Name maps to Identification. Validating FIDO2 signatures and PINs maps to Authentication. Evaluating SAML role attributes against ACLs maps to Authorization. Logging session timestamps and executed commands via TACACS+ maps to Accounting.
Each scenario represents a distinct stage in identity and access management: Identification is claiming an identity (entering a UPN); Authentication is proving that identity (validating FIDO2 keys and PINs); Authorization is determining allowable actions (checking SAML attributes against ACLs); and Accounting is recording session data and actions for audit logs (logging TACACS+ execution details).
Adım Adım Çözüm
Anahtar Kavram
Authentication, Authorization, and Accounting (AAA) Framework