EV Code Signing
Key Benefits
Instant SmartScreen reputation
EV certificates receive immediate SmartScreen reputation — zero download warning on first install.
All vital company information displayed
Company name, address, and identity are fully verified and displayed on every signed binary.
Kernel-mode driver signing
Required for Windows 10 kernel-mode and user-mode drivers — only EV certificates qualify.
Windows Hardware Dev Center access
EV certificate required for Dashboard Portal submission and driver distribution.
Who Is It For?
Enterprises distributing to end users
Needing instant download trust without SmartScreen friction from day one.
Driver & firmware publishers
EV is the only certificate type for Windows kernel-mode and user-mode drivers.
DevOps & CI/CD teams
Needing EV-level signing in automated pipelines via cloud HSM — no physical token.
Windows Hardware partners
Requiring Dashboard Portal access for driver submission and certification.
Purchase & Pricing
1. Select Certificate Duration
2. Select Key Storage & Delivery (optional)
eSigner Cloud Signing
Sign anywhere using eSigner.com. No hardware required.Select the monthly or annual signature volume tier. Any unused signatures will roll over into the next month or year if there is an active certificate. Each tier provides a certain number of included credentials which are pre-selected based on the selected tier. Extra credentials can be purchased at $20 per month. New certificates will receive 30-days free of eSigner cloud signing. After the first 30 days, your monthly or annual subscription fees will be applied. For multi-year subscription discounts, high-volume signature packages and custom solutions, please contact sales.
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.
What is attestation? Before issuing your certificate, SSL.com verifies that your private key was generated and is stored inside your cloud HSM ā not exportable to software. This one-time attestation fee covers the verification process with your chosen provider.
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. International shipping tracked; delivery subject to customs. 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 It Works
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
Issued under CA/B Forum EV Code Signing Baseline Requirements.
Microsoft Authenticode (EV)
Required for kernel-mode drivers and immediate Microsoft SmartScreen reputation.
Windows Hardware Dev Center
EV certificate required for portal access and driver submission.
WebTrust for Code Signing BR
SSL.com is audited annually by BDO under WebTrust for Code Signing Baseline Requirements.
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.
With OV, SmartScreen reputation builds over time. With EV, reputation is immediate from the first download — zero user-facing SmartScreen warnings.
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.
Ready to get EV Code Signing?
Related Products
OV Code Signing
Organization signing without EV requirements — your company name on every installer.
Sole Proprietor EV
Same EV trust for individuals — no registered business entity required.