Skip to content

170 practical guides on SAP, cybersecurity and AI, $9.99 each. Shop all books ›

0

Blog›Cybersecurity

What Is Identity and Access Management (IAM)? A Plain Guide

Identity and access management decides who can log in and what they can do. Learn the identity lifecycle, which MFA methods are strongest, least privilege, single sign-on, privileged access and access reviews.

Most breaches don’t start with a clever exploit. Often someone simply logs in, using a password that was stolen, guessed or bought. Verizon’s 2025 Data Breach Investigations Report found that credential abuse was the most common way attackers first got in, at 22% of breaches, slightly ahead of exploited vulnerabilities at 20%. Identity and access management is the discipline that decides who can log in and what they can do once they’re inside.

Identity and access management (IAM) is the set of processes and tools an organization uses to create and manage digital identities, verify that people and systems are who they claim to be, and control what each one can access. NIST describes the goal as making sure the right people and things have the right access to the right resources at the right time.

In one sentence: IAM answers three questions for every login and every action: who are you, can you prove it, and are you allowed to do this?

Key takeaways

  • IAM covers identities, authentication (proving who you are) and authorization (what you’re allowed to do).
  • Stolen or misused credentials were the top initial access vector in Verizon’s 2025 report.
  • The identity lifecycle (joiner, mover, leaver) is where most access problems start.
  • CISA calls phishing-resistant MFA, such as FIDO/WebAuthn, the gold standard.
  • Least privilege and regular access reviews keep access from piling up over time.

What are the parts of IAM?

IAM combines two related areas. Identity management is about creating and maintaining the identities themselves. Access management is about checking those identities at login and deciding what they can do. The building blocks:

Part Question it answers Examples
Identity Who or what is this? Employee accounts, contractor accounts, service accounts, device identities
Authentication Can you prove it? Passwords, authenticator apps, security keys, passkeys, certificates
Authorization What are you allowed to do? Roles, groups, permissions, policies
Governance Is the access still right? Access requests, approvals, periodic reviews, segregation of duties checks
Audit What actually happened? Login logs, change logs, admin activity records

People often mix up authentication and authorization because they happen close together. Authentication is showing your badge at the door. Authorization is which rooms your badge opens once you’re in the building.

Why does IAM matter so much?

Attackers go where it’s easiest. A working username and password, especially one with administrator rights, is easier than breaking through a well-patched system. That’s why credential abuse keeps showing up at the top of breach reports, and why phishing, which usually aims to steal credentials, sits close behind.

Weak IAM also creates problems that have nothing to do with outside attackers. Former employees whose accounts were never disabled, staff who have collected access from every job they’ve held, and shared administrator passwords all make it hard to say who did what. Auditors notice these quickly, and regulations in finance, healthcare and government expect strong access control.

A well-run IAM program fixes much of this. It makes logins harder to steal, limits what a stolen account can do and gives you a record of who had access to what and when.

What is the identity lifecycle?

Every identity goes through the same stages. IAM teams often call this joiner, mover, leaver.

Stage What should happen What often goes wrong
Joiner Create the account and give access based on the person’s role, ideally automatically from the HR system New hires get a copy of a colleague’s access, including things they don’t need
Mover Add access for the new role and remove access from the old one Old access is never removed, so people collect permissions over the years
Leaver Disable all accounts promptly when someone leaves Accounts in some systems are missed, especially apps outside the central directory

The mover stage is the quiet problem. It’s easy to add access when someone asks, and there’s rarely anyone asking to take it away. This slow build-up, sometimes called privilege creep, is one reason access reviews exist. It’s also how segregation of duties conflicts appear in systems like SAP, where one person ends up able to both create a vendor and pay it.

Non-human identities go through a lifecycle too. Service accounts, API keys and the accounts used by automation and AI agents often outnumber people, have broad permissions and never “leave.” They need owners, expiry dates and reviews just like employee accounts.

Which authentication methods are strongest?

Passwords alone are weak because they can be phished, guessed, reused across sites or stolen by malware. Multi-factor authentication (MFA) adds a second proof, but not all MFA is equal. CISA’s guidance ranks methods by how well they hold up against current attacks:

Method Strength Main weakness
FIDO/WebAuthn security keys and passkeys Strongest, phishing-resistant Needs supported devices and some rollout effort
PKI-based smart cards and certificates Strongest, phishing-resistant More infrastructure to manage
Authenticator app push with number matching Good interim option Can still be phished by a convincing fake login page
Authenticator app codes (one-time passwords) Better than nothing Users can be tricked into typing the code into a fake site
SMS or voice codes Weakest MFA SIM swapping and interception

CISA says any form of MFA is better than none, but calls phishing-resistant MFA the gold standard and urges organizations to make moving to it a high priority. The reason FIDO methods resist phishing is that the login is tied to the real website’s address using public key cryptography. A fake site can copy the look of the real one, but it can’t get a valid signature for the real domain.

A practical order of work: start with administrators and remote access, then email and other services exposed to the internet, then everyone else. Push notifications without number matching are open to “MFA fatigue,” where attackers send prompt after prompt until someone taps approve, so turn on number matching if you use push.

How do you decide what access people get?

