Sectigo OV Code Signing Certificate
Verify the organization behind your software while protecting the signing key with compliant hardware. Sectigo OV Code Signing is designed for software publishers that need verified publisher identity without the EV validation model.
Check Current Sectigo PricingSectigo currently displays OV Code Signing at $715 per year. Confirm the final price and purchase terms on the official page before ordering.
What Is Sectigo OV Code Signing?
Sectigo OV Code Signing is an Organization Validation certificate for software publishers. Sectigo's current validation documentation describes OV Code Signing as its non EV Code Signing certificate and explains that the validation process verifies the identity of the software publisher and organization behind the certificate.
Verified software publisher
A Code Signing signature helps users establish who signed software and whether the signed content has been modified after signing. OV adds verified organization identity to that signing process.
It is relevant to software companies, independent software vendors, SaaS businesses distributing desktop applications or installers, and developers publishing software under an organization.
Current hardware based signing
Modern Code Signing provisioning requires the private signing key to be protected by compliant hardware. Sectigo supports a supplied hardware token and customer controlled HSM configurations that meet the applicable requirements.
This means the current workflow should not be treated like older certificate processes where a private key could simply be downloaded as a PFX file.
What You Get With Sectigo OV
The value of OV is not just the certificate itself. The current product combines organization validation, protected private key handling and support for common software signing workflows.
Organization Validation
Sectigo verifies information about the organization requesting the certificate before issuing the OV Code Signing certificate.
Hardware Token Option
Sectigo can provision the Code Signing certificate onto a supplied hardware token for controlled workstation based signing.
Customer HSM Support
Organizations can use their own supported HSM when it satisfies Sectigo's requirements for protected key storage and attestation.
Key Attestation
Hardware generated key attestation provides evidence that the private key was generated inside approved hardware and cannot be exported.
Timestamping
Timestamping is supported as part of software signing workflows and helps preserve the verifiability of signatures beyond certificate expiration.
CI/CD Support
HSM based signing can be incorporated into automated release environments where the signing infrastructure is configured appropriately.
Current Sectigo OV Code Signing Price
Sectigo currently displays OV Code Signing at $715 per year and EV Code Signing at $829 per year on its public pricing page.
| Pricing detail | Current information |
|---|---|
| Product | Sectigo Code Signing, including OV Code Signing |
| Validation model | Organization Validation |
| Displayed annual price | $715/year |
| Price basis | Five year purchase option |
| Shorter purchase terms | Higher price |
| EV Code Signing | Higher price than the published OV starting price |
| Maximum individual certificate validity | 459 days |
| Multi year purchase | Available subject to current provisioning and reissuance requirements |
Important: $715/year is the annual price currently displayed on Sectigo’s public pricing page. Confirm the displayed annual price and purchase terms on Sectigo’s official page before ordering.
Hardware Token or Customer HSM?
The right option depends on how and where your organization signs software.
Sectigo supplied hardware token
Sectigo can provision the Code Signing certificate onto a physical token and ship it securely to the customer. This approach fits organizations where signing is performed from a controlled workstation.
A token can be straightforward for a smaller signing operation, but physical hardware can become less convenient when builds and releases happen automatically across multiple environments.
Customer controlled HSM
Organizations can use a supported HSM when the device meets Sectigo's applicable requirements, including FIPS compliance and externally verifiable key attestation.
This approach is more relevant to enterprise software teams, centralized signing infrastructure, automated release environments, CI/CD pipelines and organizations that already operate HSM infrastructure.
459 Days Maximum Certificate Validity
Sectigo began enforcing a maximum Code Signing certificate validity of 459 days from February 23, 2026. This is important when explaining Sectigo's multi year purchase options.
A multi year purchase term does not mean that a single certificate remains valid for five years.
Five Year Purchase Term Does Not Mean Five Year Certificate Validity
This distinction is important for buyers comparing current Code Signing products. Sectigo continues to offer multi year Code Signing as a product term, while individual certificates must be reissued during that term according to the current validity requirements.
What remains available
- One year Code Signing remains available through the current delivery method.
- Multi year Code Signing continues as a product term.
- New multi year remote provisioning uses customer generated keys.
- The signing device must be supported.
- Key attestation is required.
What changed
Sectigo provisioned token based multi year orders were discontinued for new orders after February 15, 2026. Current multi year workflows therefore need to be described using the newer provisioning and reissuance model rather than as one five year certificate.
Compare OV and EV Before Choosing
Review the validation differences and choose the certificate type that matches your software distribution and signing requirements.
Compare OV and EV Code SigningHow Sectigo OV Validation Works
The validation process is intended to confirm the organization requesting the Code Signing certificate. The exact time can vary when additional verification is required, so the product page should not promise a fixed issuance time.
Sectigo OV Code Signing Specifications
| Specification | Details |
|---|---|
| Certificate type | OV Code Signing |
| Validation | Organization Validation |
| Also called | Non EV Code Signing |
| Displayed annual price | $715/year, as displayed per year |
| Private key | Hardware protected |
| Token | Sectigo supplied token option |
| HSM | Customer HSM supported when requirements are met |
| Key attestation | Required for applicable hardware provisioning |
| Maximum certificate validity | 459 days |
| Timestamping | Supported |
| CI/CD | Supported with suitable signing infrastructure |
What Can You Sign With Sectigo OV?
Sectigo positions its Code Signing certificates for software and code signing across multiple environments. The exact implementation depends on the signing tool and protected key infrastructure.
Windows applications
Sign supported Windows executables and applications using Microsoft Authenticode workflows.
Installers
Sign software installers so users can verify the publisher and software integrity.
Java
Use the certificate in supported Java signing workflows.
PowerShell
Sign supported PowerShell scripts as part of your software or administration workflow.
Office and VBA
Use supported Code Signing workflows for Microsoft Office macros and VBA.
CI/CD releases
Integrate protected signing into automated software release pipelines using suitable token or HSM infrastructure.
Sectigo OV Code Signing for CI/CD
A physical token can become inconvenient when software is built and released automatically. For automated environments, an HSM based configuration can provide controlled access to the signing key while keeping the private key inside protected hardware.
For larger organizations, Sectigo also provides Code Signing capabilities through Sectigo Certificate Manager, which can support centralized certificate management and automation.
Sectigo OV vs EV Code Signing
Both models provide organization identity and hardware protected key options. The primary difference is the validation level and the circumstances in which EV is required.
| Feature | Sectigo OV | Sectigo EV |
|---|---|---|
| Organization validation | Yes | Yes |
| EV validation | No | Yes |
| Publisher identity | Yes | Yes |
| Hardware protected key | Yes | Yes |
| Token option | Yes | Yes |
| HSM option | Yes | Yes |
| Maximum validity | 459 days | 459 days |
| General software signing | Yes | Yes |
| Higher validation level | No | Yes |
| Displayed annual price | $715/year | Higher than OV |
Does Sectigo OV Code Signing Remove SmartScreen Warnings?
No guarantee should be made.
Code Signing establishes publisher identity and helps verify software integrity. It should not be marketed as an automatic way to remove Microsoft SmartScreen warnings. SmartScreen reputation involves additional factors beyond certificate validation.
Who Should Choose Sectigo OV?
OV is generally appropriate when the software is distributed under an organization and verified publisher identity is required without a specific EV requirement.
Software companies
Distribute applications under a verified company identity.
Independent software vendors
Associate software releases with the verified organization behind the product.
SaaS companies
Sign desktop applications, agents, utilities or installers that complement SaaS products.
Enterprise software teams
Integrate OV signing with existing HSM infrastructure and centralized release processes.
Organization developers
Publish software under an organization's verified identity rather than an individual's name.
Teams without EV requirements
Choose OV when a higher EV validation level is not required by the workflow.
When EV May Be More Appropriate
- Your organization specifically requires EV validation.
- Your software platform or signing workflow has an EV requirement.
- You have a Windows driver signing workflow with applicable EV requirements.
- Your internal security or procurement policy requires EV.
OV Is Not a Lower Quality Version of EV
Do not choose EV simply because it sounds more secure. The correct choice depends on the actual validation and signing requirements of your software, release environment and internal policies.
Sectigo OV Certificate vs Sectigo Certificate Manager
Sectigo OV Code Signing Certificate
This is the certificate used to sign software. Its purpose is to establish the verified publisher identity and support software integrity verification.
Sectigo Certificate Manager
This is the broader certificate management platform. Sectigo states that Code Signing certificates can be managed through Certificate Manager for organizational scale, management and automation.
Sectigo OV Code Signing FAQs
What is a Sectigo OV Code Signing Certificate?
It is an Organization Validation Code Signing certificate that verifies the identity of the software publisher and helps users verify software integrity. Sectigo also refers to OV Code Signing as non EV Code Signing.
How much does Sectigo OV Code Signing cost?
Sectigo currently displays OV Code Signing at $715 per year and EV Code Signing at $829 per year. Confirm the final price and purchase terms on the official page before ordering.
Is $715 the displayed annual price?
Sectigo currently displays OV Code Signing at $715 per year. Confirm the final price and purchase terms on the official page before ordering.
Does Sectigo OV Code Signing require a hardware protected key?
Yes. Current Code Signing requirements require private keys to be protected using compliant hardware. Sectigo supports its supplied token and customer HSM configurations.
Can I use my own HSM?
Yes. Sectigo supports Code Signing certificates installed on customer HSMs when the hardware meets its requirements, including FIPS compliance and externally verifiable key attestation.
What is key attestation?
Key attestation is evidence generated by the hardware that proves the private key was created inside the HSM or token and cannot be exported.
How long is a Sectigo OV Code Signing Certificate valid?
New Sectigo Code Signing certificates have a maximum validity of 459 days under the rules Sectigo began enforcing on February 23, 2026.
Can I purchase a multi year Sectigo Code Signing term?
Yes. Sectigo continues to offer multi year Code Signing as a product term, but individual certificates must be reissued during the term because each certificate is limited by current validity requirements.
Is Sectigo OV the same as EV Code Signing?
No. OV uses Organization Validation, while EV uses Extended Validation and requires a higher level of validation.
Does Sectigo OV Code Signing remove SmartScreen warnings?
No certificate should be presented as a guaranteed SmartScreen bypass. Windows reputation systems use additional signals beyond certificate validation.
Can Sectigo OV Code Signing be used for CI/CD?
Yes. Sectigo supports Code Signing in automated environments, and HSM based provisioning can be used where appropriate. Sectigo also provides Code Signing management and automation through Certificate Manager.
What is the difference between a multi year term and certificate validity?
A multi year purchase is a product term. It does not mean that one individual certificate is valid for the entire term. Individual certificates are limited to the current maximum validity period and may need to be reissued during the purchased term.
Review Sectigo OV Before You Buy
Check the current Sectigo price, purchase term, validation requirements and key protection options before selecting an OV Code Signing configuration for your software release process.
Choose the Right Code Signing Certificate