Comodo OV Code Signing Certificate
Authenticate your software publisher identity and protect signed files against unauthorized modification with Organization Validation code signing.
ComodoCA is now part of Sectigo. The Comodo product name therefore needs to be understood alongside the current Sectigo issuance ecosystem rather than as a separate independent certificate authority.
Sectigo's official Code Signing page displays $715 per year for OV and $829 per year for EV. Confirm the selected purchase term and current checkout total before ordering.
View Official Sectigo PricingComodo OV Code Signing Certificate at a Glance
The certificate is designed for software publishers that need verified publisher identity and protected signing keys across supported software distribution workflows.
What Is a Comodo OV Code Signing Certificate?
An OV Code Signing Certificate digitally associates a software publisher's verified identity with a digital signature applied to software.
Publisher identity
The signature identifies the organization or eligible individual represented by the certificate. Current Sectigo OV documentation describes validation for eligible individuals, private organizations, registered businesses, government entities and international entities.
Code integrity
The signature helps users and software platforms verify that signed content has not been modified after signing. The certificate provides the identity context while the protected private key creates the signature.
How Comodo OV Code Signing Works
The signing model combines the software hash, protected private key, certificate identity and trusted timestamp.
During signing
The publisher uses the protected private key to create a digital signature. The certificate associates that signature with the verified publisher identity.
During verification
The operating system or signing tool checks the signature, certificate chain and integrity of the signed file. If the signed content changes after signing, the integrity check can detect the modification.
Comodo OV Code Signing Certificate Validation
OV validation verifies information associated with the software publisher before the certificate is issued.
Publisher identity
The applicant's identity is validated as part of the issuance process.
Physical presence and contact
Validation checks relevant presence and contact information for the applicant.
Request authorization
The certificate request must be authorized by the appropriate party.
Subscriber Agreement
The appropriate party must approve the applicable Subscriber Agreement.
Baseline requirements
The validation framework follows the CA/Browser Forum Code Signing Baseline Requirements.
OV positioning
OV provides verified publisher identity without the additional validation requirements associated with EV Code Signing.
Hardware Protected Private Key
Modern code signing should not be treated like an ordinary SSL workflow where a private key is simply downloaded and stored in an exportable software file.
Hardware token
A physical USB token can hold the signing certificate and private key. The signer connects the token when signing software and authenticates using the token credentials.
Customer controlled HSM
Organizations with their own signing infrastructure can use a supported Hardware Security Module to generate and protect the private key.
Managed signing infrastructure
Larger signing teams can use certificate management infrastructure to control certificate enrollment, users and signing workflows.
Key attestation
Key attestation provides evidence that the private key was generated inside the supported HSM or token and cannot be exported from it.
Supported Software and File Types
Published Comodo code signing material lists support for several major software signing formats. Exact current platform compatibility should be verified with the current Sectigo documentation before purchase.
- Microsoft Authenticode
- EXE, DLL, MSI, CAB and OCX
- Java applications
- Adobe AIR
- Apple applications and plug ins
- Microsoft Office Macro and VBA
- Mozilla object files
- Microsoft Silverlight applications
Comodo OV Code Signing for Windows
Windows software is a primary use case for code signing. An OV certificate can be used with Microsoft Authenticode tooling such as SignTool for supported binaries.
Typical Windows release workflow
Build the application, access the signing key through compliant hardware, sign the executable or installer, apply a trusted timestamp, verify the signature and then distribute the signed software. Sectigo documents SignTool workflows for Microsoft Authenticode signing, the format commonly used to sign supported Windows binaries.
Timestamping
A trusted timestamp records when a signature was created. This can allow the signature to remain useful after the certificate itself expires, provided the certificate was valid when the signature was created and the relevant trust chain remains valid.
For production releases, use trusted timestamping to record when a signature was created, helping preserve its validity after the signing certificate expires when the certificate was valid at signing time and the relevant trust chain remains valid.
CI/CD Signing
Code signing can be integrated into a controlled release pipeline rather than being performed manually on individual developer machines.
Build → Test → Security checks → Signing → Timestamping → Signature verification → Release
Larger development teams can integrate code signing into a controlled CI/CD pipeline to automate software releases while keeping private keys protected and signing permissions under control.
Comodo OV Code Signing vs EV Code Signing
Both certificate types are intended for signed software, but EV applies a higher validation level. The OV versus EV comparison can help buyers decide whether that additional assurance fits their distribution and compliance requirements.
| Feature | Comodo OV | Comodo EV |
|---|---|---|
| Validation level | Organization Validation | Extended Validation |
| Publisher identity verification | Yes | Higher assurance |
| Hardware protected key | Required | Required |
| Software distribution | Yes | Yes |
| Windows signing | Yes | Yes |
| Java signing | Yes | Yes |
| Authenticode | Yes | Yes |
| Timestamping | Supported | Supported |
| Validation burden | Lower | Higher |
| Best for | Standard software publishing | Higher assurance publishing requirements |
| Displayed annual price | $715/year | $829/year |
Current Comodo Pricing
Sectigo's official Code Signing page currently displays the following annual prices for its OV and EV Code Signing certificates.
These are the prices visible on Sectigo's official Code Signing page. Since this page covers the Comodo branded OV product, confirm the exact product name, purchase term and checkout total on Sectigo's current listing before ordering.
Who Should Use Comodo OV Code Signing?
OV is relevant when software needs a verified publisher identity and protected signing infrastructure without the additional validation burden associated with EV.
Software companies
Sign desktop applications, installers, libraries and other distributable software with a verified publisher identity.
Independent developers
Authenticate software releases under an eligible individual or business identity where supported.
Enterprise development teams
Protect signing keys with compliant hardware and integrate signing into controlled release processes.
B2B software vendors
Give customers verifiable publisher information before they install or execute software.
Development and DevOps teams
Use hardware protected signing infrastructure as part of a controlled software release pipeline.
Is Comodo OV Code Signing Still Relevant?
Yes, but the branding needs to be explained correctly. ComodoCA is no longer positioned as a separate independent CA from Sectigo.
What has changed
Sectigo states that ComodoCA is now Sectigo and that ComodoCA products continue to be available through its ecosystem.
What buyers should evaluate
Focus on the current issuance process, hardware requirements, validity rules, pricing and support instead of relying on older Comodo product descriptions.
Frequently Asked Questions
What is Comodo OV Code Signing Certificate?
It is an Organization Validation Code Signing certificate used to authenticate software publishers and protect signed software against unauthorized modification.
Is Comodo Code Signing now owned by Sectigo?
ComodoCA has been unified under the Sectigo brand. Sectigo states that ComodoCA products and services continue to be available through the Sectigo ecosystem.
Can I use Comodo OV Code Signing for Windows software?
Yes. Comodo Code Signing has supported Microsoft Authenticode, including Windows executable formats. Current signing workflows should be checked against the latest Sectigo documentation.
Does Comodo OV Code Signing require a hardware token?
Current Code Signing requirements require the private key to be protected using suitable hardware. Depending on the issuance workflow, this can involve a hardware token or supported HSM.
Can I export the private key?
The private signing key is intended to remain protected within compliant hardware and should not be treated like an ordinary exportable software private key.
Does an OV certificate remove SmartScreen warnings?
No. A valid Code Signing certificate does not guarantee that Microsoft SmartScreen will stop displaying warnings. Reputation and other Microsoft security signals are separate considerations.
Does Comodo OV Code Signing support Java?
Comodo's published Code Signing documentation lists Java among its supported signing formats. Verify the current platform workflow before purchase.
Should I choose Comodo OV or EV?
Choose OV when standard publisher validation and code integrity protection meet your requirements. Consider EV when your distribution or compliance requirements call for the higher validation level.
Where can I buy a Comodo OV Code Signing Certificate?
Because ComodoCA is now part of Sectigo, current availability and purchasing options should be checked through the current Sectigo/Comodo channel rather than relying on old third party listings.
Check the Current Comodo Code Signing Offering
Comodo branded code signing should be evaluated through the current Sectigo ecosystem. Confirm current pricing, issuance options, hardware requirements and availability before purchasing.
Visit the Current Sectigo Comodo Channel