EV Code Signing
EV Code Signing
Key benefits of EV Code Signing certificates
Verified publisher identity
Your organization’s legal name displays as a verified publisher in Windows SmartScreen prompts, Microsoft Store submissions, and User Account Control dialogs: the strongest trust signal Windows displays to end users.All vital company information displayed
Company legal name, registered address, and full organizational identity details are verified under CA/B Forum EV procedures and embedded in every signed binary. Visible in Authenticode signature details.Kernel-mode driver signing
Required for Windows 10 and Windows 11 kernel-mode drivers and user-mode drivers: only EV certificates satisfy the Windows Hardware Quality Labs (WHQL) signing requirements for driver distribution.Windows Hardware Dev Center access
EV certificate required for Microsoft Partner Center (formerly Dashboard Portal) access, driver cross-signing submission, WHQL certification, and Microsoft Store app submission under an organization identity.Who needs an EV Code Signing certificate?
Enterprises distributing to end users
Enterprises distributing software to end users who need verified publisher identity displayed in SmartScreen prompts, plus hardware-backed private keys for enterprise security review and SOC 2 audit evidence.Driver & firmware publishers
Driver and firmware publishers: EV is the only certificate type accepted for Windows 10/11 kernel-mode drivers, user-mode drivers, and WHQL-certified driver submission.DevOps & CI/CD teams
DevOps and CI/CD teams needing EV-level signing in automated build pipelines. SSL.com eSigner for Code provides cloud HSM-backed EV signing via REST API: no physical token distributed to build machines.Windows Hardware partners
Windows Hardware Dev Center partners requiring Partner Center portal access for driver submission, WHQL testing, and signed driver distribution through Windows Update.Purchase & Pricing
1. Select Certificate Duration
2. Select Key Storage & Delivery (optional)
eSigner Cloud Signing
Sign anywhere using eSigner.com. No hardware required.YubiKey
Physical TokenYubiKey & EV certificates: YubiKey tokens are fully suitable for OV code signing. If you require EV code signing, particularly for kernel-mode driver signing (Microsoft HLK), a YubiKey may not meet those requirements. Contact us to discuss EV-compatible token options.
Standard
3ā5 business days after validation (Continental US)Express + $329.00
1 day after validationBring Your own Cloud HSM
Self-managed infrastructureSSL.com must attest your key to your chosen provider before issuing the certificate. This fee is a one-time charge per order.
Looking for a simpler option? SSL.com eSigner for Code provides cloud-based signing with no HSM to provision, no attestation fee, and a lower total cost for most teams.
Bring your own on-premises HSM
SSL performs an attestation ceremony for your compliant on-premises HSM.Please contact sales.
3. Validation Speed (optional)
Choose how quickly your organization or identity is validated before your certificate is issued.
Standard
3ā5 day validation Ā· 2ā3 day US shipping Validation completed after all agreements, entity info submitted, and a successful callback to a listed phone number. IncludedExpedited
2 business day validation Ā· overnight US delivery 2 business days priority validation from first complete submission and callback. Token shipped overnight in continental US. +$599.00Order Summary
How EV code signing works with eSigner cloud HSM
1: Purchase
Select EV duration and complete your order.
2: Organization & EV validation
SSL.com validates your organization identity using extended validation procedures.
3: Certificate issued
Certificate issued with your verified organization details. Must be stored on a FIPS 140-2 validated hardware token or cloud HSM.
4: Sign your code
Use signtool.exe with your hardware token.
5: Timestamp
Always timestamp at signing: EV signed code remains trusted permanently with a valid timestamp.
Compliance & Standards
CA/B Forum EV Code Signing Requirements
Microsoft Authenticode (EV)
Windows Hardware Dev Center
WebTrust for Code Signing BR
Frequently asked questions
CA/B Forum EV requirements mandate that EV private keys be stored in a FIPS 140-2 Level 2 validated HSM. A cloud HSM satisfies this requirement without physical hardware.
Microsoft SmartScreen reputation builds over time for both OV and EV certificates: each new build accumulates reputation based on clean-install download volume. EV still offers stronger trust signals: your organization name is displayed as verified publisher in SmartScreen prompts, and EV is required for kernel-mode driver signing. Note: since 2024, Microsoft no longer grants EV-signed binaries immediate SmartScreen reputation on first download.
No: if you timestamp at signing time, the signature remains valid indefinitely even after the certificate expires.
Yes: Microsoft requires an EV code signing certificate for Windows 10 kernel-mode drivers. No other certificate type qualifies.