> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Before you start

> Pre-requisites checklist for Jenkins code signing integration, including hardware, OS, access, and network requirements.

Verify your environment meets these requirements.

## Supported hardware

* KMES Series 3, application version `6.3.1.3` or later, with initial setup completed (including loading a Platform Master Key and network configuration).

## Supported operating systems

* This integration guide uses the **Web application ARchive (WAR)** file version of Jenkins. You can install it on any operating system or platform that runs a version of Java supported by Jenkins. See the [**Java Requirements**](https://www.jenkins.io/doc/administration/requirements/java/) page on the jenkins.io website for details.

## Required access

* An account on the KMES with administrator permissions to create roles, identities, TLS PKI, and update system settings.
* Local administrator/root access on the server where Jenkins is installed.

## Network and firewall

* Allow outbound TCP port**2001**(default Host API port) from the Jenkins server to the KMES Series 3, specified by FQDN (for example, `kmes.example.com`) or CIDR (for example, `10.0.0.0/24`).

<Warning>
  TLS inspection or SSL proxies can break mutual TLS handshakes. Exempt the KMES FQDN(s) from inspection. Configure the KMES Series 3 with an FQDN so the exemption applies.
</Warning>