A Charter Desk’s Week of ThreatOps: A Fictional Team Story

A Charter Desk’s Week of ThreatOps: A Fictional Team Story

Picture a small charter-booking desk with five people, a quote engine and a partner portal where operators upload their empty-leg availability. Nothing about it is real; the details below are invented to show how ThreatOps habits play out in a team that sells seats and aircraft time rather than software. The sequence of events follows the practices described in the Ops Atlas, and the numbers quoted at the end come straight from its published examples.

Monday: the question that fits on a card

The desk’s operations lead starts the quarter by refusing to subscribe to anything new. Instead she asks the team to write three questions about outside threats that someone could act on. They settle on: are criminals targeting aviation booking portals with stolen partner credentials, which remote-access weaknesses are being used, and what would we need to see in our logs to notice it?

That structure mirrors what the Atlas calls a priority intelligence requirement, one question, one fact needed, one decision. It keeps the list short on purpose; the entry suggests five to eight at most. The team pins the cards above the whiteboard where they price quotes, the same place they keep reminders from a piece on what moves private jet charter prices, because both lists exist to stop guesswork.

Tuesday: a feed, a block and a complaint

The desk already receives one free feed. Its address list is wired into the web firewall for convenience. On Tuesday morning an operator partner phones to say the portal rejects their upload page. Within minutes the team traces it: the feed had flagged an address in a shared content-delivery pool, and the partner’s own systems sit behind that very pool.

The lead follows a simple runbook. The block is reversed at once, since the Atlas allows whoever is on call to undo one. The feed is moved to alert-only status within the hour, and a line is added to a monthly count of blocks reverted. It stings, but it produces a rule: automatic blocking requires a source graded in the top reliability tiers, a credible claim, a track record of 0.9 precision or better over three months, and no appearance on the allowlist. The feed fails the precision test by a wide margin.

Wednesday: grading what comes in

With the feed demoted, the team builds a tiny source register. Every source is scored twice: a letter describing its track record, and a digit describing how far one specific claim can be believed. In the Atlas’s illustration, a first-ever report from a trusted provider lands at A3, strong source, unconfirmed claim. The desk adds a column for expiry. Network addresses expire after two weeks, because the Atlas’s sample policy treats them as short-lived, while the fingerprints of known malicious files last a year.

The register is just a spreadsheet in a version-controlled folder, which the Atlas says is a respectable beginning for a small team before any dedicated platform is considered.

Thursday: a hunt that finds nothing

Using the second question, one analyst proposes a hypothesis: a stolen partner account might sign in from a country the partner never works in, then enrol an extra handset for approval prompts. The pattern echoes a real case the Atlas retells, where a breach at a security vendor surfaced because an employee’s account had enrolled a second phone without the employee doing it.

The analyst confirms the logs go back 120 days, runs the search, and finds two matches, both explained by a partner’s sales trip. No intrusion. In many teams this feels like wasted effort. The Atlas disagrees: when the data is good enough, a null result is a confident negative and counts as success. The analyst writes a note saying the behaviour would have been visible, and files a small request for an alert on the pattern. That request is the hand-off the Atlas describes between hunting and detection engineering.

Friday: sharing, with limits

An industry mailing group asks whether anyone has seen credential-stuffing aimed at charter portals. The lead’s instinct is to say nothing; a colleague points out the Atlas rejects “sharing is risky, so share nothing”. Colour-coded labels indicate how far a note may travel, and a pre-approved category of information makes it routine. The generic pattern goes out, with no customer details, and every label is checked before anything the group sends back is forwarded. The Atlas lists passing an amber-labelled item beyond its intended clients as a classic error, so one such note stays inside the desk.

Later the lead explains the decision to a new hire using plain commercial language. A quote for a one-way empty leg is only valid for a short window, as described in an explanation of how empty-leg flights operate, and intelligence has the same shelf life.

The quarter in numbers

At quarter end the team prints a one-page review. They do not report how many addresses they loaded or how many hunts they started; the Atlas calls those vanity measures. They report ratios instead. The entry’s worked example is a useful template: 5 of 6 priority questions answered (83 percent), 14 of 40 intelligence items leading to action (35 percent), 5 of 12 hunts producing a concrete output (42 percent), and a feed whose 120 alerts included only 18 genuine ones. That last figure, 15 percent, keeps it in alert-only mode and puts its renewal in doubt.

The desk’s own figures differ, but the format lets a manager see where effort pays and where it does not. Anyone who wants to read the underlying definitions can find them in the full ThreatOps entry in the Ops Atlas.

What the story shows

  • Questions come before sources. A card on the wall did more than a new subscription.
  • Measured trust beats assumed trust, so blocking was earned, not granted.
  • An empty result is still a result when the logs were sound.
  • Sharing rules agreed in advance remove the argument at the moment of pressure.

None of it required a large budget. It required an owner, a short list, honest grading and a habit of writing things down, which a charter desk used to quoting tight turnarounds already understands. Readers who price trips with the help of a beginner’s walk through charter costs will recognise the same instinct: know what you are paying for and check it against reality.