Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A code signing certificate lets a publisher sign software so users and operating systems can confirm who produced it and that nobody altered it afterwards. Stolen signing keys are prized by attackers.

What Are Code Signing Certificates?
A code signing certificate binds a publisher’s identity to a private key used to sign executables, drivers, installers, scripts, and packages. When a user runs the file, the operating system checks the signature, confirms that the bytes have not changed since signing, and displays the publisher name rather than the blunt warning reserved for unknown software.
It is an authenticity control, not a safety guarantee. A signature says Acme Ltd produced this file. Whether Acme Ltd produced something you should run is a separate question entirely.
The mechanics are the same as any digital signature: hash the file, sign the hash with the private key, and embed the signature plus the certificate chain in the file itself. Verification recomputes the hash, checks the signature, and validates the chain to a trusted root.
Each platform wraps that differently:
A signature made without a trusted timestamp becomes invalid the day the certificate expires, which would break every copy of the software already shipped. An RFC 3161 timestamp from a timestamping authority records when the signature was made, so verification succeeds afterwards as long as the certificate was valid at that moment. Sign without a timestamp and you have given your release a two- or three-year shelf life.
A signed implant bypasses warnings, satisfies many application allowlisting rules, and often evades endpoint detection that treats signed binaries as lower risk. The history is long:
Because of incidents like these, the CA/Browser Forum changed the rules: since 1 June 2023 the private keys for all publicly trusted code signing certificates must be generated and held in hardware meeting FIPS 140-2 Level 2 or Common Criteria EAL4+, whether a USB token, a hardware security module, or a cloud signing service. Exporting a signing key to a build agent is no longer permitted, and for good reason.
Revocation deserves thought in advance. Revoking a code signing certificate can invalidate every unsigned-by-timestamp release at once, so vendors and CAs usually set a revocation date tied to the suspected compromise. Deciding that under pressure, during an incident, is not the moment to discover your build records are incomplete.
Open source projects increasingly use Sigstore, which issues short-lived certificates tied to an identity from an OpenID Connect provider and records every signature in a public transparency log called Rekor. The model removes long-lived keys from the equation and gives the same public auditability that Certificate Transparency brought to TLS. For organisations building their own software, signing sits alongside SBOM generation and dependency provenance as part of a defensible pipeline, which we assess within our regulation and compliance services.
No. Signing proves who published the file and that it has not been modified since. Malware authors obtain certificates under shell company names, buy them on criminal markets, or steal them from legitimate vendors. Treat a valid signature as identity evidence that supports reputation checks, not as a verdict on whether the code is trustworthy.
Since June 2023 all publicly trusted code signing keys must be stored in approved hardware, so the practical gap between standard and EV has narrowed. EV still carries more weight with Microsoft SmartScreen reputation and is required for kernel-mode driver attestation on Windows. For normal user-mode applications a standard certificate with good release hygiene is usually enough.
Nothing, provided each signature carries an RFC 3161 timestamp proving it was made while the certificate was valid. Without a timestamp, verification fails on the expiry date and users see warnings on software that worked the day before. Always timestamp, and check that your signing tooling has not silently skipped it.
Do not store it in CI at all. Use a cloud signing service or an HSM that signs on request, authenticate the pipeline to it with a short-lived workload identity, and restrict which branch or release job may invoke signing. Log every signing operation and alert on requests outside the release window.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.