HARICA Code Signing Certificates

Compare HARICA IV, OV and EV Code Signing Certificates based on who is signing the software, what identity needs to be validated and how the private signing key must be protected.

IV for Individuals OV for Organizations EV for Organizations CertManager Hardware & HSM

IV
Individuals and sole proprietors

OV
Enterprises and organizations

EV
Organizations requiring Extended Validation

HARICA's current documentation provides separate enrollment workflows for all three certificate types.

Visit HARICA

Three HARICA Certificates for Three Applicant Types

HARICA separates Code Signing primarily by the identity being validated. IV is designed for individuals and sole proprietorships, while OV and EV are intended for enterprises and organizations.

HARICA IV Code Signing

Designed for individual developers and sole proprietors who need software signed under a verified personal identity.

Explore HARICA IV Code Signing

HARICA OV Code Signing

Designed for software companies and organizations that need their organizational identity associated with digitally signed software.

Explore HARICA OV Code Signing

HARICA EV Code Signing

Designed for enterprises and organizations that specifically require the Extended Validation certificate profile.

Explore HARICA EV Code Signing

HARICA Code Signing Certificate Comparison

The product choice becomes straightforward when the applicant identity and validation requirement are defined first. Teams unsure which validation level fits their situation can use the code signing certificate selection guide to compare their requirements.

Feature	HARICA IV	HARICA OV	HARICA EV
Validation	Individual	Organization	Extended Validation
Individuals	Yes	No	No
Sole proprietors	Yes	No	No
Organizations	No	Yes	Yes
Personal identity validation	Yes	No	No
Organization validation	No	Yes	Yes
EV validation	No	No	Yes
Code Signing	Yes	Yes	Yes
Protected private key	Required	Required	Required
Hardware device	Supported	Supported	Supported
HSM	Supported	Supported	Supported
CertManager enrollment	Yes	Yes	Yes

Compare Certificate Validation Levels

Review the differences between certificate types before deciding which validation level matches your publisher identity and release requirements.

Compare Code Signing Certificates

HARICA Code Signing Pricing

HARICA's current support information directs customers to CertManager and its sales team for product information and pricing. Because the supplied research does not provide a verified public fixed price, this hub deliberately avoids publishing an estimated price.

Pricing should be checked directly through HARICA CertManager or HARICA sales.

This avoids publishing outdated third party pricing when the actual purchase price or delivery model may change.

Review the Certificate Buying Process

Before requesting a quote, confirm who will be named as the publisher, how the signing key will be protected and which certificate profile your release process requires.

Read the Buying Guide

Private Key Protection Is Part of the Product Decision

HARICA's Code Signing model places strong emphasis on protected private key storage. This is also a core consideration when signing software without exposing the private key. Hardware and HSM based protection are important across the product range, not only for EV.

Hardware protection

HARICA's enrollment workflows provide a hardware device option. The cryptographic device can be prepared and sent to the applicant's physical address, after which the issued certificate can be imported into the compatible token management environment.

HSM protection

HARICA recognizes HSM based key protection as part of its Code Signing security model, making it relevant to organizations with controlled enterprise signing infrastructure.

Non EV keys also require protected storage.

HARICA states that since June 1, 2023, private keys for its non EV Code Signing certificates must be protected using cryptographic devices or HSMs meeting at least FIPS 140 2 Level 2 or Common Criteria EAL 4+ requirements.

HARICA IV Enrollment for Individuals and Sole Proprietors

IV is the product category for applicants who need a Code Signing identity tied to an individual rather than a registered organization.

Identity verification

The applicant's personal information must match the government issued identification document. HARICA's current enrollment process also requires identification and address verification documents and provides authorization methods for completing validation.

Who it fits

IV is relevant to independent software developers, sole proprietors, individual application publishers and developers distributing signed software under their personal identity.

HARICA OV for Software Companies and Organizations

OV is designed for organizations that need their organizational identity associated with digitally signed software without selecting the EV certificate profile.

Organizational identity

HARICA provides a dedicated OV enrollment workflow through CertManager for enterprises and organizations.

Commercial software

OV is relevant to software companies, ISVs, enterprises and development teams publishing commercial software under an organizational identity.

The HARICA OV product page above covers the organization validation enrollment path.

HARICA EV for Organizations Requiring Extended Validation

EV is intended for enterprises and organizations that specifically require the Extended Validation level and its associated validation process.

Dedicated EV enrollment

HARICA provides a separate EV enrollment process through CertManager. This keeps the EV workflow distinct from the IV and OV application paths.

The HARICA EV product page above covers the Extended Validation enrollment path.

Code Signing Across Windows and Java

HARICA describes Code Signing as a way to authenticate applications, drivers, executables and software programs, including software executed on Windows and Java environments.

Windows software

Supported signing targets can include applications, drivers, executables and other software. A typical release flow is:

BuildTestSignTimestampVerifyRelease

Java software

