7-1 IAM Concepts and Principles
1. Identity
Identity refers to the unique characteristics that define an individual or entity within a system. It is the foundation of IAM, as it establishes who or what is accessing resources.
Example: In a corporate network, an employee's identity might be defined by their username, employee ID, and department. This identity is used to determine their access rights and permissions.
Analogy: Think of identity as a passport that uniquely identifies a person. Just as a passport verifies a person's nationality and identity, an identity in IAM verifies a user's role and permissions within a system.
2. Authentication
Authentication is the process of verifying the identity of a user or system. It ensures that the person or entity claiming to be someone is indeed who they say they are.
Example: When you log into your email account, the system asks for your username and password. The system then checks these credentials against its database to authenticate your identity.
Analogy: Authentication is like showing your ID at a security checkpoint. The guard verifies your ID to ensure you are who you claim to be before allowing you to pass.
3. Authorization
Authorization is the process of granting or denying access to specific resources or functionalities based on the user's authenticated identity and predefined policies.
Example: After logging into a corporate network, an employee might be authorized to access certain files and applications based on their role and department.
Analogy: Authorization is like having a keycard that grants access to specific rooms in a building. The keycard determines which rooms you can enter based on your role and permissions.
4. Accountability
Accountability ensures that actions taken within a system can be traced back to the individual or entity responsible. It involves logging and monitoring activities to maintain transparency and responsibility.
Example: In a financial system, every transaction is logged with the user's identity and timestamp. This allows for auditing and accountability in case of any discrepancies.
Analogy: Accountability is like having a sign-in sheet at a meeting. Every attendee signs in, ensuring that their presence and actions can be tracked and verified.
5. Identity Lifecycle Management
Identity Lifecycle Management (ILM) involves managing the entire lifecycle of an identity, from creation to deactivation. This includes onboarding new users, managing changes, and deactivating accounts when no longer needed.
Example: When a new employee joins a company, their identity is created in the system, assigned roles and permissions, and updated as their role changes. When they leave, their account is deactivated.
Analogy: ILM is like managing a library card. When a new member joins, their card is created, updated with their borrowing history, and eventually deactivated when they leave the library.
6. Single Sign-On (SSO)
Single Sign-On (SSO) allows users to authenticate once and gain access to multiple applications without needing to re-enter credentials. This simplifies the user experience and enhances security.
Example: After logging into a corporate network using SSO, an employee can access email, HR systems, and project management tools without needing to log in separately to each application.
Analogy: SSO is like having a master key that opens multiple doors in a building. Once you unlock the main door, you can access all the rooms without needing additional keys.
7. Multi-Factor Authentication (MFA)
Multi-Factor Authentication (MFA) enhances security by requiring users to provide two or more verification factors to gain access. This adds an extra layer of security beyond just a password.
Example: When logging into a banking app, you might need to enter a password, then verify your identity using a one-time code sent to your mobile device.
Analogy: MFA is like having a combination lock on a safe. You need both the correct combination (password) and the physical key (one-time code) to open the safe, ensuring that even if one is compromised, the safe remains secure.