A listings desk or small travel agency in a city like Bengaluru has the same quiet exposure as any office: a few laptops, a shared tablet at the ticket counter, and a drawer of phones used for confirmations and vendor chats. When a show is sold out and a coordinator’s laptop dies on the way to a venue, nobody wonders about policy; they wonder where the ticket list went. An audit before that moment is cheap. This checklist borrows its structure from EndpointOps, the informal label the Ops Atlas uses for looking after devices from enrolment to retirement, and keeps the focus on evidence instead of opinion.
Why audit by evidence
The Atlas makes a point that suits anyone who has ever trusted a single spreadsheet. A management dashboard in its worked example claimed about 89 percent of devices were compliant, eight of nine. After checking the console against two other inventories, only just four out of ten passed every single test together, including a healthy security agent, which is forty percent. Different sources disagreed because each one counts something different. So the first rule of this audit is simple: every number needs a second witness.
The checklist
A. Inventory (30 minutes)
- List every device used for work, owned by the business or by staff.
- Mark each as company-owned or personal, and note who holds it today.
- Record the operating system. Mainstream Windows 10 support finished in mid-October 2025 according to the Atlas, so any machine still running it carries both a risk question and a paid-extension question.
- Note which ones have not been switched on for a month.
B. Coverage (20 minutes)
- Count devices the management tool has seen in the last thirty days. Intune devices normally check in about every eight hours, so a month of silence is a real signal.
- Count devices with the security sensor reporting. Defender treats seven days of silence as inactive.
- Compare the two counts and list devices present in one but absent from the other.
C. Protection (30 minutes)
- Check whether disk encryption is on for each laptop.
- Confirm each encrypted laptop has a stored recovery key, and note the ratio. The Atlas example of 1,131 stored keys for 1,164 encrypted devices lands at 94.3 percent and still flags the shortfall.
- Ask for one live retrieval of a key, timed.
- Look at the tenant default for devices with no compliance policy; if it says compliant, change it.
D. Administration (20 minutes)
- Count how many people hold top-level admin rights, and which of them use it for everyday work.
- Check whether a wipe needs a second approver.
- Find who can read recovery keys. The Atlas counts seven built-in directory roles with that ability.
Reading the results
Do not expect clean numbers. A first audit at a small business usually surfaces a handful of stray devices, a lower-than-expected key count and at least one over-powered account. Write the three worst gaps at the top of the page, assign an owner and a date for each, and rerun the relevant section in a month. The Atlas suggests a rhythm of thirty, sixty and ninety days: reconcile and write the device standard first, push coverage and encryption keys past the mid-nineties next, then enforce broadly and drill a key retrieval.
Skills worth building along the way
For readers eyeing technology careers in the city, this is a useful practical entry point. Roles that blend support, security and administration involve exactly this work: knowing what is enrolled, what is encrypted and what has quietly gone missing. The Atlas is careful to say the word itself is no recognised job title, so a vacancy board will not list it. Search for device management, endpoint security or IT support titles instead, and treat the audit above as something you can show an interviewer.
A worked pass through one small desk
Imagine a five-person desk handling event listings and ticket partnerships. Section A turns up eleven devices, including two phones nobody remembered. Section B shows the console has heard from nine of them and the security sensor from seven, which already tells the manager that two laptops are half-covered. Section C reveals that every laptop is encrypted but only six have keys on file, so the owner schedules an afternoon to backfill escrow before any other task. Section D shows three people hold top-level rights although only one needs them. Within a week the desk has a shorter admin list, a full key set and a clear picture. Nothing exotic was bought; the work was counting and then closing gaps.
Two traps the audit often finds
First, a laptop that was encrypted recently may keep failing a BitLocker check until it restarts, because the measurement happens at boot. A restart usually clears it. Second, a tidy-up of old device records can wipe out access to keys. The Atlas says deleting the management object of an Entra-joined device can suspend BitLocker, so confirm key status first.
Source and further reading
The framework above follows the Ops Atlas description of EndpointOps, which also includes scope notes, a maturity ladder and a list of standards for teams who want to go deeper.
For the other half of running a city listings desk, your audience matters as much as your hardware. If you are building a calendar of shows, our guide to theatre experiences available around Bengaluru and the roundup of live music events visitors can attend are useful starting points, and both are exactly the kind of content that sits on the laptops this checklist is protecting.
One-page summary to pin up
Inventory first, coverage second, protection third, administration last. Count twice, trust nothing that has a single source, and test the key before you need it.