A parent asked our chief instructor a question last month that she could not dodge: “Your planes I understand. But what is this SecOps thing your IT people keep talking about, and why should I care?” Asha has taught nervous students for fourteen years, and her trick is always the same — explain the unfamiliar using only things you can see at an airfield. She sat the parent down in the briefing room and walked her through it in five short lessons. What follows is essentially her whiteboard, cleaned up. The definition she teaches comes from the Ops Atlas, which uses SecOps to mean a working contract between security and operations — baselines, one owned fix-it queue with dates, exceptions with expiry, and numbers both sides answer for. Everything else on her whiteboard hangs off that one sentence.
Lesson one: one schedule board, one truth
Every flying school lives or dies by its scheduling board. Two boards, and the school has two aircraft booked for the same slot and two instructors standing on the apron with no aeroplane. Asha’s first lesson: the security world’s version of the board is the remediation queue, and the contract insists there is exactly one of them. Every finding — a weak setting, a missing patch, a misconfigured door — lands on that single board, with a name beside it and a date underneath. Not a mailing list. Not a spreadsheet in somebody’s downloads folder. A name, and a date. The parent nodded at this point; she runs a bakery and recognised her own order book immediately.
Lesson two: new SecOps rules fly with an instructor first
You do not hand a brand-new student a new radio procedure and a solo slot on the same day. You demonstrate it, you ride along, you let the student try it while you listen, and only when the pattern is clean does it become the rule. Hardened computer settings travel the same road, and the configuration-management literature the Atlas traces this work to — SP 800-128 for the lifecycle, SP 800-70 for the checklists themselves, SP 800-40 Rev. 4 for patching — describes exactly that sequence. Pick the standard, adjust it to your fleet, test it somewhere that cannot hurt anyone, run it silently so it only logs what it would do, then switch it on for real, one group of machines at a time. The silent phase has a name, log-only mode, and its flying equivalent is the instructor’s headset: nothing is blocked yet, everything is being recorded for the debrief.
Lesson three: the pilot owes the tower a clear read-back
This was the lesson the parent did not expect, because it runs in the direction people never guess. The watching team — the security operations centre, the folks watching screens — is the tower. But the tower cannot help an aircraft that never transmits. So the contract spells out what the flying side owes the tower, and CIS Control 8 numbers those duties: at the basic level, a logging process, actual audit logs, and storage to keep them (controls 8.1 through 8.3); at the stricter level, synchronised clocks (8.4), logs flowing to one central place (8.9), retention of at least ninety days (8.10), and someone actually reading the logs weekly (8.11). Two more clauses make it work like real airspace: a shared calendar, so security changes get slots like any other traffic, and a pre-agreed containment authority, so nobody debates on the frequency while something is on fire.
Lesson four: respect the simulator instructor’s keys
Asha’s fourth lesson was about power. The school’s simulators can teach anything, including terrible habits; the instructor’s console can pause, reset, or fail every system in the aircraft. Security tooling holds the same kind of keys. Scanners, agents running as root or SYSTEM, and automation tokens deserve the treatment normally reserved for the most privileged accounts on the estate — because that is exactly what they are. Her sharpest sentence: edit rights on the routing rules amount to a find-eraser, since a rule change can slide a finding out of sight with nothing left in the log. A queue that can be quietly edited is not a queue; it is a suggestion. The parent, who once caught a staff member editing her bakery’s waste log, understood this one fastest of all.
Lesson five: storms get their own SecOps procedure
Normal work follows the board; weather does not. The contract keeps a separate lane for genuine emergencies, and the reference points are public. NIST’s emergency path expects fixes on an aggressively compressed timetable — no pretending a two-month window applies when a flaw is being exploited this afternoon. CISA’s BOD 26-04, issued in June 2026, gives federal civilian agencies concrete clocks: three days for the worst combinations of exploited flaws and internet exposure, then fourteen or sixty days depending on severity. Private organisations are not bound by it, but the scale is now the one everyone quotes. And one modern wrinkle deserves its own mention: where machines are rebuilt from images or run as containers, you hand the item to whoever maintains the image, and only a clean scan of a fresh build — every stale instance retired — counts as done. SP 800-190 wrote that container rule down long ago. Fixing the running container is like repainting a rental aeroplane; the paint stays behind on the next swap.
What the parent carried out of the briefing room
Asha’s summary fit on a sticky note, and the parent reportedly still has it on the bakery office wall. It works off the airfield too:
- One queue, every item with a name and a date.
- New rules log first, block later, and roll out in small groups.
- The flyers owe the watchers clean, central, retained logs.
- Tooling privileges are guarded like master keys.
- Storms have their own lane, with public clocks to steer by.
The fuller definition she pointed her to lives at the Atlas’s page on SecOps as a working contract — five minutes of reading, no jargon. And if you are weighing where your own training hours go, the school’s broader philosophy shows up in the recognition AIA Academy earned from AOPA, in the instrument-time students log on the FRASCA 142 simulator, and in the upset-recovery skills built on the ALSIM AL200 simulator. Procedures first, judgment second, tools third — in cockpits and everywhere else.