Keyfactor Tech Days 2027 – Be Part of The Trust Security Conference in San Diego Register now!

The Need for Code Signing Certificate Protection & the ASUS Hack

Ted Shorter Ted Shorter Chief Technology Officer & Co-Founder
Keyfactor Go Daddy Certificate Misissue Apple Google

“We saw the updates come down from the Live Update ASUS server. They were trojanized, or malicious updates, and they were signed by ASUS,” said Liam O’Murchu, director of development for the Security Technology and Response group at Symantec.

Assuming ASUS properly implemented their signature validation, it seems likely that hackers may have stolen ASUS’ signing keys in order to accomplish this.  Signifying a lack in automation around code signing certificate protection.

In the last few years, we have seen a growing awareness around code signing, and an uptick in code signing and validation – which is great.  However, if you lose control of the private keys, the whole system falls apart.  And today very few organizations properly protect code signing certificates:  they’re on developers’ workstations, build servers, etc.  they should be carefully protected, and they’re usually not – because it’s hard to do.

Subscribe to The Source

Stay secure with Keyfactor's monthly newsletter, packed with expert insights and practical steps for quantum-readiness.

Continue Reading

Solving for Self-Signed Certificate Errors in Your Certificate Chain
Certificate Management

Solving for Self-Signed Certificate Errors in Your Certificate Chain

Read more
How PKI, Crypto and Machines Make the Digital World Go 'Round
Machine Identity Management

Gartner Webinar Preview: How Crypto Makes the World Go Round

Read more
Industrial Internet of Things (IIoT)

Balancing Security and Interconnectivity in the Manufacturing Industry

Read more