❚

35–52 minutes

reading

·

Identity: the new Operating System of Trust

Conceptual identity and access management illustration linking lost access, role changes and dependency outages to verification, permissions and supported recovery
Conceptual illustration: dependable identity services protect people through changing circumstances, not only successful sign-in (after Magritte)

🧭 Executive summary

A successful login does not settle who controls an account, whether its permissions remain justified or whether the legitimate person can recover access safely. Identity and access management (IAM) brings together the policies, processes and systems governing who may access what. It needs to work throughout the human-account lifecycle. My argument is that leaders should buy and govern that whole service, not regard a working sign-in screen as the finished job.

The evidence supports that broader view. The United Kingdom’s (UK) National Cyber Security Centre (NCSC) connects appropriate access, proportionate authentication and joiner, mover and leaver processes with making legitimate work easier in its identity and access management guidance. Authentication means checking control of a registered means of signing in, rather than proving that every later action is appropriate. Joiner, mover and leaver processes grant, adjust and remove access as someone’s relationship with the organisation changes.

The United States’ (US) National Institute of Standards and Technology (NIST) treats digital identity risk as more than a problem for the organisation running the system. Its fourth-revision Digital Identity Guidelines also ask designers to consider the people using the service, including their privacy, experience and routes to redress. Redress means a way to challenge and resolve a problem with the identity service. I regard these as complementary parts of a dependable service. Individual design choices can still involve trade-offs that need to be explained and tested.

The Cyber Security Breaches Survey 2025/2026 supplies UK business and charity context, not a measure of a particular account’s risk or proof that an IAM product works. The joint Scattered Spider advisory revised in July 2025 describes support requests used to change account control. Its reporting supports scrutiny of recovery decisions, not blame directed at individual help-desk staff or an assumed explanation for every retail incident.

The practical decisions are to name an accountable business owner, agree risk-based access-removal timescales and fund usable recovery and controlled emergency access, an approved exceptional route when ordinary access is unavailable. Ownership must cover enrolment (establishing an account and its means of signing in), authentication, permissions, account recovery (regaining account control) and removal. Use strong authentication and make elevated administration limited and temporary where appropriate. Check that removal reaches applications and existing sessions, meaning continuing signed-in interactions, rather than stopping at a disabled central account.

Design around the people who actually depend on the service: customers, colleagues, contractors, residents, beneficiaries and volunteers. They will not all have the same devices, connectivity, accessibility needs or support arrangements. Require suppliers to explain their responsibilities, limitations, dependencies and full-service costs. Ask what happens when the ordinary route fails, without assuming that a pricing model, outsourcing decision or commercial incentive caused an incident.

Start with the most consequential human-account journeys and their owners. Agree representative, authorised tests of recovery, role changes and dependency failures, meaning loss of a service the identity process needs. Examine usability, rejected impersonation, actual access removal and restoration separately. Record the conditions, exceptions and untested assumptions, then correct, retest and review after material changes. These are proposed acceptance practices to validate locally, not guarantees of continuity, security or universal recovery success. The customer assurance question is whether the supplier can show dependable outcomes in conditions representative of your environment.

🔑 Why a valid login does not prove appropriate access

Three parallel panels distinguish identity proofing, authentication and authorisation, showing why a valid login does not establish continuing permission
Conceptual illustration: confidence in identity, control of a sign-in method and permission to act answer different questions (after Mondriaan)

IAM answers several related but different questions. Identity proofing concerns the confidence needed in a claimed identity. Authentication checks control of an associated authenticator, a means used to sign in, such as a password or passkey. The credential records the binding between the account and its authenticators. A passkey is a device-managed digital key used instead of a password. Authorisation decides what the account may do. NIST separates identity proofing, authentication and federation, the arrangements through which one service relies on identity information from another, in its Digital Identity Guidelines. Keeping these distinctions clear prevents a strong login method being mistaken for a complete protection programme.

Authentication provides risk-based assurance, a level of confidence assessed against risk, not certainty about every action that follows. NIST’s authentication guidance describes checking that a claimant controls authenticators associated with an account. That does not, by itself, establish that a permission remains justified after a transfer, that a recovery request is legitimate or that the organisation can safely operate without one of its suppliers. Those are additional questions, requiring their own evidence and decisions.

Consider an illustrative example, not a reported incident. A colleague moves from payroll into another department. Their passkey still works perfectly, but their old payroll permissions remain. The authentication technology has done its job; the business process has not. The appropriate response is not another reminder about passwords. It is an effective role-change process that removes obsolete access, verifies the result and assigns responsibility when a connected application does not update.

Customers face a related problem from the other direction. Someone who loses a telephone may be the legitimate account holder while lacking the normal means of proving it. Imagine a recovery screen that only says, “enter the code sent to your phone”. That is illustrative wording, not a quotation from a named service, and it does not resolve the lost-phone problem. Conversely, a process that accepts a convincing story without adequate checks may restore access to the wrong person. The design question is how to offer a safe alternative, not whether security or customer service should win.

I therefore use “operating system of trust” as a business metaphor, not a claim that identity replaces every other safeguard. It describes the connected decisions that let people act, challenge suspicious requests and withdraw authority when circumstances change. The boundaries matter: this article concerns human accounts and their supporting processes. Machine-account lifecycle and cross-environment detection deserve separate treatment. Devices matter here only insofar as their condition, loss or unavailability affects a person’s access.

This approach follows the NCSC’s emphasis on who needs access and under what conditions. It also changes the executive conversation. Instead of asking whether IAM software has been installed, ask whether the organisation can demonstrate the right outcome for the person, the service and the information involved, including when the ordinary route fails.

🔎 What recent research and developments actually establish

🔄 Protect human accounts from joining to leaving

🛡️ Use strong authentication and make privileged access temporary

💻 Devices: the other half of every access request

⚙️ Machines, workloads and artificial intelligence agents

🛟 Design account recovery around the person who needs help

🔗 Plan for identity dependencies becoming unavailable

🤝 Make suppliers accountable for customer outcomes, not just features

🧪 Demand representative testing and evidence you can examine

🧭 Conclusion: Leadership decisions and practical actions

References and further reading (much more here)

Research cut-off: 11 November 2026.

References contains cited publications, source pages and definition sources.

Further Reading contains additional background and identity navigation.

Comments

Leave a Reply

❚

Latest posts