Cybernion
← Insights

Security

What Is Identity and Access Management (IAM)?

30 Sept 2026 · Updated 30 Sept 2026

Identity and access management (IAM) is the discipline of controlling who and what can access an organisation’s systems and data, and proving those decisions on demand. It combines authentication (proving identity), authorisation (deciding what that identity can do) and lifecycle management (creating, changing and removing access) into one governed process, usually backed by a directory, single sign-on and multi-factor authentication.

Most breaches do not start with a clever exploit. They start with a valid set of credentials that should not have worked, or an account that should have been disabled months earlier. IAM is the practice built specifically to close that gap.

What is identity and access management

IAM is the combination of policy, process and technology that answers two questions for every user and system account in an organisation: who is this, and what is it allowed to do. The first question is authentication, proving that a login attempt truly belongs to the person or system it claims to. The second is authorisation, deciding what that verified identity can see, change or run once it is inside.

A mature IAM programme also manages the full lifecycle of an identity, from the day someone joins the organisation through every role change, project assignment and system rollout, to the day their access is removed. That lifecycle discipline, often shortened to joiner mover leaver, is where a lot of IAM programmes quietly fail. Access accumulates as people change roles, and it rarely gets removed at the same rate it gets granted.

IAM is not limited to human employees. Contractors, partners, customers accessing a portal, and non-human identities such as service accounts, API keys and application to application connections all need to be identified, authorised and reviewed. In many cloud environments, non-human identities now outnumber human ones by a wide margin, which is part of why IAM has grown from a helpdesk function into a security discipline.

What are the core components of an IAM system

A typical IAM setup has several moving parts working together rather than one product doing everything.

Identity store. A central directory, such as Microsoft Entra ID (formerly Azure AD), Okta, or an on premises directory, holds the authoritative record of every identity and its attributes.

Authentication. The mechanism that verifies a login attempt, ranging from a password alone (weak) to multi-factor authentication combining a password with a second factor, through to passwordless methods like passkeys.

Authorisation. The logic that decides what an authenticated identity can do, commonly implemented through role based access control (assigning permissions to job roles) or the more granular attribute based access control (evaluating multiple attributes like department, location and device state at the point of access).

Single sign-on. A layer that lets a user authenticate once and access multiple connected applications without logging in again to each one.

Provisioning and deprovisioning. Automated workflows that create accounts and grant access when someone joins or changes role, and remove access promptly when they leave or no longer need it. This is consistently the weakest link in manual IAM setups.

Governance and audit. Periodic access reviews, logging of authentication and authorisation events, and reporting that lets an organisation demonstrate, not just assert, who had access to what.

How does IAM differ from PAM and identity governance

IAM is the umbrella term. Two more specific disciplines fall underneath it and are often confused with it.

Privileged access management (PAM) focuses narrowly on the smaller set of accounts that carry elevated rights, domain administrators, database administrators, cloud root accounts and service accounts, because a compromise of one of these accounts causes disproportionate damage. PAM adds controls like credential vaulting, just in time elevation and session recording that would be excessive for an ordinary user account.

Identity governance and administration (IGA) focuses on the oversight layer, periodic access certification, segregation of duties checks, and reporting that proves access matches policy over time. Where IAM grants and enforces access day to day, IGA periodically asks whether the access that has accumulated still makes sense.

Together, IAM, PAM and IGA form a layered approach: broad identity management for everyone, tighter controls for privileged accounts, and ongoing governance to catch drift between the two.

What standards make IAM interoperable

IAM depends on open standards so that identity providers, applications and cloud platforms can work together without custom integration for every pairing.

SAML (Security Assertion Markup Language) is an older but still widely used standard for exchanging authentication and authorisation data between an identity provider and a service provider, commonly used for enterprise single sign-on.

OpenID Connect (OIDC) is a modern authentication layer built on top of OAuth 2.0, widely used for consumer and cloud application logins, including the familiar “sign in with” options.

OAuth 2.0 is an authorisation framework that lets one application access resources on behalf of a user without handling that user’s password directly, commonly used for API access and third party integrations.

SCIM (System for Cross-domain Identity Management) automates the creation, update and removal of user accounts across connected systems, which is what makes prompt deprovisioning practical at scale rather than dependent on someone remembering to email IT.