Authorization needs a model. The common ones:

  • Role-based access control (RBAC). Permissions are grouped into roles that match jobs, such as “accounts payable clerk,” and people get roles. This is the most common model, including in SAP, where roles are built in transaction PFCG.
  • Attribute-based access control (ABAC). Decisions use attributes of the user, resource and situation, such as department, data classification or location. More flexible, but harder to design and explain.
  • Policy-based and just-in-time access. People get elevated access only when they need it, for a short time, often with approval. This is common for administrator work.

Whatever the model, the guiding idea is least privilege: give each identity the minimum access it needs to do its job, and nothing more. Least privilege limits the damage when an account is compromised and makes mistakes less costly.

What is single sign-on and federation?

Single sign-on (SSO) lets people log in once to a central identity provider and then reach many applications without signing in again. Federation is the trust arrangement behind it: the application trusts the identity provider’s statement that the user has signed in. Common standards for this include SAML and OpenID Connect, which builds on OAuth 2.0.

SSO helps security in several ways. People have fewer passwords to reuse, MFA can be enforced in one place, and disabling one account cuts off access to every connected app. The trade-off is concentration. The identity provider becomes a very valuable target, so it needs the strongest protection you have: phishing-resistant MFA for admins, tight change control and close monitoring.

What is privileged access management?

Privileged accounts, such as domain administrators, database administrators, cloud root accounts and SAP emergency users, can change almost anything. Privileged access management (PAM) is the part of IAM that protects them. Typical controls:

  • Store privileged passwords in a vault and rotate them automatically.
  • Grant admin rights just in time, for a set period, with approval.
  • Separate admin accounts from everyday accounts, so reading email never happens with admin rights.
  • Record or log privileged sessions and review them.
  • Require phishing-resistant MFA for every privileged login.

CISA makes the point directly in its MFA guidance: if an attacker compromises a system administrator’s account, they may be able to reach any system and any data in the organization. That’s why privileged access usually gets protected first.

How do access reviews work?

An access review (also called recertification) is a regular check where managers or system owners confirm that each person still needs the access they have. Done well, reviews catch privilege creep, leftover accounts and segregation of duties conflicts. Done badly, they turn into a “rubber stamp” where reviewers approve everything to get through the list.

Ways to make reviews useful:

  1. Show reviewers access in business terms (“can approve payments”) instead of technical names.
  2. Highlight what’s risky or unusual, such as privileged roles, conflicts or access not used in 90 days.
  3. Make removal easy and automatic once a reviewer says no.
  4. Review high-risk access more often than low-risk access.

In SAP environments, tools such as SAP Access Control within SAP GRC run these reviews and check for conflicts before access is granted.

A worked example: one stolen password, two outcomes

Picture a finance analyst at a mid-size company. She gets an email that looks like it comes from the IT help desk, clicks the link and types her password into a convincing fake login page. The attacker now has her password. What happens next depends almost entirely on IAM.

Company A uses passwords plus SMS codes. The fake page asks for the code too, she types it in, and the attacker logs in. Over the years she has moved from accounts payable to treasury to reporting, and nobody removed her old access, so the account can still create vendors and release payments. There is no single sign-on, so the same password works for several cloud apps she uses. The access review last quarter was approved in bulk. The attacker changes a vendor’s bank details and the next payment run sends money to the wrong account. It takes weeks to work out which systems were touched because logs are spread across many places.

Company B has the same analyst and the same phishing email. Here the login uses a passkey on her laptop. The fake site can’t produce a valid sign-in for the real domain, so the stolen password alone gets the attacker nowhere. Even if it had worked, her access matches her current reporting job only: her old payables and treasury roles were removed when she moved. Changing vendor bank details requires a second person to approve, and the identity provider flags the unusual login attempt to the security team, who reset her password the same morning.

The phishing email was identical in both companies. The difference was in the IAM basics: phishing-resistant MFA, a clean mover process, segregation of duties and central logging. None of it is exotic, and all of it is the kind of work IAM teams do every day.

Frequently asked questions

What is the difference between authentication and authorization?

Authentication proves who you are, for example with a password and a security key. Authorization decides what you’re allowed to do after that, based on your roles and permissions.

Is IAM only about employees?

No. IAM also covers contractors, partners, customers and non-human identities such as service accounts, API keys, devices and AI agents.

What is phishing-resistant MFA?

It’s MFA that a fake website can’t trick you into handing over, such as FIDO/WebAuthn security keys, passkeys and PKI smart cards. CISA calls it the gold standard.

Where should a small company start with IAM?

Turn on MFA everywhere it’s available, starting with email and admin accounts, use one identity provider for single sign-on where possible, and make sure leavers lose access on their last day.

The bottom line

IAM decides who gets in and what they can do, and stolen credentials remain one of the most common ways attackers get started. Manage the joiner, mover and leaver lifecycle carefully, move toward phishing-resistant MFA, give least privilege, protect administrator accounts first and run access reviews that actually remove access. Remember the non-human identities too, since they often hold the broadest permissions of all.

Sources: Verizon 2025 Data Breach Investigations Report announcement; CISA: Implementing Phishing-Resistant MFA; NIST glossary: identity and access management.

Go deeper with these books