On This Page

Home / Edge/ Secure Your Deployment/ Centralize and Reuse Global Secrets/ Connect External Secret Stores/Connect CyberArk Central Credential Provider Secret Stores

Connect CyberArk Central Credential Provider Secret Stores ​

Configure a secret store that is backed by CyberArk Central Credential Provider (CyberArk CCP) to retrieve global secrets from CyberArk Privileged Access Management (PAM) accounts.

  1. In Global Settings > Security > Secrets > Secret Stores, select Add Secret Store.

  2. In the New Secret Store modal, configure the store using the following fields:

    • Secret store: Select CyberArk CCP.

    • Store name: Unique identifier for the secret store.

    • Description: Brief description of the secret store (optional).

    • URL: Base HTTPS URL of the CyberArk CCP endpoint. Include the host, an optional port, and the IIS application name only (for example, https://components.example.com/AIMWebService).

    • App ID: Application ID registered in CyberArk.

    • Safe: CyberArk Safe that holds the accounts that the secret store will read.

    • Folder: For PAM Self-Hosted, the folder in the CyberArk Safe that holds the accounts that the secret store will read. Leave empty for Root. For a nested folder, enter the full path from Root, using \ as the path separator (for example, Root\Apps\Prod).

    • TLS Settings (Client Side):

      • Client certificate: Certificate stored in Cribl to present when IIS requires mutual TLS (optional).

        Create the certificate from PEM files or a PKCS#12 (.pfx or .p12) bundle. PKCS#12 upload is not available in FIPS mode. Add the certificate and its private key on the Leader.

      • Trusted server CA path: Path on the Leader to a PEM file of certificate authorities (CAs) that verify the CyberArk CCP server certificate (optional). For example, $CRIBL_HOME/local/cribl/auth/server-ca.pem. Enter a path when the server certificate is self-signed or signed by a private CA. Leave blank to use the system trust store.

      • Server name (SNI): Hostname from the CyberArk CCP server certificate (optional). Provide when the certificate was issued for a different hostname than the one in URL. Leave blank when the hostnames match. Cribl sends the hostname that you provide in the TLS handshake and uses the hostname to verify the server certificate.

      • Minimum TLS version: Minimum TLS version to use when connecting to CyberArk CCP (optional).

      • Maximum TLS version: Maximum TLS version to use when connecting to CyberArk CCP (optional).

    • Health check secret: Object name of a credential in the CyberArk Safe (optional). Enter the credential’s Object name exactly as it is stored in the Safe.

      • Create a credential in the CyberArk Safe to use only for the Health check secret, and give it a non-sensitive value. If you provided a Folder, create the credential in the same folder.

      • During Test and Save and subsequent health checks, Cribl reads the credential to confirm that it can retrieve a secret from the Safe. Cribl does not save the credential value or send it to Worker Groups and Edge Fleets.

      • If you leave the Health check secret field empty, Cribl checks only that CyberArk CCP responded, not whether Cribl can retrieve secrets. On every health check, Cribl will ask CyberArk for a credential named cribl-gsm-connectivity-probe. Since you did not create that credential, CyberArk will record a not-found log entry each time. To stop these log entries, enter a Health check secret.

  3. Select Test and Save.

You cannot change the URL, Safe, or Folder after you create the secret store. Create a new secret store to read accounts from a different CyberArk CCP URL, Safe, or Folder.

Reference CyberArk Account Objects ​

When you add a global secret in a secret folder that is backed by a CyberArk CCP secret store, enter the account Object name in one of these fields:

  • External secret reference for a Text secret
  • Secret key reference for an API key and secret key secret
  • Password reference for a Username and password secret

Enter the Object name exactly as CyberArk stores it. Do not enter a path. The Object name cannot contain \, /, :, *, ?, ", <, >, or |, and it cannot start or end with a dot or a space.

Leave Response field empty to use the entire secret stored on the CyberArk account. For a JSON secret, enter a key to extract that field (for example, token).

Health Check Error Messages ​

After five consecutive failed health checks for a CyberArk CCP secret store, Cribl displays a system bulletin message. Health checks run every 30 seconds, so a single transient failure can clear on its own. For details about health checks and reload, deploy, and recovery, see Secret Store Health Check Failures.

A connectivity-only check treats HTTP 404 APPAP004E for cribl-gsm-connectivity-probe as healthy. The same response for a configured Health check secret is an error.

Error messageFailure
CCP health check for store "<store-id>" timed out after 5000msThe health check timed out.
CCP health check secret "<object-name>" not found in store "<store-id>" (HTTP 404, APPAP004E). Check the Object name, Safe, Folder, and retrieval permissions.CyberArk CCP returned an account-not-found response for the configured health check secret.
CCP health check for store "<store-id>" failed (HTTP 401)

CCP health check for store "<store-id>" failed (HTTP 403). Check the client certificate and IIS access settings.

CCP health check for store "<store-id>" failed (HTTP 400, APPAP423E). Check the AIMWebService user and its Vault connection.
CyberArk CCP or IIS denied the request.
CCP health check for store "<store-id>" failed (HTTP <status-code>, AIMWS031E). Check the App ID.

CCP health check for store "<store-id>" failed (HTTP <status-code>, APPAP008E). Check that the application user exists, is enabled, is not expired, and is allowed from the CCP server.
CyberArk CCP requires the App ID, or it cannot use the application user.
CCP health check for store "<store-id>" could not finish because of a temporary error (HTTP <status-code>)CyberArk CCP returned a temporary error (HTTP 408, 429, 500, 502, 503, or 504).
CCP health check for store "<store-id>" could not verify the server certificate (CERT_HAS_EXPIRED)

CCP health check for store "<store-id>" could not verify the server certificate (DEPTH_ZERO_SELF_SIGNED_CERT). Check that Trusted server CA path points to the PEM CA that issued the server certificate.
Cribl could not verify the CyberArk CCP server certificate.
CCP health check for store "<store-id>" did not return a valid secret responseCyberArk CCP answered the health check, but the response was not an account secret.
CCP health check for store "<store-id>" could not reach the server (<error-code>)Cribl could not reach CyberArk CCP.

CyberArk CCP Firewalls and IP Allowlists ​

When the Leader resolves global secrets from CyberArk CCP, it connects to the URL that you configured. If IIS or a firewall in front of that URL accepts connections only from specific addresses, add the Leader egress address to the IIS or firewall allowlist. If the CyberArk application for the App ID uses Allowed Machines, enter that same address on the application.

Cribl.Cloud ​

Cribl.Cloud rejects a CyberArk CCP URL that uses a private IP address. Workspaces use public egress by default, and the Leader egress IP can change.

Enable static egress for the Workspace region so that the Leader uses a stable set of outbound IPs. Those addresses are listed in Workspace > Connections > Static Egress IP. Add every address to the IIS or firewall allowlist and to Allowed Machines on the CyberArk application. If you later disable static egress, those IPs will change, and you must update the IIS or firewall allowlist and Allowed Machines.

On-Prem Deployments ​

In on-prem deployments, the Leader Node typically has a stable egress IP that you control. Use that address. For a high-availability pair, use the address of every Leader that resolves CyberArk CCP secrets.

An on-prem Leader can use an internal hostname or a private IP address as the URL in the secret store configuration.