CIS-1355 · Security Engineering · Module 7

Identity and Access Management (IAM)

Verify identities, protect credentials, and grant only the access each task requires.

Establish identity and verify sign-ins

Identity and access management (IAM) covers digital identities, credentials, and resource permissions across the account lifecycle. Identity proofing establishes who an applicant is during enrollment when required. Authentication later checks that the claimant controls an authenticator bound to the account. Authorization decides which actions the account can perform. Accounting records activity for review. Authentication, authorization, and accounting form the AAA framework.

Something you know
A password or PIN. Two knowledge secrets, such as a password and a PIN, still represent one factor type.
Something you have
A hardware or software token, a smart card, or a security key. Hardware and app-based one-time passwords (OTPs) can be phished. A FIDO security key can use USB or NFC to sign a challenge tied to the service.
Something you are
Physical traits such as fingerprints, face, iris, or vein patterns. Biometrics can produce false matches or rejections and require privacy safeguards and a recovery option. A device can use a biometric to activate a cryptographic authenticator locally.

Multifactor authentication (MFA) uses distinct factor types. SMS codes can help protect password-based accounts, but phishing, number porting, and SIM swaps create risks. NIST treats use of the public telephone network for out-of-band authentication as restricted. Prefer phishing-resistant authentication where available.

Location, device posture, and patterns such as typing rhythm or gait can help assess sign-in risk. Voice can reflect both physical and behavioral characteristics. Cognitive or knowledge-based prompts may draw on personal history, and a trusted person can sometimes help with enrollment or recovery. Evaluate these signals for reliability and privacy before using them in an access decision.

NIST · Identity Proofing and Enrollment · NIST · Authentication and Authenticator Management

Recognize password attacks and protect stored verifiers

Store password verifiers using a dedicated password hashing scheme, such as Argon2id where appropriate. A unique random salt prevents identical passwords from producing identical stored verifiers and limits reuse of precomputed work. A pepper is a separate secret kept outside the password database. One approach applies a keyed HMAC to the password hash. Key stretching raises the cost of each offline guess. A fast general-purpose hash alone is unsuitable for password storage.

Replace default credentials and use long, unique passwords generated and stored by an approved password manager. Use an enterprise vault to control and audit access to shared or privileged secrets where needed. Length helps when the password is hard to predict. NIST calls for at least 15 characters when a password is the sole factor, screening against common or compromised passwords, and changing passwords when there is evidence of compromise. Routine expiration adds user burden. Rate-limit failed attempts and monitor failures across accounts as well as within each account.

NIST · Password requirements · OWASP · Password Storage Cheat Sheet

Separate federation, single sign-on, and directory access

Single sign-on (SSO) allows one authentication session to support access to multiple applications. Federation allows a relying service to trust identity assertions from an identity provider across an administrative or trust boundary. SSO can also work within one organization.

SAML
Uses XML assertions to exchange information about authentication and identity attributes. It is commonly used for enterprise browser SSO.
LDAP
Provides access to directory entries such as users and groups. A directory can support the identity provider without serving as the federation protocol.
OAuth 2.0 and OpenID Connect
OAuth 2.0 is a framework for delegated authorization. OpenID Connect (OIDC) adds an authentication layer, including an ID token that conveys identity claims to the application.

Passwordless authentication can use passkeys. A passkey uses a public-key credential scoped to a relying party. It may be device-bound or synced through a credential provider. Set enrollment and account recovery rules with the same care as routine sign-in.

OpenID Foundation · How OpenID Connect works · RFC 4511 · LDAP

Grant, review, and remove access

A data owner typically approves how an asset is used and who may have access. Custodians or stewards implement and maintain safeguards according to policy. In privacy law such as the GDPR, a controller determines the purposes and means of processing, a processor acts on the controller’s behalf, and a data protection officer advises and monitors compliance where that role applies.

Discretionary access control (DAC)
An authorized owner or administrator can grant access to a resource, for example through file permissions.
Mandatory access control (MAC)
A centrally enforced policy governs access, often using subject clearances and resource labels.
Role-based access control (RBAC)
Permissions are assigned to roles such as payroll reviewer. Users receive permissions through role membership.
Rule-based access control
Access depends on predefined rules, such as allowing administrative connections only from an approved network.
Attribute-based access control (ABAC)
Policy evaluates attributes of the subject, resource, requested action, or environment. A rule might allow a technician to view records only for the site assigned to their account.

An access control list (ACL) specifies who can perform particular operations on an object, such as reading or modifying a folder. Per-user entries can become hard to audit at scale. Groups, role assignments, and inheritance can simplify updates when used consistently. Review effective permissions as well as the visible list.

Privileged access management (PAM) controls elevated access with measures such as separate admin accounts, time-limited elevation, approval, credential vaulting, and activity logging. Review access when people change roles or leave.

NIST · Guide to Attribute Based Access Control · EUR-Lex · GDPR, Articles 4 and 39

Practice case

A sign-in alert and excessive payroll access. A central identity provider records attempts using one common password across dozens of accounts. A support contractor reports that they could view a payroll export after signing in to the payroll portal through SSO. Their account belongs to a support group that inherited read access to the export folder.

What type of password attack does the pattern suggest? What would help confirm whether it succeeded? Which controls would you change at the identity provider and on the export folder?

Review a possible answer

The pattern suggests password spraying. Review successful sign-ins, MFA events, session issuance, and related endpoint or network records. Monitor attempts across accounts, rate-limit failures, and move high-risk users to phishing-resistant MFA. If an account was compromised, revoke its sessions and remediate its credentials.

Remove the inherited grant that exposes payroll data to the support group and limit read access to the authorized payroll role. Test effective permissions with both a support account and a payroll account. Review available access logs to determine which records were opened or exported. SSO established the contractor’s identity. The folder ACL governed access to the export.

Read and watch