Six IdentityOps Myths Flying Club Committees Still Believe

Six IdentityOps Myths Flying Club Committees Still Believe

Light-sport flying clubs run lean. A few volunteers keep the aircraft booked, the membership list current and the website alive, and the technology tends to be whatever worked last season. Somewhere in that setup sit accounts: the booking system, the shared mailbox, the payment link, the cloud folder with insurance paperwork. Advice about looking after those accounts, grouped under the label IdentityOps, is full of folklore. Here are six myths I hear in club committee meetings, with what the evidence says and what to do instead. No jargon walls, just the useful bit.

Myth 1: “Once we disable someone’s login, they are gone”

This one feels obvious, and that is why it survives. A committee member resigns, someone flips a switch on the club email, and everyone moves on. The reality is messier. The Ops Atlas, a catalogue from xOps School, states in its article on IdentityOps practice that a disabled central account is not the same thing as a finished offboarding. Sessions that were open can keep working for a while, and separate records inside each application may remain untouched.

What to do. Make a leaving checklist with one line per tool: booking system, payment portal, shared folder, social page. Sign the person out of everything, then confirm each line. Write the date beside it.

Myth 2: “Everyone has two-step sign-in, so we’re covered”

A club treasurer proudly says that all members of the committee have switched on a second step. Ask which kind. If it is a texted code or a one-tap approval, an attacker may still get through: codes can be intercepted by number-swapping, and tired people approve repeated prompts to make them stop. The Atlas reserves the phrase phishing resistant for hardware-bound methods such as security keys and smart cards, and it calls the claim of full protection based on weaker methods an anti-pattern.

What to do. Give security keys to the two or three people who can move money or change who has access, then extend to the rest as budget allows. Keep a spare key in the clubhouse safe.

Myth 3: “Passwords must be changed every ninety days”

Many of us were taught this. It produces predictable patterns, like Spring2026 turning into Summer2026. The guidance the Atlas relays from the current NIST digital identity revision points the other way: favour long passwords, drop periodic forced changes and complexity rules, and check choices against lists of known bad ones. Length beats tricks.

What to do. Ask members and volunteers for long passphrases and use a password manager. Change a password when there is reason to believe it was exposed, not by the calendar.

Myth 4: “Single sign-on puts all our eggs in one basket, so avoid it”

Clubs sometimes resist a shared login for fear that one stolen password opens everything. It is a fair worry, but the Atlas argues the framing is slightly off. Single sign-on concentrates control rather than risk: you protect one front door properly, and you can lock every room at once when someone leaves. The cost of not having it is a dozen separate passwords, many of them weak or reused, plus no single place to cut off access. The catch is that the central service becomes the most important system you run and needs the strongest protection.

What to do. If your tools support it, use a central sign-in with a hardware key for its administrators. If they do not, at least keep one master list of which tool uses which login.

Myth 5: “A shared account is fine, we all trust each other”

Trust is real, but it is not the point. The front-desk login that four volunteers use cannot tell you who cancelled the maintenance slot on Thursday, and when a volunteer leaves you must change the password for everyone. The Atlas lists shared service accounts among the habits to drop. The same reasoning covers the club’s automation: the link between the booking calendar and the payment page should have a login of its own, with a named owner, rather than borrowing a person’s credentials.

What to do. One person, one login. One automated connection, one machine login with an owner and an end date. For retirement, disable first and delete later.

Myth 6: “If someone is locked out, the quickest fix is a phone call”

Everyone wants to help a member who lost access before a weekend of flying. Yet the call itself is the weak point. The Atlas describes the order it prefers: the member first tries to sort it out alone, using a backup method enrolled earlier; if that fails and a person must step in, a one-time code goes out only when a committee member who knows the requester vouches for them in person or on live video; calling back a number on file is discouraged because numbers can be hijacked; the real owner is notified after the reset. It points to public advisories about a criminal group that repeatedly got resets through help desks by sounding confident and rushed.

What to do. Agree a standard answer such as: for your protection, we confirm identity at the clubhouse or on a video call. Members respect procedures that protect their money.

How the myths play out on one ordinary Saturday

To see why these beliefs persist, walk through a plausible club weekend, invented for illustration. A volunteer who ran the booking page for three years steps down on Friday evening. Nobody mentions the shared inbox or the payment link, because everyone assumes the email switch covers it. On Saturday morning a message arrives from a member claiming to be the new treasurer, asking for an urgent password reset on the payment account because the old one is unreachable. The duty volunteer wants to be helpful and has no script.

Count the myths at work. The old volunteer’s logins are assumed gone because one switch was flipped. The payment account has a shared password. The caller expects a quick phone fix. If the club had followed the six habits above, the Friday checklist would have listed the payment link and the shared inbox, the payment account would have an individual owner, and the duty volunteer could reply with the standard answer: we confirm identity at the clubhouse or over video. Fifteen minutes of preparation changes the entire Saturday. The Atlas notes that attackers do not need clever code when a polite voice and a hurried volunteer will do.

A bonus myth: “Security tools will fix this for us”

Clubs are pitched products all the time. The Atlas offers a sober counterpoint. It cautions against buying a governance product before the membership and staff data is clean, and it observes that in each public incident it cites, the weakness was a process lapse rather than a flaw in the underlying cryptography. Tools help only when the list of who exists is accurate and someone owns each account.

What a tiny club can skip

Not every recommendation fits a club of thirty members. The Atlas itself says that a very small organisation may fold the practice into existing duties instead of creating a separate role, and that expensive governance software can wait until the basic data is trustworthy. So skip the grand programme. Keep the roster, the leaving checklist, the keys for the two people who matter and the lockout script. Those four items cost an evening and a modest purchase, and they close the doors that incident reports keep describing. Everything else can be added as the club grows.

Putting the myths to work

A club can turn this into a one-evening committee agenda:

  1. Write the roster of accounts and name an owner for each.
  2. Draft a leaving checklist with one line per tool.
  3. Order security keys for the treasurer and administrator.
  4. Write the lockout script and pin it in the clubhouse.
  5. Pick a date next quarter to repeat the review.

For committee members who want to understand the technology side more deeply, there are accessible starting points such as a primer on building technology skills through a training school and a corporate-training view of IT infrastructure. Nobody expects a volunteer to turn engineer, yet understanding the vocabulary helps when a supplier talks fast.

Dull routine beats clever products every time, in the hangar and in the booking system alike. Fix the process, keep a log, and the myths lose their grip.