Every charter desk has a story about the call that came after the trip. A client remembers a fuel stop that was not on the quote, a catering swap, a change of aircraft. Somebody has to reconstruct what happened, and the quality of the paperwork decides whether that takes ten minutes or a bad week. The same dynamic plays out in digital operations, where the paperwork is a trail of logs, and a young discipline called SecDataOps is about keeping that trail honest. Six common myths stand in the way.
The facts below come from the Ops Atlas, and you can read the original in the Atlas page that describes SecDataOps. I have translated them into the world of private aviation, where a record that cannot be trusted is worse than none.
Myth 1: SecDataOps is just marketing for something old
There is a grain of truth, and it is worth admitting. The Atlas itself describes the label as young, pushed largely by software suppliers, and not defined by any standards body. Public use goes back to at least early 2023, and a handful of companies promote their own versions of it.
But the underlying work, collecting and storing event records so investigators and auditors can rely on them, appears in official publications under older headings such as log management and event logging. An American federal memo from 2021 set out tiers for it, and later official guidance followed. So the name may be fashionable while the craft is established. Think of how a charter desk might rebrand its trip-sheet routine: the label changes, the need for a signed, dated trip sheet does not.
Myth 2: collect everything and sort it out later
It sounds like the safe choice, the digital version of keeping every napkin from every client dinner. The Atlas pushes back, quoting Australian-led guidance that over-collection makes effective detection rules harder to write. When the useful lines are lost among a mountain of noise, analysts burn hours digging and budgets burn too.
A better habit is to decide what each source is for. A client record on a long trip might need to be retrievable within hours, while a routine ping from a monitoring tool can sit in cheap storage and be summarised. The Atlas illustration compares 400 GB a day kept entirely in premium storage with 8 GB a day of summaries and raw data parked in a cheap lake for 400 days, and the second layout costs well under half as much while keeping raw records more than four times longer.
Myth 3: ninety days is the industry standard
Ninety days feels respectable because it is a default in many products. Yet defaults are chosen for storage convenience, not for how problems actually unfold. The Atlas cites a 2026 report on the previous year’s investigations: a worldwide median of 14 days, but 122 days in espionage-type cases, with one long-running implant staying roughly 400 days. The report itself argues that standard three-month retention leaves organisations unable to see how an intrusion began.
Charter people understand this instinctively. A dispute about a booking can arrive many months later, after a card chargeback or an insurance query, and nobody accepts that the manifest was deleted after one quarter. Regulators are specific in their own ways: one federal memo asks for 12 months of readily searchable records plus 18 months of cold storage, India’s 2022 directions name 180 days, and Australian guidance proposes a one-year starting point for administrator and security logs.
Myth 4: our security software vendor takes care of the logs
The Atlas puts this plainly: SIEM products only search whatever reaches them. Nothing in the licence guarantees that every record made it, that it was parsed correctly, nor that the licence covers long-term storage. Assuming otherwise is like assuming your charter broker also tracks every ground transfer in the itinerary. The broker books what you asked for. If a limousine company is not in the loop, there is no record of it.
In practice that means someone inside your company must own the pipeline from each source to each store. For luxury travel, where one client may use a private car, a jet and a villa in a single weekend, the same principle applies to records: the airport-transfer side of the journey is a separate chain with its own evidence, and a gap there is still a gap in the story.
Myth 5: once data is tidied, the original can go
It is tempting to keep only the neat, standardised version. The Atlas warns that parsers contain errors and that open schemas deprecate attributes from one release to the next. If the neat copy is wrong, the original is the only route back. Its advice is to keep raw records in the cheapest tier and convert onward from them.
A trip-sheet analogy helps. Imagine a charter manager types the handwritten log into a spreadsheet and burns the paper. One mistyped time and the evidence of a delayed departure changes quietly. Keep the paper, even if it sits in a box in the cupboard.
The Atlas adds a cautionary detail about strict conversion tools. In one popular collector, a missing value converted to an integer becomes zero, so garbage can show up as a believable event. The cure is to send lines that fail an exact pattern to a quarantine area rather than forcing them through.
Myth 6: one schema will suit everybody
A tidy standard sounds ideal, and open options exist. Version 1.9.0 of an open security schema arrived in August 2026 under the Linux Foundation, and several vendors maintain their own models. But the Atlas cautions against forcing one shape on every consumer. A hunting analyst wants rich detail, an auditor wants stable fields and a finance team wants a cost summary. Different readers, different views, one preserved raw record underneath.
It is the difference between the manifest a pilot needs, the invoice a client needs and the safety summary an insurer wants. All three come from the same underlying trip, shaped for their reader.
What good looks like, in a charter company’s clothes
The Atlas sketches a maturity ladder: Reactive, Inventoried, Contracted, Measured, Optimising. A charter operator at the Reactive stage finds records only when something goes wrong. At Inventoried, a list exists of every system that holds trip data and who owns it. At Contracted, each system has a one-page promise about format, freshness and retention. At Measured, a monitor notices when a feed goes quiet, ideally paging someone after fifteen minutes of silence. At Optimising, tiering and costs are tuned with replay checks.
The first month of the Atlas plan asks only for a register, scores for each source, a retention policy and health monitors on the ten most important. That is achievable for a small team. If your guests value discretion, as discussed in our piece on what luxury travellers expect from a provider, trustworthy records are part of delivering it.
One more story to close
The Atlas recounts a plain runbook episode. A system upgrade reset name-lookup logging on two hosts, and refreshed certificates broke log forwarding on two more. Both changes slipped past the formal review board, so nobody linked them to the missing records until an investigation needed them. A charter manager would call that a ground-handling change nobody told dispatch about.
The fix was not clever. Every upgrade on a system in the top-ten list now ends with a check that logging still works, and once a month the team stops a test source on purpose to see who notices. Boring, regular and effective, which is about the best thing you can say about any record-keeping routine.
Takeaway
Six myths, one idea: evidence has to be planned before it is needed. Keep the original, choose retention by how long problems hide, name an owner for each feed, and test the alarm. Treat this as general reading rather than guidance for a particular company, and use it to open a conversation with whoever looks after your systems.

