Infisical is the open-source platform for securing secrets, certificates, access, and AI Agents.
TypeScript acmeagentsai-agentscertificate-managementdevsecopsenvironment-variableskubernetesopen-sourcepampkipostgresprivate-caprivileged-access-managementsecret-managementsecret-managersecretssecrets-managementsecuritysecurity-toolsvault
---
title: "KMIP"
sidebarTitle: "Overview"
description: "Let devices and software that support KMIP manage their keys."
---
The Key Management Interoperability Protocol (KMIP) is a standard protocol that storage arrays, databases, servers, and backup tools use to get their encryption keys from a key manager. With KMIP, these clients can create and fetch keys in Infisical KMS.
<Info>
KMIP is available under Infisical's [Enterprise](https://infisical.com/pricing) plan. If you're self-hosting Infisical, contact [email protected] to purchase an enterprise license.
</Info>
<Accordion title="How it works">
KMIP clients don't connect to Infisical directly. They connect to a KMIP server that you run on your own network with the Infisical CLI, and the KMIP server passes each request on to Infisical:
```mermaid
flowchart LR
subgraph network["Your network"]
client["KMIP client"]
server["KMIP server"]
end
client -- "KMIP request, port 5696" --> server
server -- "HTTPS, port 443" --> infisical["Infisical KMS"]
style network fill:#ffffde,stroke:#aaaa33,color:#000
style client fill:#ececff,stroke:#9370db,color:#000
style server fill:#e1f5fe,stroke:#01579b,color:#000
style infisical fill:#ffffff,stroke:#757575,color:#000
```
1. A KMIP client connects to the KMIP server on port 5696, and authenticates with a client certificate that Infisical issued
2. The KMIP server sends the request to Infisical over HTTPS
3. Infisical runs the request against the keys in the client's KMS project
You create a KMIP server once for your organization, and any KMS project can use it. You register each client in the KMS project whose keys the client uses.
Unlike the Infisical API, KMIP gives the client the key material, and the client encrypts data itself. This means you shouldn't [rotate](/documentation/platform/kms/key-rotation) a key that a KMIP client uses.
</Accordion>
## Set up KMIP
<CardGroup cols={2}>
<Card title="Deploy a KMIP server" icon="server" href="/documentation/platform/kms/kmip-server">
Run the KMIP server that your KMIP clients connect to.
</Card>
<Card title="Connect KMIP clients" icon="plug" href="/documentation/platform/kms/kmip-clients">
Connect a KMIP client to the keys in a KMS project.
</Card>
</CardGroup>
To set up a specific client, see [Dell PowerEdge SEKM](/documentation/platform/kms/kmip-dell-poweredge).
## Supported KMIP versions and operations
The KMIP server supports KMIP versions 1.0 to 1.4, and the following operations on symmetric keys:
| Operation | What it does |
| --- | --- |
| Create | Creates a symmetric key |
| Register | Adds a key that was created outside Infisical |
| Locate | Finds keys by their attributes |
| Get | Returns a key |
| Activate | Makes a key available for use |
| Revoke | Revokes a key |
| Destroy | Deletes a key |
| Get Attributes | Returns a key's attributes |
| Query | Returns the operations and objects that the server supports |
When you register a client, you choose which of these operations the client can run.