IdenTrust Code Signing Certificates

Compare IdenTrust Code Signing and EV Code Signing certificates, including current pricing, validation, hardware protection, supported platforms and signing features.

Organization Identity EV Code Signing Hardware Token HSM RFC 3161 Timestamping
IdenTrust Code Signing
Standard organization identity
$225
IdenTrust EV Code Signing
Extended Validation
$281
SafeNet USB Token
Optional storage device
$100

Certificate prices are shown separately from optional hardware, shipping and applicable taxes.

View IdenTrust Certificate Details

Two IdenTrust Code Signing Options

IdenTrust's current TrustID range includes a standard Code Signing certificate for organization identity and an EV Code Signing certificate for organizations that need additional validation and a higher level of identity assurance.

STANDARD CODE SIGNING

IdenTrust Code Signing Certificate

Designed for software developers and organizations that create and distribute applications and executable code. It validates the relationship between the certificate holder and the business organization.

$225 / 1 year
Current certificate price

Explore IdenTrust Code Signing Certificate

EXTENDED VALIDATION

IdenTrust EV Code Signing Certificate

Provides an enhanced level of identity assurance and requires additional business operations validation beyond the standard Code Signing certificate.

$281 / 1 year
Current certificate price

Explore IdenTrust EV Code Signing Certificate

IdenTrust Code Signing vs EV Code Signing

Both products are intended for organizational software signing. The key difference is the validation level and the additional requirements associated with Extended Validation.

FeatureIdenTrust Code SigningIdenTrust EV Code Signing
Organization identityYesYes
Validation levelStandard Code SigningExtended Validation
Current 1 year price$225$281
Hardware tokenYesYes
HSM storageYesYes
Private key hardware protectionYesYes
Microsoft AuthenticodeYesYes
JavaYesYes
Adobe AIRYesYes
Apple code signingSupported formats listed by IdenTrustSupported formats listed by IdenTrust
TimestampingFree RFC 3161 serviceFree RFC 3161 service
Best suited forStandard organizational software signingHigher assurance organizational signing

Why Software Publishers Use IdenTrust Code Signing

01

Establish publisher identity

The certificate establishes the identity of the organization associated with signed software.

02

Protect software integrity

Digital signatures help recipients determine whether signed code has been modified after it was signed.

03

Support production releases

Code Signing can be incorporated into controlled software release processes for applications, executable code and other supported formats.

Supported Software and Signing Environments

IdenTrust lists a broad range of software and code signing environments. The supported formats vary by platform and signing workflow.

EXE
DLL
MSI
CAB
OCX
Java
Adobe AIR
Apple
Microsoft Office
Firmware & Drivers

IdenTrust specifically identifies Microsoft Authenticode formats including EXE, DLL, CAB, OCX and MSI. It also lists Java, Adobe AIR, Apple, Microsoft Office, firmware and drivers among supported environments or use cases.

Choose How Your Signing Key Is Protected

IdenTrust's Code Signing offering supports hardware based private key protection. Organizations can use a supported hardware token for workstation based signing or their own compliant HSM for centralized signing infrastructure.

OPTION A

Hardware Token

A supported USB token protects the certificate and private key. This approach can suit developers or release engineers who need to sign software from individual workstations.

+$100
SafeNet USB Token when a new storage device is required
OPTION B

HSM

Organizations with centralized signing infrastructure can use their own compliant HSM to generate and protect signing keys. This approach fits controlled enterprise signing environments.

Hardware Requirements for the Signing Key

Private key protection of the current Code Signing model. IdenTrust specifies compliant hardware storage for its standard organization identity Code Signing product.

COMPLIANT HARDWARE

FIPS 140-2 Level 2

IdenTrust specifies storage on hardware meeting FIPS 140-2 Level 2 or Common Criteria EAL 4+ requirements for its standard Code Signing certificate.

CENTRALIZED INFRASTRUCTURE

Common Criteria EAL 4+

Organizations can also use their own compliant HSM to generate and protect private signing keys for controlled signing environments.

