Let me tell you about a small administrative IT team at a spine-care hospital group, one I have made up so that nobody has to be embarrassed. They run the patient-facing website, the appointment-reminder tool and a few reporting jobs. Their week looks ordinary until the afternoon they decide to count how many digital keys exist across their systems, and the number turns out to be much larger than anybody guessed. That afternoon is where their IAMOps story starts.
The story is only about back-office technology: accounts, credentials and rules for software. It says nothing about care, clinicians or outcomes, and it is general information rather than advice for any particular organisation.
The key drawer nobody opened
The team lead, whom I will just call the lead, starts with a spreadsheet and a coffee. Each automated job that publishes the website or pulls a report needs some way to prove who it is. Over the years those proofs had piled up as long-lived access keys pasted into settings pages. Some belonged to jobs that no longer existed. One belonged to a contractor’s test script.
Think of a hospital’s physical key cabinet. If it holds copies cut years ago, with no log of who borrowed which, the cabinet is a risk even if nothing has gone wrong. Digital keys are the same, except they can be copied silently.
The Ops Atlas, which the team found while searching for a name for their problem, treats this exact situation as one of the ordinary levers of the discipline it calls IAMOps: where possible, swap stored secrets for short-lived identities issued at the moment a job runs. The Atlas is careful to call the label informal, so the team treats it as a useful vocabulary and not a certification.
Week one: count, name, and stop the bleeding
The lead sets a modest first target, the same sort of ladder the Atlas describes in its maturity notes: before improving anything, stop creating new long-lived keys. Every new automation must use a short-lived identity or wait.
- Every key gets an owner and a purpose written beside it.
- Keys with no owner are scheduled for shutdown after a two-week notice.
- No new permanent keys, with exceptions logged in a shared register.
It is humble work, and it causes the first moment of friction. A developer says the notice period feels slow. The lead answers that a slow week is cheaper than a mystery next year, and the room, mostly, agrees.
Week three: the trust rule that was too friendly
The team moves their website publishing job to a federated login: the build system presents a signed statement about itself, and the cloud account decides whether to trust it. Someone writes the trust rule to accept any build from the organisation’s code namespace. It works on the first try, and the lead feels a small chill.
Why the chill? The Atlas warns that a wildcard on the subject of such a statement admits every repository under that name, not just the one you meant. The team rewrites the rule to name one repository and one environment, and adds a note explaining why. A rule that works at once deserves a second look, especially when it works for everyone.
Week six: a quiet incident that did not happen
One Friday an old staging credential, still unrevoked, shows up in a pasted log. In the old world this would mean a long weekend of rotating things in a panic. In the new one, the credential is already on the retirement list and has been dead for ten days. The lead reads the alert, closes it, and goes home.
The Atlas is blunt about why this pattern matters across the industry. It points to survey data in which a large share of cloud users, in the range of well over half for some platforms, still carry active keys older than a year. The team had been one of them. Being able to say “that key was retired last month” is the payoff for dull preparation.
What they measured
Rather than collect dashboards, the team tracked three plain numbers each month:
- How much of the credential stock had passed the three-month mark.
- How many production changes were followed by an unexpected denial within a day.
- How many exceptions on the register were past their review date.
After a quarter the first number had fallen sharply, the second was small enough to count on one hand, and the third was zero because someone finally owned the register.
Where the team asked for outside perspective
Over the quarter the team also read around the site for context on how groups like theirs plan technology alongside services. A post on keeping automated machines checked and maintained gave them a useful habit: write the routine down so it survives staff changes. Another piece, a broad overview of operations disciplines and learning paths, helped the newer members see where access work sits among its neighbours.
Lessons the lead wrote on the whiteboard
When the quarter ended, the lead wrote a short list that the team still keeps near the monitor.
- Count before you clean. You cannot shrink what you have not listed.
- Prefer an identity that expires on its own to a secret someone must remember to retire.
- If a trust rule works for everybody, ask whom it was supposed to exclude.
- Give every exception a name and a date.
- Celebrate the incident that did not happen, quietly.
The invented team in this story is not special. Their tools were ordinary and their budget was small. What changed was that they began to treat the rules for “who may do what” as something with an owner, a history and a schedule. That is the whole idea behind IAMOps, and it scales from a three-person hospital IT office to a much larger organisation without changing its shape.
Should your own group want a starting point, begin with the inventory. Open a blank document, write down each long-lived credential your office has ever created, and put a person’s name next to every line. The awkwardness of that first list is all the motivation you need to start on the second, and it costs nothing but an hour.
A final word on tone. Nobody in the story was blamed for the drawer of old keys, because every team that grows quickly ends up with one. The useful question was never who left it there, but what small habit would keep it from refilling. Habits, more than tools, are what the lead was really building, and they are easier to hand to a new colleague than any clever script.
