{"id":3747,"date":"2024-05-24T08:51:48","date_gmt":"2024-05-24T13:51:48","guid":{"rendered":"https:\/\/www.darkreading.com\/cyber-risk\/the-sec-solarwinds-case-what-ciso-should-do-now"},"modified":"2024-05-24T08:51:48","modified_gmt":"2024-05-24T13:51:48","slug":"the-secs-solarwinds-case-what-cisos-should-do-now","status":"publish","type":"post","link":"https:\/\/ddi.mohflo.net\/index.php\/2024\/05\/24\/the-secs-solarwinds-case-what-cisos-should-do-now\/","title":{"rendered":"The SEC’s SolarWinds Case: What CISOs Should Do Now"},"content":{"rendered":"
<\/a><\/div>\n
<\/div>\n

COMMENTARY<\/span><\/span><\/p>\n

In October 2023, the Securities and Exchange Commission (SEC) dramatically altered the landscape for security professionals by initiating a groundbreaking lawsuit against SolarWinds Corp. and its chief information security officer (CISO). The case was notably the first time the SEC has charged a CISO individually in an enforcement case and has many security leaders questioning what immediate steps they should take to protect both themselves as individuals, as well as their organizations, against similar litigation.<\/span><\/p>\n

Most everyone working in cybersecurity today is aware of the SolarWinds breach, which occurred in 2020, when a threat actor gained unauthorized access to the networking company’s environment and planted malware in its Orion software. SolarWinds unknowingly disseminated the Orion update containing the malware to customers.<\/span><\/p>\n

Late last year, the SEC sued SolarWinds and its CISO, Timothy Brown, alleging both made false and misleading statements to investors about SolarWinds’ cybersecurity risks, practices, and vulnerabilities in documents filed with the SEC, in a \u201cSecurity Statement\u201d posted to the company\u2019s website, and in various other media, including press releases, podcasts, and blog posts. <\/span><\/p>\n

What Should CISOs Do?<\/h2>\n

The SEC’s case may take years to resolve through litigation, but here are five action items all public company CISOs should consider now.<\/span><\/p>\n

\n