Choosing products that support these standards, rather than proprietary alternatives, keeps an organisation’s identity architecture portable and reduces the amount of custom code needed to connect a new application.

Why IAM matters for security and compliance in Australia

Credential based attacks remain one of the most common ways an attacker gets a foothold, whether through phishing, credential stuffing, or simple password reuse. IAM controls, particularly multi-factor authentication and prompt deprovisioning, directly close off that path.

The ASD’s Essential Eight includes multi-factor authentication and restricting administrative privileges as two of its eight mitigation strategies, both of which are IAM controls in practice. The Information Security Manual (ISM) sets out detailed identity and access requirements for government and regulated systems. ISO 27001 Annex A includes a dedicated set of access control clauses covering user access provisioning, access rights review and privileged access, which are assessed directly against how an organisation’s IAM programme actually operates, not just what its policy says.

For organisations handling Australian government information, sound IAM practice, including least privilege and demonstrable access reviews, is a practical prerequisite for a successful IRAP assessment, because access control weaknesses are one of the most common findings.

How do we build or improve an IAM programme

Most organisations already have some IAM in place, usually a directory and basic single sign-on, and the improvement work is in tightening what exists rather than starting from nothing.

Start with an accurate inventory of who has access to what, including service accounts and shared logins, which are almost always undercounted. Move toward role based or attribute based access control instead of granting permissions one request at a time. Automate provisioning and, particularly, deprovisioning, since delayed removal of access is the most common gap found in audits. Add multi-factor authentication everywhere it is not already enforced, prioritising anything internet facing or privileged. Establish a regular cadence, commonly quarterly, for access reviews where managers or system owners confirm that existing access is still needed. None of this requires a large platform on day one. A well configured directory with enforced MFA and a disciplined manual review process delivers most of the security benefit before any specialised IAM product is purchased.

Frequently asked questions

What is identity and access management?

Identity and access management (IAM) is the set of policies, processes and technology an organisation uses to make sure the right people and systems have the right access to the right resources, at the right time, for the right reasons. It covers proving who a user is (authentication), deciding what they are allowed to do (authorisation), and keeping a record of both. IAM spans employees, contractors, partners and increasingly non-human identities like service accounts and applications.

What are the core components of IAM?

IAM systems typically include an identity store that holds user records, authentication mechanisms such as passwords and multi-factor authentication, authorisation logic that maps identities to permissions through roles or attributes, single sign-on to reduce repeated logins, and provisioning workflows that create, change and remove access as people join, move within, and leave the organisation. Auditing and reporting run underneath all of it, recording who accessed what and when.

How is IAM different from PAM?

IAM manages access for the general population of users to everyday systems and applications. Privileged access management (PAM) is a specialised subset focused specifically on accounts with elevated rights, such as domain administrators, database administrators and service accounts, which can cause disproportionate damage if compromised. Most organisations run PAM as a tighter, more heavily monitored layer on top of a broader IAM programme rather than as a separate discipline.

What identity standards does IAM rely on?

Common standards include SAML (Security Assertion Markup Language) and OpenID Connect for single sign-on and federated authentication, OAuth 2.0 for delegated authorisation between applications, and SCIM (System for Cross-domain Identity Management) for automating the creation and removal of user accounts across systems. Using open standards instead of proprietary integrations lets an organisation connect identity providers to cloud applications without custom code for every pairing.

Why does IAM matter for Australian organisations?

Compromised credentials are consistently one of the most common ways attackers gain a foothold, and the ASD’s Essential Eight includes both multi-factor authentication and restricting administrative privileges as two of its eight mitigation strategies. IAM is also directly assessed under ISO 27001 Annex A access control clauses and is a practical prerequisite for passing an IRAP assessment on any system handling government information.

Sources:

  1. Digital Identity Guidelines, SP 800-63-4, National Institute of Standards and Technology, 2025
  2. Essential Eight, Australian Signals Directorate, 2026
  3. ISO/IEC 27001:2022, International Organization for Standardization, 2022
  4. Security Assertion Markup Language (SAML) V2.0, OASIS, 2005

Last updated: 30 August, 2026

Talk to us about your engagement

A scoped proposal within one business day.