Norsk Hydro: This Is How You React to a Ransomware Breach

The company's response to a massive ransomware attack is an object lesson in how to do it right.

Larry Loeb, Blogger, Informationweek

March 25, 2019

3 Min Read

You're the new CEO of a global manufacturing company. On your first day on the job, you hang your pictures and find the washroom.

On the second day, your worldwide IT structure gets taken out by the LockerGoga ransomware. The entire company goes down. Both back office and production systems have been affected and are unusable.

That's what happened to the new CEO of aluminum maker Norsk Hydro last week. And you thought your week was bad.

What was not bad was how the company responded. Their overall response will serve future business scholars as an example of how to do it right.

Norsk gave transparency and insight into a tough situation. They took active and proactive measures to disseminate the facts. For example, a temporary website was set up. Details of what was occurring were given via Facebook posts to both the press and staff to prevent rumor formation.

Their efforts even extended to holding daily webcasts with the most senior staff talking through what was occurring, as well as answering questions. They even took questions from webcast watchers. As a result of their efforts, their stock's price managed to go up after the incident. Investors responded positively to what they saw as real information, not conjecture.

In a press release, the company said that the root cause of the problems had been detected, a cure has been identified, and together with external partners (including national security authorities) that Hydro was working on reverting virus infected systems back to a pre-infected state.

They were not going to pay the demanded ransom.

Jo De Vliegher, head of information systems, also said in that same press release that: "Experts from Microsoft and other IT security partners have flown in to aid Hydro in taking all necessary actions in a systematic way to get business critical systems back in normal operation."

The company said production had resumed to normal levels by the week's end after the attack, except for Extruded which was at 50%. UK security researcher Kevin Beaumont said in his blog that the attack happened because the malware was not being identified by endpoint solutions rather than any missteps the company took.

Additionally, the malware was signed with a certificate that had been given to a company that reported only £1 of assets. Worse, the Certificate Authority failed to revoke the certificate in a timely manner. A revocation, by the way, may not have stopped the malware since many security tools do not retrieve the CRL and check the serial number for revocation.

Since the company uses Office365 they could still communicate with each other, the press and customers by using non-IT infrastructure like mobile phones. Because their communications had been migrated to a managed cloud service, the capability to communicate was not affected.

The upshot is that Norsk did things right, and still got hit. But they survived because they had already planned for this kind of problem by having good backups available and dealt in a straightforward and honest manner with their customers.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Read more about:

Security Now

About the Author(s)

Larry Loeb

Blogger, Informationweek

Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek. He has written a book on the Secure Electronic Transaction Internet protocol. His latest book has the commercially obligatory title of Hack Proofing XML. He's been online since uucp "bang" addressing (where the world existed relative to !decvax), serving as editor of the Macintosh Exchange on BIX and the VARBusiness Exchange. His first Mac had 128 KB of memory, which was a big step up from his first 1130, which had 4 KB, as did his first 1401. You can e-mail him at [email protected].

Keep up with the latest cybersecurity threats, newly discovered vulnerabilities, data breach information, and emerging trends. Delivered daily or weekly right to your email inbox.

You May Also Like


More Insights