XML 32 R21.htm IDEA: XBRL DOCUMENT v3.20.2
Ransomware Incident
6 Months Ended
Jun. 30, 2020
Ransomware incident  
Ransomware incident

Note 14 —Ransomware Incident

During the fourth quarter ended December 31, 2019, some of the Company’s systems were affected by a ransomware incident that encrypted information on its systems and disrupted customer and employee access to its applications and services. The Company immediately took steps to isolate the impact and implemented measures to prevent additional systems from being affected, including taking its network offline as a precaution. In connection with this incident, third party consultants and forensic experts were engaged to assist with the restoration and remediation of the Company’s systems and, with the assistance of law enforcement, to investigate the incident. The Company has found no evidence that customer or employee data was exfiltrated from its network.

 

The Company restored connectivity and resumed operations quickly following the ransomware incident. However, fourth quarter 2019 operations were adversely affected by the inefficiencies caused by taking the network offline for a period of time. As a result, the Company’s fourth quarter 2019 revenue was also adversely affected as the Company was unable to fulfill a portion of customer demand during the quarter.

 

We do have insurance coverage, including cyber insurance, and are working diligently with our insurance carriers on claims to recover costs incurred. We expect that the insurance recovery process will be ongoing throughout 2020.

 

In 2019, ransomware incident related costs incurred totaled $7.7 million, net of estimated insurance recoveries of $5.0 million. These costs were primarily comprised of certain employee related expenses and various third party consulting services including forensic experts, legal counsel and other IT professional expenses. Further insurance recoveries will be recorded when considered probable. During the six months ended June 30, 2020, the Company collected $3.0 million of its recorded insurance receivable.