A property business that deals in hangars, airpark homes and aviation-linked estates lives on email and shared documents. Viewing schedules, tenant details, offer letters and client identity papers all move through a handful of accounts. That makes a particular failure painfully common: something is wrong with the mailbox, the whole team discusses it in the same mailbox, and the problem gets worse. This piece diagnoses that failure and a few cousins of it, using the ResponseOps framing from the Ops Atlas. Read it as background on operations; it offers no legal, financial or security counsel.
The Atlas, run by xOps School, sets out, in its ResponseOps entry, an approach where handling hostile intrusions is a permanent function of the business. The site concedes that the word is a house coinage that no standard recognises, which is why supplier contracts should say incident response.
Problem 1: the team is coordinating over the compromised channel
Symptom. A manager notices odd forwarding rules in a shared inbox. The team sends round messages such as “check your settings” and “who clicked that link?” over the same system.
Diagnosis. The Atlas files this under what to avoid: holding response conversations on email or chat that may already be compromised. Anyone reading along learns what you know and what you plan, and can adjust, delete evidence or speed up.
Fix. Set up a bridge in advance that does not depend on the main systems. A phone number for a conference line, a separate messaging group on personal devices or a paper call list in the office all work. The Atlas puts an out-of-band bridge in its first thirty-day tasks, with a named lead and a one-page plan.
Problem 2: the cleanup destroyed the story
Symptom. After a suspicious login, the IT contractor resets passwords, deletes the odd rules and reports success. Two weeks later a client says they received a request that looked like it came from you.
Diagnosis. Nobody preserved evidence or scoped the incident. The Atlas calls the wipe-and-start-over habit a myth, since it deletes the clues and closes one entry point while the person responsible remains free. Without logs and copies you cannot say what was read or sent, which complicates every later conversation with clients, insurers and authorities.
Fix. Collect first and clean second, in that order. Save mailbox audit logs and relevant system records as copies, record a hash of each at the time of collection, keep a note of who handled them with UTC times, and store originals on write-once media. For devices, the long-standing RFC 3227 order says to capture memory before disk. You can arrange for your contractor to follow a one-page version of this before the next scare.
Problem 3: nobody decided when “we knew”
Symptom. A client’s personal documents may have been exposed. Staff debate for days whether it was really a breach. By the time the owner says yes, a reporting window may have shrunk or closed.
Diagnosis. Many reporting clocks start at awareness, and the Atlas adds that European regulators read it as being reasonably certain, which is a lower bar than proof. Its table, current to October 2026, spans windows from six hours to sixty days depending on the rule. Which ones apply to your firm depends on where your clients live and what you hold, and that is a question for counsel. The point the Atlas hammers is organisational: a missed deadline is often just a missing owner.
Fix. Appoint one person to decide awareness, with a deputy, and record the decision time. Work through the reporting map with a lawyer in advance. The Atlas notes that legal advice itself sits outside the discipline.
Good client handling is a selling point in this trade, and the same service mindset shows up in the post on personalised service for luxury property clients. A calm, honest incident response is part of that experience, not a break from it.
Problem 4: the fix was only half done
Symptom. The firm isolates a laptop and thinks the matter is closed. Next month, the same account shows activity from a new location.
Diagnosis. Containment was not verified, and eviction was not complete. The Atlas gives examples where steps look effective but are not: short-lived cloud credentials stay valid until they expire, security group changes in one major cloud leave tracked sessions open, and disabling an account in a directory service takes roughly fifteen minutes to an hour to reach all clients. It also relays agency guidance to list every lasting way in before the cleansing begins.
Fix. Treat each action as something to test. After you disable an account, try to use it. After you isolate a device, confirm it is cut off. When you finally evict, do it for every identified route at once.
Problem 5: restoring brought the trouble back
Symptom. Files were encrypted, the firm restored from last night’s copy and within a day they were locked again.
Diagnosis. Two classic patterns are at work. The Atlas lists restoring hosts from compromised backups as an anti-pattern that leads to re-encryption. And if client data was copied out before the lock-up, restoring files does not reverse that; the Atlas calls out the notion that having backups turns an attack into a plain restore as a myth for exactly that reason.
Fix. Establish the date of earliest compromise, choose a backup from before it, and confirm the restored systems are clean before reconnecting them. Decisions about payment demands belong with senior leaders and counsel; the Atlas only reports that a US sanctions office strongly discourages paying.
A word on handoffs and vendors
Property firms lean on outside help: a managed IT provider, a website agency, a cloud host. Before trouble starts, ask each of them three plain questions. Who do I call, and at what hours? What will you collect before you change anything? Who tells whom if client data is involved? Write the answers on the same one-page plan, because in a tense hour nobody wants to hunt through old contracts for a phone number.
A sanity check on the numbers
To know whether things are improving, the Atlas favours three clocks per event, namely how long the intruder lingered, how quickly you called it an incident and how quickly you contained it, plus three quarterly figures covering intruders returning, deadlines met and whether stored evidence is still intact. It also warns that counting incidents measures workload, not how good your response was. For a small firm, a spreadsheet with six columns is enough.
A starter plan that fits a small firm
Month one: lead, sponsor, one-page plan, separate channel, emergency admin logins. Month two: short scripts for ransomware, a hijacked account and a leaked key, plus an evidence folder and the reporting map. Month three: a seated rehearsal with the owners, fixes for the biggest gaps and a handoff to whoever runs overall incident command. For another example of how the firm presents complicated choices clearly, see the article on how complex property decisions are made simpler.
Nothing above needs special equipment. It is a short list of habits, practised until they are boring, and the habit that costs least is writing down the time you first became suspicious.

