Software Integrity
Prove your software is genuine: before it runs on anyone’s machine
Two ways to sign and protect your software
Code Signing Certificates
Sign your code with a validated identity. IV for individuals, OV for organizations, EV for maximum trust and verified publisher identity.
eSigner for Code: Cloud Signing
Sign from the cloud. No hardware token required. Integrates with GitHub Actions, Jenkins, Azure DevOps, and more.
SSL‘s code signing certificates and cloud signing service let you cryptographically sign executables, drivers, scripts, and firmware, so users, platforms, and operating systems can verify your software is authentic and hasn’t been tampered with before it runs. Every certificate level and the cloud signing service share the same underlying trust chain, so the right choice depends on who needs to be named on the signature and how you want to manage the private key, not on a difference in security.
Unsigned or improperly signed code is one of the leading software supply chain attack vectors
Software supply chain attacks, from SolarWinds to XZ Utils, have made one thing clear: the integrity of code between the developer and the end user is not guaranteed without cryptographic signing. Operating systems, platforms, and security tools increasingly require signed binaries, and the shift is now backed by policy as well as practice: the NIST Secure Software Development Framework (SSDF) and the software supply chain requirements that followed Executive Order 14028 both call for signed provenance on software artifacts, and compliance frameworks including SLSA and SOC 2 build on the same expectation.
SSL’s Software Integrity products address two distinct needs:
- Code Signing Certificates: validated certificates that cryptographically bind your identity to the code you sign, at three validation levels (IV, OV, EV)
- eSigner for Code: a cloud-based signing service that eliminates the hardware token requirement for EV code signing, enabling seamless CI/CD pipeline integration
Compare code signing certificate options
Compliance & Standards
Microsoft Authenticode
All Windows executable signing, OV and EV trusted
Windows Kernel Mode Drivers
Requires EV Code Signing certificate
Microsoft SmartScreen
Your verified organization name is displayed as publisher in SmartScreen prompts
Apple Gatekeeper / Notarization
macOS distribution requires Developer ID signing and notarization
CA/B Forum Code Signing BR
All SSL certificates comply with Code Signing Baseline Requirements
