bastion

Incident Reporting and Communication

Build this skill

Report and escalate an incident through the right channels, keep a factual incident log and write a responsible notice to affected people.

Who hears about the attack, and how fast

Arjun sees the scrambled files on the Nashik Road counter laptop at 4:40 pm. What he does within two minutes, and what Neha does over the following two hours, decides who learns about the incident, how quickly, and from whom. Incident reporting is getting news of an incident to the right people through an agreed route. Incident communication is what you then tell everyone affected: staff, customers, partners and the authorities. Both go wrong surprisingly often. People hesitate to report, the news reaches the wrong person, or customers hear rumours before they hear the truth.

A reporting route everyone knows

An incident reporting procedure is a short, simple, well-known way for anyone to raise the alarm. At Tulsi Health it is printed on a card at every counter: call IT on extension 200, or the IT mobile number after hours, and say what you saw, when, on which device, and what you have already done. It works like the fire alarm in a college hostel. Anyone may press it, nobody needs to be sure there is a fire, and nobody is punished for a false alarm, because a false alarm costs minutes while a silent fire costs the building.

Two details make the route work. First, people must not be blamed for reporting, even when they caused the problem by clicking a link, otherwise they hide mistakes and the attacker gains days. Second, the report should use a channel the attacker cannot see. If an attacker controls a laptop, they may be reading its email too, so Arjun phones instead of emailing. Using a separate channel like this is called out-of-band communication.

Escalation: moving it up the ladder

Escalation means passing an incident to people with more authority or more skill as its seriousness becomes clear. A hospital works this way: the ward nurse calls the duty doctor, the duty doctor calls the specialist, and for something very serious the hospital head is told. An escalation matrix writes down in advance who must be told at each severity level, and how fast, so nobody has to decide under pressure whether to disturb the boss on a Saturday evening.

Severity Example at Tulsi Health Who is told How fast
Low One failed login from a store laptop Logged by IT Next working day
Medium Phishing email reported by five staff, nobody clicked Neha Within 4 hours
High A staff account used from an unknown computer Neha and Vikram Within 1 hour
Critical Ransomware spreading, customer data at risk Neha, Vikram, outside experts and authorities At once
ArjunNehaVikramOutsidePhone call, 4:40 pm1Rates it Critical2Escalates, 4:55 pm3CERT-In, insurer, vendor4Staff instructions5

Information moves up as the severity becomes clear, and instructions move back down. The outside reports are planned in advance, not invented on the night.

Some incidents must also be reported outside the organisation. In India, directions issued in 2022 by CERT-In, the national agency that responds to cyber incidents, require organisations to report many kinds of cyber incident, ransomware included, within six hours of noticing them. Separately, under the Digital Personal Data Protection Act, 2023, an organisation whose personal data is breached must inform the Data Protection Board and the people affected. Six hours passes quickly in a crisis, so the plan names in advance who files these reports and keeps the forms ready.

Follow the evening's escalation step by step below. A few steps pause to ask what should happen next, so decide before you reveal each one.

The incident log: one record of the truth

Incident documentation is the running written record of an incident, usually kept in one shared incident log or ticket. Every entry carries an exact time, who saw or did something, what happened, and any decision made, with who made it and why. Entries are added as things happen, not written up afterwards from memory, and facts are kept clearly separate from guesses. The log serves many readers: the next person on shift, the CERT-In report, the insurer, any legal case, and the review meeting at the end.

INC-0317 · Ransomware, Nashik Road CRITICAL 16:40 Arjun (store): files renaming on NR-1. Cable pulled. 16:52 Neha: ransomware confirmed. Severity set to Critical. 17:05 Neha: shared-drive access for Nashik accounts paused. 17:15 Decision (Vikram): stores stay open, bill on paper. 18:30 Neha: report sent to CERT-In. Receipt saved. 19:20 Unknown: was customer data copied out? Checking logs. All times IST · entries added as they happen Exact time, every line one time zone throughout Who saw or did it a name, not a blame Decisions, and by whom so nobody argues later Facts kept apart from guesses and unknowns

A good log reads like a ship's logbook: short, timed, factual entries. The last line openly says what is still unknown instead of guessing.

Saying the right thing to the right people

Responsible communication is honest, timely, accurate and useful to the person receiving it. Staff should hear first and from inside, so they do not learn about the attack from a WhatsApp forward. Customers need plain words: what happened, which of their details were involved and which were not, what Tulsi Health has done, and what they should do now. One person, usually Vikram, speaks for the company, so that different staff do not give different stories.

What you leave out matters as much. Do not guess who the attacker was, do not promise it can never happen again, do not blame a named employee, and do not publish technical details that would help another attacker. There is also a real danger after any breach announcement: criminals phone the affected customers pretending to be the company. A customer like Mrs. Lata Gokhale is safer when the notice says plainly that Tulsi Health will never call to ask for an OTP, the one-time code sent to your phone.

Helps the readerWhat happened, in plain wordsWhich data was involved, and which was notWhat has been done so farWhat to do now, and what to ignoreWhere to ask questionsHarms the reader or the responseBlaming a named employeeGuessing who the attacker wasPromising it can never happen againTechnical details that help attackersSilence until rumours spread

Every line in a customer notice should either inform or protect the reader. Anything else adds risk.

Now sort the draft lines for Tulsi Health's customer notice. Ask of each one whether it informs or protects the reader, or whether it blames, guesses or helps an attacker.

The review after the dust settles

A post-incident review, also called a lessons-learned meeting, happens within a week or two of the incident closing. The team walks through the timeline from the incident log and asks what happened, what went well, what went badly, and why. It is blameless: the aim is to fix systems and habits, not to punish a person. Think of a cricket team watching the match replay. Nobody shouts at the bowler; they change the field placing so the same shot does not find the gap next time. Every finding ends as an action with an owner and a date, otherwise the meeting becomes a conversation that changes nothing.

What happenedFake invoice email on ThursdayNight login with a stolen passwordEncryption on Saturday afternoonWhat went wellCounter card followed exactlySpread stopped within 25 minutesCERT-In report filed in timeWhat went badlyNo two-step login on staff accountsBackups never tested by restoringLogs nearly overwrittenActions, owner, dateTwo-step login: Neha, by 1 DecMonthly restore test: Neha, from DecPhishing drill: Riya, by 15 Dec

The review ends with named actions and dates. Those actions become part of preparation for the next incident.

Follow your curiosity.

↑ ↓ to explore · Enter to open · Escape to close