> ## 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

> Outlines environment prerequisites and compatibility requirements for Bitwarden integration.

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

* Windows 10 and later
* Linux

## 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 all hosts where you install or configure components.

## Network and firewall

* Allow outbound TCP port **2001**(default Host API port) from your self-hosted Bitwarden 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 a FQDN so the exemption applies.
</Warning>

## Other

* OpenSSL
* Bitwarden

<Note>
  Refer to the Bitwarden [About Key Connector](https://bitwarden.com/help/about-key-connector/) article to ensure you understand the requirements for enabling Key Connector (such as having an Enterprise organization, a self-hosted Bitwarden server, an active SSO implementation, and so on).
</Note>