A Back-Office Team’s Tuesday: ResponseOps in an Invented Story

Healthcare IT

The story below is invented. It involves a small administrative team behind an online consultation service, and it is meant to show how the discipline the Ops Atlas calls ResponseOps plays out when a digital incident lands on ordinary people with ordinary jobs. Nothing here concerns clinical care or any real organisation; the focus is the back office, where appointment lists, document uploads and staff logins live. Think of it as a rehearsal on paper.

Tuesday, 7:40: A mailbox that behaves oddly

The scheduling coordinator, an early starter, notices that the shared inbox has messages marked as read that she did not open, and an automatic forwarding rule she has never seen. She does not investigate on her own. The team has a laminated card by the monitor that says: tell the lead first. She phones the operations lead, who says the sentence the card suggests, “I am declaring a possible security incident”, and writes the time in UTC at the top of a fresh page.

That small ritual follows the first practice in the Atlas: declare. Without a declaration, no clock formally starts, nobody is clearly in charge and the team slides into private theories. With it, three roles are claimed within minutes: a lead, a technical contact from the IT supplier, and a note-taker.

8:15: The temptation to wipe

The IT supplier proposes reinstalling the coordinator’s laptop immediately. It seems tidy. The lead hesitates, recalling a drill where the facilitator pointed out that wiping removes both the evidence and one foothold, yet leaves the person behind the intrusion free to try again. The Atlas lists this as a myth worth dropping.

The compromise is a short pause. The technical contact captures a snapshot of memory first, then an image of the disk, because an internet RFC the Atlas cites asks collectors to secure the fastest-vanishing data first. Each capture gets a hash, a UTC time and a name on the custody sheet. The originals go to storage that cannot be overwritten; all analysis happens on copies.

While the technical contact works, the note-taker keeps the log readable. Each line has a UTC time, an initial for who acted, what was done and why. When the lead later needs to brief the owner, she reads the log aloud; when the adviser asks for a sequence, it is there. This unglamorous record is what the Atlas means when it lists chain of custody and timestamps among the core skills.

9:30: How far has it gone?

Scoping begins. The forwarding rule is the visible symptom, but the team asks what else the same account could reach: the shared drive of uploaded documents, the appointment calendar, a billing portal. They keep two lists, one for confirmed findings and one for suspicions. By late morning the confirmed list holds four systems, where the initial guess had been one. The Atlas gives a similar example in which a problem first estimated at six systems proved to cover fifteen, and it uses the growth ratio as a measure of how reliable early guesses are.

Nobody on the team is a forensic expert, and nobody pretends to be. The retainer the company signed last year with an outside firm means the technical contact can call a specialist who already knows the layout. That arrangement matches one of the Atlas’s staffing options, in which a small internal lead is paired with an external retainer.

11:00: Containment with a stopwatch

The lead refuses the “disable everything” suggestion. Shutting down the appointment calendar would cancel a day of sessions and could also erase evidence. Instead the team removes the forwarding rule, revokes active sessions for the affected accounts, and resets the passwords of those accounts. The technical contact reminds everyone that the Atlas warns of a lag after switching off a cloud identity, anywhere from fifteen minutes to a whole hour, so the team watches the sign-in log for a fixed window instead of trusting the button.

They also move their conversation. Because the intruder may be reading the company mailbox, the team moves to a dial-in line and a chat group set up on private handsets. The Atlas names conducting a response over compromised email as a common anti-pattern.

Afternoon: The question of who must be told

Uploaded documents may include personal information, so reporting duties might apply. The lead does not guess. Months earlier, with the company’s legal adviser, she had drawn a sheet that lists the regimes that could be relevant and when each clock starts. In its October 2026 summary the Atlas lists a European privacy rule of three days from awareness and an American health-privacy rule of up to two months. The adviser, not the team, decides what applies. The role of “person who decides when we are aware” was assigned in advance, which the Atlas says is the thing most often missing when deadlines are missed.

This article offers general background only; it is not legal or regulatory advice, and it says nothing about care.

A second, quieter task runs in parallel: telling staff what to say. A short holding line is agreed for anyone who gets a call, stating only that the company is checking an irregularity and will follow up. It speculates about nothing, names no cause and promises no outcome. The lead has learned that off-the-cuff explanations tend to be the very things a later review has to correct, so the team keeps all statements brief, factual and approved.

Thursday: Evicting together

By midweek the list of access routes has stopped growing: one rogue forwarding rule, one reused password and one stray application token. The team replaces everything in a single window, because removing routes one at a time lets the intruder use the remaining ones. They restore nothing from backup, since nothing had been damaged, but the lead confirms that the most recent backup predates the first suspicious entry, in case it is ever needed.

The review, a fortnight later

The team measures what happened. The intruder was active for a little under two days before anyone noticed; the company declared within about twenty minutes of the first odd observation; and containment took until early afternoon. They compare those figures with the previous drill and record where they were slower than hoped. The Atlas suggests these three yardsticks, along with scope growth, rather than a simple count of incidents, which only reflects workload.

Their action list is short: enable alerts for forwarding rules, rehearse the evidence capture twice a year, and put the deadline sheet where anybody can find it offline. The coordinator takes ownership of the first item. If your own team handles shared expenses or finance tasks, the same habit of clear rules and written ownership is described in our piece on splitting bills through a recurring payment tracker. For staff who want to explore operations careers, there is also a walkthrough of a learning route for remote technology workers.

One footnote on tooling. The company runs a basic ticketing tool to track tasks and an open-source collector kept on a spare laptop. The Atlas mentions case-management projects of this sort, among them DFIR-IRIS, but it stresses that the plan comes first. The team’s tools would have been no use without the habit of declaring, logging and handing over properly. Conversely, the habits worked even on a day when the tools failed to launch.

What to take from the story

None of the team’s decisions required special equipment. They required a plan written before the day, a person with authority to declare, and the willingness to slow down for ten minutes at the right moment. If you want the reference material behind these steps, read the Ops Atlas page that explains ResponseOps, which also describes a thirty, sixty and ninety day build for organisations starting from nothing.

Finally, do not assume labels protect documents. The Atlas cites a 2020 U.S. court ruling in which a company had to hand over an investigator’s report despite involving counsel. Write findings factually, and expect that someone else may one day read them.