1/53
Looks like no tags are added yet.
IAM
Identity and Access Management: ensures the right individuals have the right access to the right resources at the right times for the right reasons.
Identification
User claims an identity with a unique identifier (username, email address).
Authentication
Verifies the identity of a user, device, or system, typically by validating credentials (passwords, biometrics, MFA).
Authorization
Determines the permissions or access levels of an authenticated user; role-based access control is often used.
Accounting (auditing)
Tracks and records user activity (logins, actions, changes) to detect incidents and provide evidence.
Which IAM process is a log of logins and changes?
Accounting (auditing).
Provisioning
Creating user accounts, assigning permissions, and granting system access.
Deprovisioning
Removing access rights when they are no longer needed, such as when an employee leaves.
Identity proofing
Verifying a user's identity (personal details, driver's license, passport) before creating their account.
Interoperability
Ability of different systems, devices, and applications to work together; in IAM, often via standards like SAML or OpenID Connect.
Attestation (IAM)
Validating that user accounts and access rights are correct and up to date through regular reviews and audits.
MFA
Multi-factor authentication: requires multiple methods from independent categories of credentials for a layered defense.
Something you know
Knowledge factor: password, PIN, answers to secret questions.
Something you have
Possession factor: smart card, hardware token (key fob), or software token on a device.
Something you are
Inherence factor: biometrics such as fingerprints, facial recognition, or voice recognition.
Somewhere you are
Location factor: based on IP address, GPS, or network connection; geographic restrictions can apply.
Something you do
Behavior factor: keystroke patterns or device interaction; rarely a primary factor but adds an extra layer.
Single-factor vs 2FA vs MFA
Single uses one factor; 2FA requires exactly two different factors; MFA uses two or more (up to five).
Tradeoff of more authentication factors
Generally safer, but less convenient for the end user.
Passkey
Passwordless alternative that uses public key cryptography and is secured by device authentication such as fingerprint or facial recognition.
Five password policy characteristics
Length, complexity, reuse, expiration, and age.
Password length guidance
Strong passwords should be at least 12 to 16 characters; longer passwords increase security exponentially.
Password complexity
Mix of uppercase, lowercase, numbers, and special characters; more character choices resist brute force better.
Password reuse risk
Reusing a password across accounts increases vulnerability because one breach exposes the others.
Password expiration downside
Overemphasis on forced changes leads users to choose poor passwords.
Password age
How long a password has been in use; older passwords have a higher risk of being compromised.
Password manager features
Password generation, auto-fill, secure sharing, and cross-platform access.
Why use a password manager?
It creates unique strong passwords for every account, preventing reuse and removing the need to remember them.
Passwordless authentication methods
Biometrics, hardware tokens, one-time passwords, magic links, and passkeys.
Magic link
One-time link sent by email that logs the user in automatically.
OTP
One-time password: sent to email or phone for a single use.
Brute force attack
Tries every possible character combination until the password is found; mitigated by length, complexity, login limits, MFA, and CAPTCHAs.
Dictionary attack
Uses a list of commonly used passwords (with number and symbol variations) to crack passwords.
Password spraying
Tries a few common passwords against many usernames; avoids account lockouts and targets weak passwords.
Why does password spraying avoid lockouts?
Each account only sees a few attempts, staying under the lockout threshold.
Hybrid attack
Combines brute force and dictionary methods, such as adding numbers or special characters to dictionary words.
SSO
Single sign-on: one set of credentials accesses multiple applications through a trust relationship with an identity provider.
IdP
Identity Provider: the system that authenticates the user and issues the assertion other applications trust.
SSO benefits
Better user experience, increased productivity, lower IT support costs, and encouragement of stronger passwords.
LDAP
Lightweight Directory Access Protocol: accesses and maintains distributed directory information; stores users, group memberships, and roles for authentication and authorization.
LDAPS
LDAP secured with SSL or StartTLS.
OAuth
Open Authorization: open standard for token-based access that lets third-party services access account information without exposing passwords; uses JSON Web Tokens.
SAML
Security Assertion Markup Language: logs users into applications based on a session elsewhere by redirecting them to an identity provider.
Why use SAML?
It eliminates the need for each service to authenticate users directly and decouples services from identity providers.
Federation
Links electronic identities across multiple identity management systems so users can reuse credentials across organizations; based on trust relationships.
Federation flow
Login initiation, redirect to the IdP, authentication, assertion generation, return to the service provider, verification and access.
Federation benefits
Simplified user experience, reduced administrative overhead, and less password reuse.
PAM
Privileged Access Management: restricts and monitors privileged access so least privilege is granted for specific tasks or roles.
JIT permissions
Just-in-time permissions: admin access granted only when needed for a task and revoked when it is complete.
Password vaulting
Stores and manages passwords in a secure digital vault; requires MFA to access and creates an audit trail.
Ephemeral credentials
Temporary accounts for time-limited access that are automatically disabled or deleted after a set period (the guide calls these temporal accounts).
MAC
Mandatory Access Control: uses security labels on users and resources; access is granted only if the user's label is equal to or higher than the resource's.
DAC
Discretionary Access Control: resource owners decide which users can access their resources.
RBAC (role-based)
Users are assigned to roles; enforces minimum privileges and handles job turnover well.