Free RFC 3161 Timestamping

IdenTrust provides a free RFC 3161 compliant timestamping service with its Code Signing certificates. Timestamping records evidence of when a signature was created and supports long term validation of signed code.

Why timestamping matters

Certificate validity and signature validity are not the same thing. A properly timestamped signature can remain verifiable after the signing certificate expires, subject to the applicable trust and revocation rules.

Current IdenTrust Code Signing Prices

IdenTrust currently publishes separate certificate prices for its standard Code Signing and EV Code Signing products. The optional SafeNet USB Token is listed separately when a new storage device is required.

ProductValidityCurrent price
IdenTrust Code Signing1 year$225
IdenTrust EV Code Signing1 year$281
SafeNet USB TokenOptional$100
Budget separately for hardware and additional charges.

The published $225 and $281 figures are certificate prices. Hardware, shipping and applicable taxes should be considered separately.

IdenTrust Certificate Validity in 2026

365 DAY MAXIMUM

Current certificate validity is one year

IdenTrust announced that effective February 26, 2026, the maximum validity period for its Code Signing certificates was reduced to 365 days to align with CA/Browser Forum requirements.

For this reason, the IdenTrust hub should not describe these products as multi year Code Signing certificates.

Which IdenTrust Certificate Should You Choose?

STANDARD ORGANIZATIONAL SIGNING

Choose IdenTrust Code Signing

Choose the standard certificate when your organization needs to establish its identity while distributing software and does not require the additional validation level of EV.

HIGHER ASSURANCE

Choose IdenTrust EV Code Signing

Choose EV when your organization specifically requires the higher validation level associated with EV Code Signing or has a workflow that calls for EV.

The decision should consider your software platform, distribution model, signing infrastructure and applicable platform requirements rather than assuming EV is always necessary.

IdenTrust Code Signing FAQ

What is an IdenTrust Code Signing Certificate?

An IdenTrust Code Signing Certificate is used to digitally sign software and establish the identity of the organization associated with the signed code. It also helps recipients verify that signed code has not been modified after signing.

How much does an IdenTrust Code Signing Certificate cost?

The current published price is $225 for 1 year for the standard IdenTrust Code Signing certificate.

How much does an IdenTrust EV Code Signing Certificate cost?

The current published price is $281 for 1 year for IdenTrust EV Code Signing.

What is the difference between IdenTrust Code Signing and EV Code Signing?

The standard certificate provides organization identity validation for Code Signing, while EV Code Signing applies additional validation requirements and provides a higher level of identity assurance.

Does IdenTrust support hardware tokens?

Yes. IdenTrust supports hardware token storage. Its current store lists a SafeNet USB Token as an optional $100 purchase when a new token is needed.

Can IdenTrust Code Signing use an HSM?

Yes. IdenTrust provides an HSM storage option for its organization identity Code Signing certificates, allowing organizations to generate and protect private keys on their own compliant HSM.

Does IdenTrust provide timestamping?

Yes. IdenTrust provides a free RFC 3161 compliant timestamping service with its Code Signing certificates.

Does IdenTrust Code Signing work with Microsoft Authenticode?

Yes. IdenTrust lists Microsoft Authenticode among supported signing environments and identifies formats including EXE, DLL, CAB, OCX and MSI.

Can IdenTrust Code Signing be used for Java?

Yes. Java is among the platforms listed by IdenTrust for its Code Signing certificates.

How long is an IdenTrust Code Signing Certificate valid?

IdenTrust reduced the maximum Code Signing certificate validity to 365 days effective February 26, 2026.

Find the Right IdenTrust Code Signing Option

Choose standard IdenTrust Code Signing when organization identity validation is sufficient. Choose EV Code Signing when your organization specifically needs the additional validation level associated with EV.

Visit IdenTrust

Related Code Signing Resources

IdenTrust Code Signing Certificate

IdenTrust EV Code Signing Certificate

What Is Code Signing?

Microsoft Authenticode Code Signing