Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.
5.1.2. Identity and Access Management
AAA Framework:
- Authentication: Prove who you are (credentials, certificates, biometrics)
- Authorization: What you're allowed to do (permissions, roles)
- Accounting: Record what you did (audit logs)
Authentication Methods:
- Multi-factor (MFA): Combines two or more different factor types—something you know (password), have (token or authenticator app), are (biometric), or somewhere you are (location). A password plus a PIN is still single-factor
- Certificate-based: PKI certificates prove identity
- SSO (Single Sign-On): Authenticate once, access multiple systems
- LDAP: Directory service for centralized identity management
PAM (Privileged Access Management): Vaults administrative credentials and issues them on a check-out basis for a limited time (just-in-time access), with every use logged—shrinking the window in which privileged credentials can be misused and preserving individual accountability.
AAA Protocols:
- RADIUS: Remote Authentication Dial-In User Service—common for network access (UDP 1812/1813; encrypts only the password)
- TACACS+: Cisco protocol (TCP 49)—separates authentication, authorization, accounting; encrypts entire payload
Access Control Models (authorization):
| Model | How access is decided | Example |
|---|---|---|
| RBAC (Role-Based) | Permissions attach to job roles; users inherit them from their role | Help desk role can reset passwords but not change switch configs |
| Rule-based | Administrator-defined conditions applied to every request | Allow a server only from a given subnet during business hours |
| DAC (Discretionary) | The resource owner grants access at their discretion | A user shares a folder and sets its permissions |
| MAC (Mandatory) | The system compares classification labels to user clearance; users can't change them | Secret / Top Secret labels |
| ABAC (Attribute-Based) | Policies evaluate attributes of user, resource, and environment | Allow if department = Finance and device is managed |
Authorization Principles:
- Privilege creep: Access that accumulates as a user changes roles. It violates least privilege—revoke old-role access at every transfer, and run periodic access reviews to catch what was missed.
- Separation of duties: Split a critical task so no single person can complete it alone (the person who approves payments can't also issue them).
Enroll to unlock the 2 flashcards for this section and review them on a spaced-repetition schedule.
Written byAlvin Varughese
Founder•20 professional certifications