Pilots trust checklists because memory fails at the worst moment. IdentityOps, the upkeep of the records that say who and what may sign in to an organisation’s systems, benefits from the same humility. A reference site called the Ops Atlas calls this field unsettled, since each vendor sketches its borders in a different place. What follows is a list of eight habits, written in the order a pilot might walk around an aircraft, that an aviation business can adopt without buying anything new.

1. Walk the whole aircraft: inventory every account

A walk-round starts with seeing everything, not only what you expect to see. Begin by listing every person, contractor and automated connection with a login to scheduling, maintenance, payroll and e-mail. Include the quiet ones: the export script, the weather-data connector, the simulator booking integration. Without this list, nothing else in the discipline has anything to stand on.

2. Read the tech log: record an owner for each entry

Every defect in a tech log has a name and a date beside it. Do the same for accounts. The Atlas suggests recording for each automated account who owns it, why it exists, the date it lapses and the interval between reviews, so that a credential never exists without somebody answerable for it.

3. Confirm currency: drive changes from the personnel record

An instructor’s medical and rating currency come from a controlled source. Accounts should too. Let the personnel system be the origin for joiners, movers and leavers, and have directories and applications follow it. Provisioning standards such as SCIM exist so that apps can receive those changes automatically, although the Atlas cautions that many software vendors keep that feature behind higher-priced plans.

4. Check the seals: protect sign-in properly

A seal that anyone can replicate is no seal. The Atlas says only hardware security keys built on the FIDO2 standard and certificate-based smart cards count as phishing-resistant, and recommends rolling them out to administrators first, then to anybody who touches e-mail, remote access or money, then to everyone. It also recommends long passwords, a blocklist and no scheduled expiry.

5. Close the door behind you: end sessions, not only accounts

Switching off a leaver’s account is like removing a name from the duty roster while the person still holds the hangar pass. The entry notes that signed-in sessions and tokens can outlive the account for anywhere from minutes to many hours, so a good leaver routine cancels them explicitly and checks inside each connected application. One vendor-specific warning appears in the entry: in one widely used identity service, deactivating a user is destructive across every connected app, while suspension keeps the assignments intact. Know which button you are pressing.

6. Plan the divert: write the recovery script before you need it

A crew does not invent a diversion procedure at altitude. Write the route back in for a person who has lost a phone: use a second method that they enrolled earlier; for assisted cases, a one-time code only once their manager has vouched for them directly; for accounts with wide reach, in-person style proofing and a second administrator’s sign-off. The Atlas advises against relying on a call-back to a phone number, citing SIM-swap tactics.

7. Inspect what has sat idle: sweep dormant accounts

Aircraft parked for months get extra inspections. Accounts that have not been used for ninety to one hundred and eighty days deserve the same. Exclude people on formal leave, emergency access logins and automated accounts with a registered longer rhythm, then disable the rest and watch for complaints. Disable, wait, then delete, so that a mistake is reversible.

8. Debrief with numbers: count outcomes end to end

After the flight comes the debrief. Count leavers who are fully gone from every application, not merely those disabled in the main directory. In the Atlas’s example, forty departures with thirty-six timely disables and three lingering application accounts yield 82.5 percent end to end instead of a flattering 90. Agree targets, such as a four-hour limit for disabling the main login and a day for all applications, then review them monthly.

A word on the links between systems

Aircraft depend on data links, and organisations depend on the connections one application makes to another. The Atlas points to the OAuth security guidance document (RFC 9700), which says the older implicit flow should not be used and the password-style grant must not be used at all. It also notes the OpenID shared-signals work, finalised in September 2025, which lets one system tell another that a session or account has changed so that access can be cut quickly. You do not need to implement these personally. You do need to ask suppliers whether their integrations follow them, and to keep a register of which app talks to which.

One more caution from the entry: provisioning that happens only at the moment of first login leaves no channel for removal. If a supplier offers that choice, prefer the option that can also take names off the list.

Putting the eight habits into a rhythm

The entry suggests a cadence: daily comparison between the personnel list and the account list, weekly sampling of recoveries, monthly review of machine-account expiries, and a quarterly leaver drill. Training departments already schedule recurrent checks this way. For a simulator-heavy operation, such as the one described when a new IFR training device joined the programme, every booking account and instructor login attached to that equipment belongs in the register from day one. The same is true for the fleet news in the post about an advanced glass-cockpit twin entering the fleet, where avionics data and maintenance tools bring their own service accounts.

For definitions, standards references and the maturity ladder behind these habits, see the IdentityOps reference in the Ops Atlas. Treat it as a map: it is candid that scopes differ, and a careful academy will adapt the list to its own fleet of systems.

© 2024 ADVANCED INTERNATIONAL AVIATION ACADEMY. ALL RIGHTS RESERVED.

STAY CONNECTED WITH US: