Comodo EV Code Signing Certificate
Establish a stronger level of publisher identity assurance for digitally signed software with Comodo EV Code Signing, now available through the Sectigo ecosystem. Protect your signing key with suitable hardware and build a controlled release workflow for Windows and other supported software environments.
Check Current Official PricingCurrent official Sectigo EV Code Signing price, checked October 18, 2026. Comodo-branded products are offered through the Sectigo ecosystem. Confirm current terms on the official page before ordering.
What Is a Comodo EV Code Signing Certificate?
Comodo EV Code Signing is an Extended Validation certificate designed to provide stronger assurance about the identity of a software publisher. It binds a verified publisher identity to a digital signature so recipients can verify who signed supported software and whether the signed content has been modified.
Comodo is now part of Sectigo
Comodo certificate offerings are now part of the Sectigo ecosystem. Existing Comodo branded certificate products remain accessible through the Sectigo ecosystem, while current issuance and security requirements follow modern Code Signing rules.
This page keeps the Comodo product name because that is what users may search for, but it does not present ComodoCA as an independent current certificate authority.
Higher publisher assurance
EV provides more extensive publisher validation than OV. The purpose is not simply to make software safer than every OV signed application, but to provide a higher level of verified publisher identity assurance.
Both modern EV and OV workflows use protected signing keys under current Code Signing requirements.
Key Features of Comodo EV Code Signing
Comodo EV combines Extended Validation with protected private key handling, timestamping and support for common software signing workflows.
Extended Validation
EV requires more extensive validation than standard OV Code Signing and is intended for organizational applicants.
Hardware Protected Key
The private signing key is generated, stored and used inside suitable compliant hardware rather than treated as an ordinary exportable file.
Hardware Token
A compatible hardware token can hold the signing credential for controlled workstation based signing.
HSM Support
A supported HSM can fit centralized signing infrastructure, automation and enterprise release environments.
Key Attestation
Attestation provides evidence that the private key was generated inside the hardware and cannot be exported.
Timestamping
Trusted timestamping can preserve evidence of when the signature was created and should be part of production signing. The details are covered in code signing and timestamping.
How Much Does Comodo EV Code Signing Cost?
Sectigo’s official Code Signing page currently lists EV Code Signing at $829/year and OV Code Signing at $715/year. These are the official prices displayed for the current Sectigo offerings, not reseller prices. Pricing and purchase terms can change, so check the official page before ordering.
| Pricing detail | Current official information |
|---|---|
| EV Code Signing | $829/year |
| OV Code Signing | $715/year |
| Pricing source | Sectigo official website, checked October 18, 2026 |
| Purchase terms | Confirm available term and final checkout price on Sectigo’s official page |
| Older Comodo pricing | Historical only; not the current official price |
| Maximum individual certificate validity | 459 days under current Sectigo rules |
Pricing note: The current official Sectigo page lists EV Code Signing at $829/year and OV Code Signing at $715/year. Prices can change; the official Sectigo page is the source of truth for the amount available at checkout.
Choosing EV Code Signing for Your Software?
Compare the requirements for an EV certificate with your publishing, validation and protected-key needs before purchasing.
Compare EV Code Signing RequirementsHow Comodo EV Code Signing Works
The signing process creates a cryptographic association between the software, the protected private key and the EV certificate. See how code signing works for the cryptographic sequence. A trusted timestamp is added so the signing event has an independent time reference.
When a recipient verifies the signed software, the signature can be checked to determine whether the publisher identity is trusted and whether the signed content has changed.
Comodo EV Code Signing Validation Requirements
EV Code Signing requires more extensive validation than OV. The current Sectigo validation process can include organizational checks, public record verification, applicant authorization, identity verification, callback verification and additional documentation.
Organization legitimacy
Verification that the organization is legitimate and operational.
Organizational information
Review of relevant organization information and records.
Public record checks
Applicable public records can be checked as part of EV validation.
Applicant authorization
Confirmation that the applicant is authorized to request the certificate.
Identity verification
Verification of the relevant authorized contact or applicant.
Callback verification
Organizational callback procedures may be required during validation.
Validation timing: Do not promise a fixed issuance time. The exact evidence and verification steps can vary according to the applicant and jurisdiction.
The Private Signing Key Must Stay Protected
Modern Code Signing requirements make hardware based private key protection a central part of the issuance and signing workflow. The private key should not be handled as an ordinary downloadable file. Follow established code signing key protection practices.
Compatible hardware tokens and supported HSM based signing environments can protect the private key while allowing controlled signing operations.
Comodo EV Code Signing With a Hardware Token
A compatible hardware token can store and protect the signing credential. Current Sectigo documentation includes workflows for EV certificates stored on USB tokens.
Typical token based workflow
This approach is useful for controlled workstation based signing where the physical token can remain under the organization's control.
Comodo EV Code Signing With an HSM
An HSM becomes more relevant when signing needs to be integrated into centralized infrastructure rather than tied to a single workstation.
Where HSM fits
- Enterprise software teams
- Automated release environments
- CI/CD pipelines
- Centralized signing
- Multiple build environments
- Organizations with existing HSM infrastructure
Why hardware backed signing matters
An HSM keeps the signing key inside protected hardware while allowing a properly configured signing process to request cryptographic operations. This is suitable for organizations that need repeatable and controlled signing across release infrastructure.
What Is Key Attestation?
Key attestation provides evidence that the private key was generated inside suitable hardware and cannot be exported. This evidence supports the current hardware based Code Signing model.
Generated inside hardware
The private key is created within the approved HSM or token instead of as an ordinary exportable file.
Remains protected
The key stays under the control of the hardware throughout the signing process.
Cannot be exported
Attestation provides evidence that the private key cannot be exported from the protected device.
Comodo EV Code Signing for Windows
Windows software is a major Code Signing use case. For platform details, see the Windows code signing guide. EV can be used with supported Microsoft Authenticode files, including common application and installer formats.
EXE
Sign supported Windows executable applications.
MSI
Sign Windows installer packages.
DLL
Sign supported Windows libraries.
CAB
Sign supported cabinet files.
Authenticode
Use Microsoft Authenticode with supported software formats.
Other supported files
Verify the exact current format compatibility before publishing a specific claim.
How to Sign an EXE or MSI With Comodo EV Code Signing
Microsoft SignTool can be used to sign and verify supported Windows applications. The exact parameters depend on the certificate storage method and hardware configuration.
Release sequence: Build → Test → Sign → Timestamp → Verify → Release.
Why Timestamp Comodo EV Signed Software?
A timestamp records when the digital signature was created. This helps preserve the evidence associated with a signature after the Code Signing certificate itself expires, assuming the signature and applicable trust conditions remain valid.
Without relying only on certificate validity
A certificate has a finite validity period. A trusted timestamp provides an independent record of the signing event.
Recommended production practice
Use a trusted timestamp during signing rather than relying only on the certificate being active at the moment software is downloaded.
Supported Comodo Code Signing Formats
Historical Comodo documentation lists several major software signing environments. Exact compatibility should be verified against current Sectigo documentation before making a platform specific implementation promise.
Microsoft Authenticode
Windows software signing and common Authenticode workflows.
EXE, DLL, MSI and CAB
Common Windows application and installer formats.
OCX
Supported Windows object file signing.
Java
Supported Java signing workflows.
Adobe AIR
Supported AIR signing workflows.
Office Macro and VBA
Supported Microsoft Office signing scenarios.
Platform note: Historical Comodo materials also list Apple applications and plugins, Mozilla object files and Microsoft Silverlight. Verify current platform requirements before publishing a compatibility guarantee.
Does Comodo EV Code Signing Remove SmartScreen Warnings?
No. Do not make this a guarantee.
An EV Code Signing Certificate establishes publisher identity and software integrity, but it should not be marketed as a guaranteed way to eliminate Microsoft SmartScreen warnings. Older Comodo marketing discussed relationships between Code Signing and SmartScreen reputation, but current 2026 content should not turn those historical statements into a promise.
459 Days Maximum Certificate Validity
Current Sectigo rules limit newly issued Code Signing certificates to a maximum validity of 459 days. This applies to EV Code Signing as well as other current Code Signing certificates.
Do not reproduce older Comodo claims of three year or five year individual certificate validity as current issuance rules.
Multi Year Purchase Does Not Mean a Five Year Certificate
A multi year Code Signing purchase term should not be confused with the validity period of an individual certificate.
Current multi year model
- Individual certificates remain subject to the 459 day maximum.
- Certificates must be reissued during a multi year product term.
- Current remote provisioning requires customer generated keys on supported hardware.
- Key attestation is required for applicable current workflows.
Why older Comodo pages can be misleading
Older Comodo material promoted longer certificate periods and hardware token savings. Those historical claims no longer describe the current 2026 issuance model.
Comodo EV Code Signing for CI/CD
EV Code Signing can be integrated into an automated release process while keeping the private signing key protected. See how to integrate code signing into a software release process. The right architecture depends on whether the organization uses an HSM, managed signing infrastructure or another supported hardware based approach. Review the options for HSM code signing before choosing an implementation.
Security rule: automate the signing process without exposing the private signing key. Do not copy signing keys into source repositories, CI variables or ordinary server storage.
Comodo EV Code Signing With Centralized Signing
Organizations that sign software frequently may benefit from centralized certificate management and controlled signing infrastructure. Sectigo currently offers Code Signing capabilities through its Certificate Manager platform.
For enterprise release teams
- Centralized signing controls
- Controlled access to signing credentials
- HSM based signing infrastructure
- Automated certificate operations
- Repeatable CI/CD workflows
Certificate versus management platform
The Comodo EV Code Signing Certificate is the certificate used to sign software. Certificate Manager is the broader management and enterprise workflow platform. They should not be presented as competing products.
Comodo EV vs OV Code Signing
The major distinction is the level and depth of publisher validation. Both modern EV and OV workflows use protected signing keys under current Code Signing requirements.
| Feature | Comodo EV | Comodo OV |
|---|---|---|
| Validation | Extended Validation | Organization Validation |
| Publisher assurance | Higher | Standard organization validation |
| Official listed price | $829/year | $715/year |
| Hardware protected key | Yes | Yes |
| Non exportable private key | Yes | Yes |
| Windows Authenticode | Supported | Supported |
| Java signing | Supported | Supported |
| Timestamping | Supported | Supported |
| Validation requirements | More extensive | Less extensive |
| Best suited for | Higher assurance publishing requirements | Standard software publishing |
Do not simplify the choice to “EV is safer.” Both use protected signing keys. EV's primary distinction is the additional level of publisher validation.
Who Should Consider Comodo EV Code Signing?
EV can be relevant when a software organization needs stronger publisher identity assurance or a specific signing workflow requires Extended Validation. The code signing certificate selection guide can help compare requirements.
Software companies
Organizations distributing desktop applications, installers, libraries and other signed software.
Enterprise development teams
Teams that need controlled signing processes and stronger publisher validation.
Commercial software vendors
Vendors that distribute signed software directly to customers and partners.
Controlled release teams
Organizations with hardware backed signing and controlled release procedures.
EV specific workflows
Organizations whose security or platform workflow specifically calls for EV validation.
Driver related workflows
EV may be relevant where the applicable Microsoft driver signing requirements call for it.
Comodo EV Code Signing for Windows Drivers
EV Code Signing can be relevant to Windows driver signing workflows where Microsoft requires the applicable EV certificate and signing process.
Keep the claim specific
Do not state that every Windows driver requires Comodo EV. Verify the current Microsoft requirements for the specific driver type and distribution method before selecting a certificate.
Comodo EV Code Signing Specifications
| Specification | Details |
|---|---|
| Certificate type | Extended Validation Code Signing |
| Brand | Comodo |
| Current CA relationship | ComodoCA is now part of Sectigo |
| Primary purpose | Authenticate software publisher and protect code integrity |
| Validation level | Extended Validation |
| Applicant | Organization |
| Private key | Hardware protected and non exportable |
| Hardware | FIPS compliant token or supported HSM |
| Key attestation | Required for applicable current issuance workflows |
| EV price | $829/year |
| Current official EV price | $829/year |
| Current official OV price | $715/year |
| Maximum certificate validity | 459 days |
| Signing formats | Authenticode, Java, Adobe AIR and other supported formats |
| Timestamping | Supported |
| Windows signing | Supported |
Does EV Code Signing Guarantee SmartScreen Approval?
No
An EV certificate should not be marketed as a guaranteed SmartScreen bypass. Microsoft reputation systems can consider multiple signals, and possession of an EV certificate does not guarantee that every download will be free of warnings.
Is Comodo EV Code Signing Still Available?
Sectigo officially states that ComodoCA is now Sectigo and that ComodoCA products and services remain available through the Sectigo ecosystem.
What this means for buyers
If you specifically search for a Comodo EV Code Signing Certificate, verify the current availability, purchasing route, price, hardware option and issuance method through the current Sectigo or Comodo channel.
What to avoid
Do not rely on an old Comodo product page for current price, validity or issuance claims. The 2026 Code Signing model has materially changed.
Comodo EV Code Signing FAQs
What is a Comodo EV Code Signing Certificate?
It is an Extended Validation Code Signing certificate designed to provide stronger assurance about the identity of a software publisher and authenticate digitally signed software.
Is Comodo EV Code Signing now part of Sectigo?
Yes. ComodoCA has been unified under Sectigo, while ComodoCA products remain accessible through the Sectigo ecosystem.
How much does Comodo EV Code Signing cost?
Sectigo’s official website currently lists EV Code Signing at $829/year and OV Code Signing at $715/year. Check the official product page for the latest price and purchase terms.
Is the old $647 Comodo price still current?
No. The $647 figure comes from older Comodo material and should not be presented as a verified 2026 EV purchase price.
Does Comodo EV Code Signing require a hardware token?
Current Code Signing requirements require protected private key storage in suitable hardware. Supported workflows can use a compatible hardware token or supported HSM.
Can I use an HSM with Comodo EV Code Signing?
Yes. Supported HSM based workflows can protect the private signing key and support centralized signing infrastructure.
Can I export the Comodo EV private key?
No. The modern Code Signing model is designed so the private signing key is generated and protected inside suitable hardware and is not exportable.
What is key attestation?
Key attestation provides evidence that the private key was generated inside the hardware and cannot be exported.
Can I sign EXE and MSI files?
Yes. EV Code Signing can be used with Microsoft Authenticode, and current Sectigo documentation provides SignTool workflows for supported EXE and MSI signing.
Does Comodo EV Code Signing guarantee that SmartScreen will not show a warning?
No. EV should not be treated as a guarantee of SmartScreen approval or the absence of warnings.
How long is a Comodo EV Code Signing certificate valid?
Under current Sectigo rules, newly issued Code Signing certificates have a maximum validity of 459 days.
Can I buy a multi year Comodo Code Signing product?
A multi year product term can exist, but individual certificates remain subject to the current 459 day maximum and must be reissued during the purchased term.
Does Comodo EV Code Signing support timestamping?
Yes. Comodo's published Code Signing documentation includes timestamp functionality, and timestamping is recommended for production signing.
Is Comodo EV better than Comodo OV?
EV provides a higher level of publisher identity assurance and requires more extensive validation. OV can be sufficient when those additional validation requirements are not needed.
Can Comodo EV Code Signing be used in CI/CD?
Yes. Organizations can integrate protected signing into automated release pipelines using suitable HSM or supported signing infrastructure.
Compare EV and OV Before You Choose
If your workflow does not require Extended Validation, compare the validation requirements and protected-key options for Comodo OV Code Signing before making a purchase decision.
Compare Comodo OV Code Signing