Sole Proprietor EV Code Signing
Sole Proprietor EV Code Signing
Key Benefits
Verified publisher identity
Your verified individual or sole proprietor name is displayed as publisher in Windows SmartScreen prompts, same as standard EV.
No business entity required
Validated as an individual under CA/B Forum EV sole-proprietor procedures: your verified personal name appears on every signed installer. No business entity required; the EV trust tier is accessible to solo developers.Kernel-mode driver signing
Required for Windows 10 and Windows 11 kernel-mode drivers and user-mode drivers: now accessible to individual developers through the sole-proprietor EV tier without registering a business entity.Windows Hardware Dev Center access
Required for Microsoft Partner Center (formerly Dashboard Portal) access: WHQL driver submission and Windows Update distribution are accessible to sole proprietors through this EV tier.Who Is It For?
Sole proprietors & independent developers
Sole proprietors and independent developers who need verified publisher identity in SmartScreen prompts and hardware-backed keys, without the overhead of registering a business entity.Individual driver & firmware authors
Individual driver and firmware authors: EV is the only certificate type accepted for Windows 10/11 kernel-mode drivers, and this tier makes EV accessible to individuals.Freelancers & open-source maintainers
Needing verified publisher identity as an individual, your name displayed in SmartScreen without a registered business entity.
Individual Windows Hardware partners
Individual Windows Hardware partners requiring Microsoft Partner Center access for driver submission, WHQL certification, 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 It Works
1: Purchase
Select Sole Proprietor EV duration and complete your order.
2: Individual EV validation
SSL.com validates your individual identity using extended validation procedures: no registered business entity required.
3: Certificate issued
Certificate delivered with your verified personal name. 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, same standard as organizational EV.
WebTrust for Code Signing BR
Microsoft Authenticode (EV)
Windows Hardware Dev Center
Frequently Asked Questions
Both deliver identical EV trust: verified publisher identity in SmartScreen, kernel-mode driver signing, and timestamped signatures. The difference: standard EV validates a registered business entity; Sole Proprietor EV validates an individual or sole proprietor without requiring a registered organization.
If you need verified publisher identity in SmartScreen, kernel-mode driver signing, or Windows Hardware Dev Center access, choose Sole Proprietor EV. IV Code Signing is a lower-cost option for basic code signing trust without EV-level identity validation. SmartScreen reputation builds over time for all certificate types (IV, OV, and EV).
CA/B Forum EV requirements mandate that EV private keys be stored in a FIPS 140-2 Level 2 validated HSM. You can use a physical hardware token or enroll in a cloud HSM service, which satisfies the requirement without buying physical hardware.
No: if you timestamp at signing time, the signature remains valid indefinitely. Always timestamp your code at signing.