{"id":50857,"date":"2023-03-04T00:01:08","date_gmt":"2023-03-04T00:01:08","guid":{"rendered":"https:\/\/www.threatshub.org\/blog\/snap-ciso-i-rate-software-supply-chain-risk-9-9-out-of-10\/"},"modified":"2023-03-04T00:01:08","modified_gmt":"2023-03-04T00:01:08","slug":"snap-ciso-i-rate-software-supply-chain-risk-9-9-out-of-10","status":"publish","type":"post","link":"https:\/\/www.threatshub.org\/blog\/snap-ciso-i-rate-software-supply-chain-risk-9-9-out-of-10\/","title":{"rendered":"Snap CISO: I rate software supply chain risk 9.9 out of 10"},"content":{"rendered":"

SCSW<\/span> On a scale of 1 to 10, 10 being the highest risk, Snap Chief Information Security Officer Jim Higgins rates software supply chain risk “about 9.9”<\/p>\n

Ten, for the record, is “always security hygiene,” he told The Register<\/em>. It seems we’re a long way from avoiding the next SolarWinds-style scenario.<\/p>\n

Not only is the supply chain at high risk, but it’s a tough security problem to fix because a single product can have tens of thousands of software dependencies. <\/p>\n

“It’s a physics problem,” Higgins said, in that software packages are dependent on so many other third-party and open-source software libraries. And it only takes a bug in one of these to make your organization the next cautionary tale.<\/p>\n

The most important thing his fellow CISOs can do to improve supply chain security is to know what software their organization uses and understand the dependencies across the supply chain, according to Higgins. He recommends adding a full inventory of libraries in use as a start point for fixing the problem, so security staff know exactly what to check.<\/p>\n

“Understanding your inventory is absolutely No. 1,” he said. “It’s 50 percent of the problem. If you can understand where everything is and a CVE hits, then at least you know immediately what you need to do and where.”<\/p>\n

Oh, and also, don’t forget to patch. \u00ae<\/p>\n