Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security //

Ransomware

3/25/2019
11:15 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

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.

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.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-3493
PUBLISHED: 2021-04-17
The overlayfs implementation in the linux kernel did not properly validate with respect to user namespaces the setting of file capabilities on files in an underlying file system. Due to the combination of unprivileged user namespaces along with a patch carried in the Ubuntu kernel to allow unprivile...
CVE-2021-3492
PUBLISHED: 2021-04-17
Shiftfs, an out-of-tree stacking file system included in Ubuntu Linux kernels, did not properly handle faults occurring during copy_from_user() correctly. These could lead to either a double-free situation or memory not being freed at all. An attacker could use this to cause a denial of service (ker...
CVE-2020-2509
PUBLISHED: 2021-04-17
A command injection vulnerability has been reported to affect QTS and QuTS hero. If exploited, this vulnerability allows attackers to execute arbitrary commands in a compromised application. We have already fixed this vulnerability in the following versions: QTS 4.5.2.1566 Build 20210202 and later Q...
CVE-2020-36195
PUBLISHED: 2021-04-17
An SQL injection vulnerability has been reported to affect QNAP NAS running Multimedia Console or the Media Streaming add-on. If exploited, the vulnerability allows remote attackers to obtain application information. QNAP has already fixed this vulnerability in the following versions of Multimedia C...
CVE-2021-29445
PUBLISHED: 2021-04-16
jose-node-esm-runtime is an npm package which provides a number of cryptographic functions. In versions prior to 3.11.4 the AES_CBC_HMAC_SHA2 Algorithm (A128CBC-HS256, A192CBC-HS384, A256CBC-HS512) decryption would always execute both HMAC tag verification and CBC decryption, if either failed `JWEDe...