> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeperpam/privileged-access-manager/cloud-security/keeper-encrypter.md).

# Keeper Encrypter

Keeper Encrypter preserves Keeper's zero-knowledge architecture for Cloud Security integrations. It provides a secure, self-hosted path for CNAPP findings and remediation status.

### Why Keeper Encrypter exists

CNAPP providers need to send findings into Keeper. Keeper needs to return remediation status after an admin takes action. Keeper Encrypter handles that exchange without moving customer decryption into Keeper's cloud.

### How it works

* It runs as a Docker container in your environment.
* It receives inbound webhook traffic from the CNAPP provider.
* It encrypts integration payloads with a customer-managed 256-bit key stored in Keeper.

The service authenticates with Keeper using the device configuration you generate during setup. It reads the CNAPP configuration it needs through Keeper Secrets Manager. This keeps the integration aligned with Keeper's zero-knowledge model.

## Setup

{% stepper %}
{% step %}

### Generate a 256-bit encryption key

Use OpenSSL to generate the key:

```
openssl rand -base64 32
```

{% endstep %}

{% step %}

### Store the key in Keeper

* Create a shared folder in your vault.
* Create a new **Secure Note** record in that folder.
* Paste the Base64 key from the previous step into the record.
  {% endstep %}

{% step %}

### Create the application and gateway

* Create a new Keeper Secrets Manager application.
* Select the shared folder that stores the encryption key.
* Grant **Can Edit** permission.
* Create a new Gateway.
* Select **Linux** configuration.
* For **Config Type**, select **Base64**.
* Save the generated value for `DEVICE_CONFIG`.
  {% endstep %}

{% step %}

### Pull the Docker image

```
docker pull keeper/encrypter
```

{% endstep %}

{% step %}

### Create the `.env` file

Create a `.env` file in the Keeper Encrypter root folder.

Set `DEVICE_CONFIG` to the value you saved in the previous step. Fill the remaining values during provider-specific setup.

```
BACKEND_WEBHOOK_URL=https://connect.keepersecurity.com/api/device/cnapp/issue
NETWORK_UID=
PAYLOAD_TYPE=
KSM_CNAPP_CONFIG_RECORD_ID=
DEVICE_CONFIG=
CONNECT_URL=https://connect.keepersecurity.com
PORT=
```

{% endstep %}

{% step %}

### Complete the provider setup

[Configure Wiz](/keeperpam/privileged-access-manager/cloud-security/wiz-integration.md)
{% endstep %}
{% endstepper %}


---

# 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.keeper.io/keeperpam/privileged-access-manager/cloud-security/keeper-encrypter.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.