Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Skip to content Skip to footer

The Solarwinds Tipping Point

Published by: Digicert

In December 2020, hackers had broken into several federal government computer networks and the attack was traced back to a software system, called Orion, an IT management program built and sold by the Texas-based cybersecurity company SolarWinds.
Signing software is important in and of itself, but it's all too easy to overlook the management of signing policies and practices—and that's where we find security gaps that can be exploited. When it comes to software security, the choice is binary. You can choose best practices, or you can choose to leave your supply chain open to attack.
The vulnerability that led to the SolarWinds data breach wasn't caused by weak security tools. It was a failure to implement every step on the list of code signing best practices. How could the SolarWinds attack have been prevented?

Read More

By submitting this form you agree to Digicert contacting you with marketing-related emails or by telephone. You may unsubscribe at any time. Digicert web sites and communications are subject to their Privacy Notice.

By requesting this resource you agree to our terms of use. All data is protected by our Privacy Notice. If you have any further questions please email dataprotection@techpublishhub.com

digital route logo
Lang: ENG
Type: Whitepaper Length: 9 pages

More resources from Digicert