Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Reputation after a breach is decided by how an organisation communicates, not by the severity of the attack, and the contrast between TalkTalk and Norsk Hydro shows the gap clearly.

How Do You Manage Reputation After a Breach?
Customers, regulators, and journalists rarely judge an organisation on whether it was attacked. They judge it on what it said, when it said it, and whether what it said turned out to be true. Two European incidents illustrate the two directions this can go, and the technical severity was not what separated them.
TalkTalk disclosed a breach in October 2015 with early public statements that proved wrong on both scale and severity. Figures were revised downwards repeatedly, the chief executive gave interviews in which she could not answer basic questions about whether data was encrypted, and the story stayed in the news for weeks because each day produced a correction. The ICO fined the company £400,000 under the pre-GDPR regime, and the company reported losing around 101,000 customers and incurring costs approaching £60 million.
Norsk Hydro was hit by LockerGoga ransomware in March 2019 across its global aluminium operations. The company refused to pay, told everyone what had happened within hours, held daily open webcasts throughout the response, published its own losses as they accumulated, and ran plants manually where it could. The financial cost was severe, in the region of 70 million US dollars with only a fraction insured. Its reputation improved.
The difference was not the attack. It was that one organisation said less than it knew and one said everything it knew, including that it did not yet know enough.
UK GDPR sets two separate obligations and conflating them causes problems. Article 33 requires notification to the ICO within 72 hours of becoming aware of a personal data breach, unless it is unlikely to result in a risk to individuals. Article 34 requires communication to affected individuals without undue delay where the risk to their rights and freedoms is high. The first is a regulatory filing and can be made in phases as facts emerge; the second is a public act with reputational consequences and must be clear, specific, and practically useful.
Organisations with listed securities have a third clock, since a material incident may be inside information requiring disclosure under UK market abuse rules. Financial entities and operators of essential services have sector reporting duties on top.
Regulatory outcomes are also public. The ICO fined Advanced Computer Software Group £3.07 million in March 2025 over the 2022 attack that disrupted NHS 111, and Interserve £4.4 million in 2022. The published decision notice becomes part of the permanent record of what the organisation did or failed to do.
Draft holding statements, a notification template, a stakeholder map, and an out-of-band contact list now, and test them in a tabletop exercise with the communications and legal teams present. The common failure in exercises is not technical: it is that nobody has agreed who approves a public statement at 02:00 on a Sunday.
At Privia Security, we build communications and regulatory steps into the plans we develop during Emergency Action Plan Services, so the decisions that shape reputation are made in advance rather than improvised.
Usually yes, with a statement that reflects what is actually known. Regulatory deadlines do not wait for a completed investigation, and the alternative is that the news emerges through a leak site, a journalist, or a customer. Confirm the incident, describe the action being taken, commit to a specific update time, and avoid any figure forensics cannot yet support.
A personal data breach must be reported to the ICO within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to individuals. The report can be made in phases if full details are not yet available. Separately, affected individuals must be told without undue delay where the breach poses a high risk to them.
Because it was open at a point where silence was easier. The company confirmed the attack within hours, refused to pay, ran daily public webcasts, disclosed its losses as they accrued, and explained plainly what it did not yet know. Stakeholders had no reason to suspect concealment, so the story became one of competent handling rather than one of corporate evasion.
No. It does not stop stolen data being published or sold, it does not remove the obligation to notify the ICO and affected individuals, and the ICO has stated explicitly that payment is not a mitigating factor in its enforcement decisions. Payments also tend to emerge publicly, at which point the organisation faces criticism for the payment as well as the breach.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.