{"id":38904,"date":"2020-12-21T17:18:33","date_gmt":"2020-12-21T17:18:33","guid":{"rendered":"http:\/\/1b187661-5757-4084-afef-ed8becc66f29"},"modified":"2020-12-21T17:18:33","modified_gmt":"2020-12-21T17:18:33","slug":"security-vendors-its-time-to-come-clean-about-intrusions","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/security-vendors-its-time-to-come-clean-about-intrusions\/","title":{"rendered":"Security vendors: It\u2019s time to come clean about intrusions"},"content":{"rendered":"
<\/div>\n

The intrusion into SolarWinds, FireEye, and multiple US Government agencies continues to roil the cybersecurity world. In the past week, a slew of additional details have emerged about the scope of the intrusions with more surely to come. <\/p>\n

\n

SolarWinds Coverage<\/span> <\/h3>\n<\/p><\/div>\n

Security vendors spend all their time talking about security, but not in a way that’s useful right now. As we wrote in our prior blog, no vendor should turn what happened to these companies into a marketing opportunity. Let us repeat for emphasis: no vendor should turn what happened to these companies into a marketing opportunity. Other security vendors should also understand that this is not a time to throw stones at FireEye — a breach like this could happen to any vendor. <\/p>\n

But security vendors do need to have a conversation with customers. Security leaders need answers. <\/p>\n

Security vendors are notoriously close mouthed about attempted intrusions against them as a vendor. Despite a series of intrusions on vendors — RSA and Lockheed Martin<\/a>, MeDoc<\/a>, SolarWinds<\/a>, and FireEye<\/a> — it is virtually impossible to get a vendor to talk about what they deal with. And as the prior examples demonstrate that vendor intrusions are often a mechanism into their customers as well. Here’s why this matters now: <\/p>\n

If the threat actors went after FireEye — what other security vendors did they go after? <\/strong><\/p>\n

Does anyone doubt that other security vendors were on the list of potential targets? <\/strong><\/p>\n

End users should ask the following of their security vendors: <\/p>\n