> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-code-signing-certificates.md).

# Ordering EV Code Signing Certificates

**What Is an EV Code Signing Certificate?**

An Extended Validation (EV) Code Signing certificate provides the highest level of identity assurance available for signing software, applications, drivers, and executable files. It verifies the publisher's identity and ensures that signed software is authentic, has not been tampered with, and originates from a trusted organization.

Unlike Organization Validation (OV) Code Signing certificates, EV Code Signing certificates require the Certificate Authority (CA) to perform rigorous, multi-step verification of your organization's legal existence, physical address, operational status, and the authority of the individuals requesting the certificate. This validation process is governed by the CA/Browser Forum Code Signing Baseline Requirements and Extended Validation Code Signing Guidelines.

EV Code Signing certificates require the subscriber's private key to be generated and protected within a certified hardware cryptographic device, such as a FIPS-compliant USB token or a secure cloud-based Hardware Security Module (HSM). This significantly reduces the risk of private key compromise and unauthorized code signing.

The issuance timeline is typically 3–5 business days as the CA completes the full Extended Validation process. Once issued, the certificate provides the highest level of publisher trust for securely signing software and establishing publisher authenticity.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-code-signing-certificates.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.