HARICA also identifies Java software as a Code Signing use case. Teams packaging Java applications can follow the technical steps for signing Java JAR files. The appropriate signing process should be selected according to the Java packaging format and signing tool being used.

Timestamp Every Production Signature

Timestamping is an important part of a long term signing strategy because it records the signing time and can allow signed code to remain verifiable after certificate expiration or revocation, subject to the applicable trust conditions. A production workflow should timestamp signed software as part of the signing process.

Sign → Timestamp → Verify

HARICA's Code Signing best practices recommend timestamping signed code. Treat timestamping as part of the production signing process rather than an optional final step.

HARICA Code Signing Lifecycle

A controlled signing lifecycle connects identity validation, protected key creation and software release into one repeatable process.

Certificate Request Identity Validation Key Generation Certificate Issuance Software Signing Timestamping Verification Renewal or Replacement

HARICA's current enrollment process illustrates this lifecycle through CertManager registration, identity verification, payment, validation, certificate acceptance and certificate import. OV and EV follow the same general structure with applicant specific validation requirements.

HARICA Code Signing for CI/CD

Automated software releases should keep the private signing key outside ordinary build systems. HARICA's security guidance emphasizes minimizing access to signing keys and using cryptographic hardware to prevent private key export.

Source → Build → Automated Tests → Security Checks → Protected Signing Key → Sign → Timestamp → Verify → Release

For organizations automating signing, design the signing infrastructure around protected hardware or HSM based key storage rather than exporting private keys into CI/CD servers. A dedicated automated code signing workflow for CI/CD can help make these controls repeatable.

HARICA Code Signing Security Practices

Private key security is one of the most important operational responsibilities in Code Signing. HARICA recommends controls that reduce unnecessary access and protect signing credentials from export.

Limit key access

Minimize access to private keys and restrict the number of users who can use signing credentials.

Use cryptographic hardware

Protect Code Signing keys with appropriate physical security controls and cryptographic hardware.

Control signing approval

Establish policies that define who can approve and perform production signing operations.

HARICA Certificate Replacement and Rekeying

Replacement procedures can differ between non EV and EV certificates, particularly when determining whether existing key material can be reused.

Non EV replacement

HARICA can rekey and issue a new certificate using newly generated key material for non EV Code Signing scenarios.

EV replacement

HARICA documents several EV replacement scenarios, including reuse of an existing key pair when the private key has not been compromised or generation of a new key pair.

Which HARICA Certificate Should You Choose?

Choose HARICA IV

Choose IV if you are an individual developer or sole proprietor and want the certificate associated with your verified personal identity.

Choose HARICA OV

Choose OV if your software is published by a registered organization and you need organization validation without the additional EV validation level.

Choose HARICA EV

Choose EV if your organization specifically requires Extended Validation and the associated higher assurance validation process.

Frequently Asked Questions

What Code Signing certificates does HARICA offer?

HARICA currently offers IV, OV and EV Code Signing certificates. IV is for individuals or sole proprietorships, while OV and EV are available for enterprises and organizations.

What is HARICA IV Code Signing?

HARICA IV Code Signing is designed for individuals and sole proprietorships. The enrollment process validates the individual's identity using identification and address verification documents.

What is HARICA OV Code Signing?

HARICA OV Code Signing is intended for enterprises and organizations that need Organization Validation for their software signing identity.

What is HARICA EV Code Signing?

HARICA EV Code Signing is designed for enterprises and organizations that require Extended Validation. HARICA provides a dedicated EV enrollment process through CertManager.

Does HARICA require hardware protection for Code Signing keys?

Yes. HARICA requires protected key storage for Code Signing and states that non EV Code Signing private keys must be protected using suitable cryptographic hardware or HSMs meeting the applicable security standards.

Can HARICA provide the cryptographic device?

Yes. HARICA's current enrollment guides state that applicants can select the hardware device option, after which HARICA prepares and sends the cryptographic device to the applicant's physical address.

Can HARICA Code Signing be used for software and drivers?

Yes. HARICA describes Code Signing certificates as being used for applications, drivers, executables and software programs.

Does HARICA support Java Code Signing?

Yes. HARICA identifies Java software among the Code Signing use cases supported by its certificates.

Does HARICA support timestamping?

Yes. HARICA recommends timestamping signed code and explains that timestamping can allow signed code to remain verifiable after certificate expiration or revocation, subject to applicable trust conditions.

How much does HARICA Code Signing cost?

HARICA's current customer support information directs customers to CertManager and its sales team for product information and pricing. This hub therefore does not publish an unverified fixed price.

Can HARICA Code Signing certificates be purchased online?

Yes. HARICA states that IV, OV and EV Code Signing certificates can be purchased directly through its CertManager platform.

Choose the HARICA Certificate Around Your Identity

IV is for individuals and sole proprietors. OV is for enterprises and organizations. EV is for organizations requiring Extended Validation. Once the certificate type is selected, build the signing process around protected hardware or HSM based key storage.

Visit HARICA