📖 What is Identity and Access Management (IAM)?
Identity and Access Management (IAM) is a framework of policies and technologies that ensures the right individuals have access to the right resources at the right times. It encompasses the processes of identification, authentication, and authorization.
"IAM is the umbrella term; remember that authentication proves who you are, while authorization determines what you can actually do."
📚 Certification: CompTIA Security+ Certification Exam (SY0-701)
🔑 What are the Key Concepts of Identity and Access Management (IAM)?
- ▸ The Principle of Least Privilege ensures users are granted only the minimum permissions necessary to perform their job functions, reducing the potential attack surface.
- ▸ Role-Based Access Control (RBAC) simplifies management by assigning permissions to roles rather than individuals, ensuring consistency across similar job functions.
- ▸ Multi-Factor Authentication (MFA) strengthens identity verification by requiring two or more independent categories of credentials, such as passwords and biometric scans.
- ▸ Identity Lifecycle Management covers the entire process of account creation (provisioning), modification, and timely removal (deprovisioning) when an employee leaves.
- ▸ The distinction between authentication and authorization is critical; authentication verifies a user's identity, while authorization determines their specific access rights.
🎯 How does Identity and Access Management (IAM) appear on the SY0-701 Exam?
You may be asked to identify the best access control model for a large organization where employees share identical job responsibilities and permission requirements.
A scenario might describe a security breach caused by a former employee still having system access, requiring you to identify a failure in the deprovisioning process.
Expect questions where you must recommend a solution to prevent lateral movement within a network by restricting user permissions to the bare minimum.
❓ Frequently Asked Questions
What is the difference between RBAC and ABAC in an IAM context?
RBAC assigns permissions based on a user's job title or role. ABAC is more granular, granting access based on attributes like time of day, location, or specific project tags.
How does 'privilege creep' occur and how does IAM prevent it?
Privilege creep happens when users accumulate permissions over time as they change roles. Regular access reviews and automated deprovisioning are the primary IAM defenses.