A Sixteen-Point EndpointOps Audit for Charter Operators

A Sixteen-Point EndpointOps Audit for Charter Operators

A charter business runs on small, fast decisions made on handheld screens. A coordinator confirms a tail number on a phone, a crew member opens a trip sheet on a tablet, a concierge checks guest preferences on a laptop in a lounge. Those devices hold itineraries, passport details and sometimes payment information. So when somebody asks who is looking after them, you want an answer better than a shrug. This checklist turns the idea the Ops Atlas calls EndpointOps into a one-afternoon audit you can run yourself.

A quick note on the source. The Atlas page on EndpointOps across the full device life describes the label as informal and as an overlap between managing devices and securing them. It is not a standard, which is good news for a smaller operator: you can adopt the parts that fit and ignore the rest. Nothing here is legal or compliance advice, so check your obligations with a qualified adviser.

Before you start: three ground rules

First, audit with someone who did not set the devices up, because fresh eyes find assumptions. Second, write every answer down, even the awkward ones. Third, agree in advance that the goal is a to-do list and not a blame list. Charter work already has plenty of pressure, and an audit that feels like an exam will not be repeated.

Section A: The device roll call

  1. List every phone, tablet and laptop that opens trip, guest or payment information. Include personal phones used by crew.
  2. For each, note the owner, the person who uses it and where it normally lives.
  3. Compare that list with whatever your management tool shows and whatever your security tool shows. The Atlas calls this three-source reconciliation, and it expects the three lists to disagree.
  4. Mark any device that appears in only one list. Those are your first investigations.

If you handle high-end guests, you will recognise the logic from service quality. Our thoughts on the preferences premium travellers expect from a provider begin with knowing exactly who and what is involved in each trip.

Section B: Is the basic set-up sound?

  1. Check that each company-owned device is enrolled in a management tool and has reported in recently. The Atlas uses a thirty-day look-back for this.
  2. Confirm the disk is encrypted and that the recovery key is stored somewhere other than the device.
  3. Look for the tenant option that lets unpolicied devices pass checks automatically. Where your platform ships that way, flip it.
  4. Check that the security sensor on each laptop has reported within the last seven days.
  5. Confirm that every device runs a version of its operating system that still receives updates. Mainstream Windows 10 support lapsed in October 2025, and recent macOS setup flows enable disk encryption by default, so an ageing mixed fleet deserves a second look.

Section C: Who can do what?

  1. Identify who has top-level administrator rights and whether they use that account for daily work. The Atlas names that habit as an anti-pattern.
  2. List which roles can read stored recovery keys. The Atlas says seven built-in roles in one identity platform can, so check yours.
  3. Find out whether a second person must approve a wipe, retirement or bulk script. If not, decide whether you want that safeguard.
  4. Check that phishing-resistant sign-in is used for anyone with administrative power.

Section D: What happens at the end?

  1. Write down, for each kind of device, whether it will be retired (company data removed) or wiped (everything erased).
  2. Check where lost devices are reported and who decides on a wipe at midnight.
  3. Confirm how storage is cleaned before a device is sold, recycled or handed to a new owner. The Atlas points to a 2025 US government guide on media sanitisation as its reference.

What a first audit usually turns up

Expect a few surprises, and treat them as normal rather than embarrassing. The most common is a device nobody remembers: a spare tablet in a drawer at the lounge, still signed in to a booking tool. The next is a recovery key that was never stored, discovered only when someone checks. A third is a shared login used by several crew, so nobody can later trace which person made a given change. None of these needs special software to fix. They need a decision, a name next to the task and a date.

One more tip: photograph or note the screen when a check fails, so that the person fixing it sees exactly what you saw. Charter teams already live by clear handovers, and the same discipline makes audit findings easy to act on.

Scoring the audit

Give yourself one point per item you can answer with evidence, not memory. Sixteen is rare on a first pass. Anything under eight means the fundamentals need attention first. Do not stress over the score; track it. When you repeat the audit in a quarter, the number is simply a trend line. Our notes on why private airport transfers feel seamless to guests are about the same principle, the ride feels effortless because the preparation behind it is thorough.

A 30-60-90 follow-up

The Atlas offers a simple shape for turning findings into progress, and it fits a small operator well.

  • First thirty days: run the reconciliation, write a one-page standard for devices and fix risky defaults.
  • By sixty days: back-fill missing recovery keys until more than 95 percent of encrypted devices have one, pilot stricter rules on a few machines and protect work apps on personal phones.
  • By ninety days: roll out the rules broadly, create a locked-down approver group for risky actions and time a first key-retrieval drill.

Keep the finished audit in a shared folder, date it and put the next review on the calendar. The first run feels like paperwork. By the third, the original question will take you a couple of minutes to answer.