Six ThreatOps Myths That Pilot Training Schools Believe

Six ThreatOps Myths That Pilot Training Schools Believe

Aviation has a long record of unlearning comfortable beliefs. “Gear-down checks are for students” and “the autopilot will catch it” were once casual remarks, and both lived on until a bulletin proved them costly. Folklore also gathers around the security side of training organisations, and a surprising share of it concerns ThreatOps: the combined practice of gathering intelligence about adversaries and hunting for what automated alarms missed. Six persistent myths follow, each checked against what the Ops Atlas says, and each translated into the world of a pilot-training operation that stores identity documents, medical-certificate scans and payment records.

Myth 1: more feeds mean more protection

It feels intuitive. If one weather source helps, ten must help more. But a cockpit with ten contradictory forecasts and no way to rank them is worse off than one with a single trusted briefing. The Atlas names “more feeds, more protection” as an anti-pattern and ties value to something measurable: how many of a feed’s flags turned out to be real. In its worked quarter, a feed raised 120 flags, only 18 held up, and the verdict was to leave it as a warning source and weigh cancelling it.

Consider a booking desk that signs up for yet another stream of warnings because a colleague raved about it. Within a month the inbox is full, the duty manager skims nothing, and the one message that mattered is buried under dozens that did not. More inputs without a way to weigh them simply move the bottleneck from collection to attention.

What to do instead: ask each subscription to earn its place with evidence. Track hits that proved real, drop the rest, and treat a cancellation as a successful decision rather than an admission of failure.

Myth 2: automatic blocking is the whole point

Pilots distrust any automation they cannot override. The same instinct applies to network rules fed by outside lists. The Atlas cites guidance from FIRST suggesting that such lists exist mainly for flagging and alerting, not for unattended blocking, and notes that early-stage programmes should simply raise alarms. Blocking needs proof of accuracy first and a human fast enough to reverse a mistake.

The Atlas describes a scenario where a list caused a shared delivery network to be cut off, taking legitimate traffic with it. Imagine a school’s student portal losing access to a document-signing service in the middle of enrolment week. A runbook that lets any on-call person undo the rule, with a review by the programme owner shortly afterwards, keeps such a slip to minutes.

What to do instead: start every new list in warning mode, set written conditions for promoting it to blocking, and log how many blocks you later reversed.

Myth 3: a hunt that finds nothing was a waste

An instructor who inspects a control cable and finds it sound has not wasted the afternoon. The Atlas insists a hunt without a catch is not a failure when the team can say, with confidence, that the relevant evidence would have appeared had the behaviour occurred. That statement of “we would have seen it” is a real result. If the logs did not cover the area, the result is different but equally useful: a ticket for the missing coverage.

The same entry defines the outcome rule firmly. Every hunt closes with something filed: a request for a new alarm, a coverage ticket, an escalation, or the confident-negative note. A person who was not involved should be able to rerun the work from the write-up.

Think of the quiet satisfaction of a fully documented, uneventful annual inspection. Nobody throws a party, yet the aircraft flies on the strength of those records. A hunting log full of tidy negatives plays the same role for an organisation’s confidence, and over a year it also shows where visibility is thin.

What to do instead: judge the hunting programme by what it files, not by how many intrusions it uncovers. Zero findings can sit alongside a healthy programme.

Myth 4: a coverage heat map shows how safe you are

Colouring in a chart is satisfying. A wall display showing which attacker behaviours your tools claim to notice looks like progress, much as a fully green maintenance dashboard does. The Atlas takes a firm line: the ATT&CK knowledge base catalogues behaviours, its tactics are not a fixed sequence an attacker follows, and a hunting framework it cites cautions that plenty of catalogue entries were never intended as live alarm rules. A filled map measures documentation effort, not protection.

There is a practical wrinkle too. The Atlas records that the October 2026 release of the catalogue added new tactic labels, which breaks older mapping spreadsheets. A team that treats colours as the goal will spend its quarter relabelling.

A cadet who memorises every page of the manual still has to demonstrate a short-field landing. The same gap separates a colourful chart from a rehearsed capability. Only exercises show whether the claimed coverage holds up when something real is attempted.

What to do instead: pick the handful of behaviours that matter to your situation, such as misuse of valid logins, and confirm through a hunt that you could notice them. Depth on a few beats width on all.

Myth 5: knowing the group tells you what happens next

Aviation accident reports name causes, not culprits, for good reason. Security has a habit the Atlas calls attribution theatre: spending days naming the adversary while the actual exposure goes unfixed. The Atlas includes a small lab exercise comparing three well-known groups from the ATT&CK catalogue. Together they used 92 distinct techniques, yet only two were common to all three: abuse of valid accounts and use of externally reachable remote services. The overlap is thin. Knowing a group is active does not forecast the specific technique that will be aimed at you.

The two shared items, though, are worth acting on whoever is behind an attempt. A school that protects logins with a second factor and limits remote access addresses both without ever needing to know a name.

What to do instead: prioritise the behaviours that recur across many groups, and keep attribution as background rather than a deliverable.

Myth 6: sharing intelligence is too risky, so share nothing

Safety culture in aviation depends on reporting near-misses openly, often under protections that keep the reporter safe. Information about security incidents deserves similar courage. The Atlas answers the fear with structure: the Traffic Light Protocol marks how far each item may travel, groups can pre-approve categories of material, and and Europe’s NIS2 directive carries an article that encourages organisations to swap information on a voluntary basis. The risk is real but manageable, and silence carries a price because other training organisations then meet the same trick unprepared.

The opposite mistake exists as well. The Atlas lists forwarding amber-marked material beyond its permitted audience as a named error. Sharing works because the rules are followed, not because anything is allowed.

What to do instead: join an information-sharing community early, agree in advance which kinds of facts may be passed on, and respect the colour on every item.

A closing thought on habits

Notice that all six myths share a root: they replace a decision with a count, a colour or a subscription. The Atlas pushes the other way, toward a short list of written questions, each with one fact and one decision attached, reviewed every quarter. A flight school that keeps that discipline gains the same thing a good safety-management system provides, which is evidence rather than reassurance.

If you want the underlying detail, including the maturity ladder and the sample thirty-sixty-ninety plan, read the Ops Atlas page that sets out the ThreatOps discipline. It is long, but the sections on anti-patterns and myths repay a careful read.

Readers who run the business side of a training operation may also like our note on plugging small money leaks before they drain a budget, a different domain with a similar attitude of measuring before acting. And for something gentler, a sightseeing guide to the Pink City makes a decent break after the technical reading.

Treat every belief in this list as a checklist item you can test. Where the evidence disagrees with the folklore, update the folklore, just as the industry has always done with its checklists.