IAM Roles

An overview of the professional roles that design, operate, and govern how identities are managed and how access to systems and data is controlled.

1 мин читањаажурирано 15. окт 2026.florianamette1 сарадник
Питајте асистента (MCP)Уреди на GitHub-у

Identity and access management roles share a single concern: making sure the right people and systems hold the right access to the right resources at the right time, and no more. Because most security controls ultimately depend on knowing who is acting and what they are permitted to do, this discipline sits at the center of modern security programs. The roles below build, run, and oversee the identity fabric an organization relies on.

What these roles share#

  • A focus on identity as the control plane, where access decisions, not network perimeters, increasingly define the security boundary.
  • A common vocabulary of authentication, authorization, directories, federation, and least privilege.
  • A spectrum from hands-on operations through engineering and governance to long-range architecture, so practitioners often move between them as experience grows.

Roles#

  • IAM Analyst: operates the program day to day, handling joiner, mover, and leaver processes, access requests, and reviews.
  • IAM Engineer: builds and automates the identity platform, integrating applications, single sign-on, and provisioning.
  • IAM Architect: defines the target state, selects technologies, and keeps identity design aligned with security and business strategy.
  • Access Governance Specialist: oversees entitlements through certification campaigns, segregation of duties, and compliance evidence.
  • PAM Specialist: secures privileged accounts and credentials, the high-value access whose misuse would cause the most harm.

References#