Keeper Encrypter
Deploy the Keeper Encrypter service for Keeper Cloud Security integrations.
Why Keeper Encrypter exists
How it works
Setup
5
Last updated
Deploy the Keeper Encrypter service for Keeper Cloud Security integrations.
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.
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.
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.
.env fileCreate 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=Last updated

