Collect CyberArk Privilege Cloud logs

This document explains how to ingest CyberArk Privilege Cloud logs to Google Security Operations using Bindplane. The parser code transforms the logs from their raw SYSLOG + KV format into the Google SecOps Unified Data Model (UDM) format. It first extracts fields from CEF formatted messages using grok patterns and key-value parsing, then maps those fields and others to their corresponding UDM fields, enriching the data with standardized values for vendor, product, and severity.

Before you begin

Make sure you have the following prerequisites:

• Google SecOps instance
• Windows 2016 or later, or a Linux host with systemd
• If running behind a proxy, firewall ports are open
• Privileged access to CyberArk Privilege Cloud

Get Google SecOps ingestion authentication file

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Collection Agents.
3. Download the Ingestion Authentication File. Save the file securely on the system where Bindplane will be installed.

Get Google SecOps customer ID

1. Sign in to the Google SecOps console.
2. Go to SIEM Settings > Profile.
3. Copy and save the Customer ID from the Organization Details section.

Install the Bindplane agent

Install the Bindplane agent on your Windows or Linux operating system according to the following instructions.

Windows installation

1. Open the Command Prompt or PowerShell as an administrator.

2. Run the following command:

   msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet
   

Linux installation

1. Open a terminal with root or sudo privileges.

2. Run the following command:

   sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh
   

Additional installation resources

For additional installation options, consult the installation guide.

Configure the Bindplane agent to ingest Syslog and send to Google SecOps

1. Access the configuration file:
   • Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   • Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

   receivers:
       tcplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:6514"
   
   exporters:
       chronicle/chronicle_w_labels:
           compression: gzip
           # Adjust the path to the credentials file you downloaded in Step 1
           creds_file_path: '/path/to/ingestion-authentication-file.json'
           # Replace with your actual customer ID from Step 2
           customer_id: <customer_id>
           endpoint: malachiteingestion-pa.googleapis.com
           # Add optional ingestion labels for better organization
           log_type: 'CYBERARK_PRIVILEGE_CLOUD'
           raw_log_field: body
           ingestion_labels:
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - tcplog
               exporters:
                   - chronicle/chronicle_w_labels
   

   • Replace the port and IP address as required in your infrastructure.
   • Replace <customer_id> with the actual customer ID.
   • Update /path/to/ingestion-authentication-file.json to the path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.

Restart the Bindplane agent to apply the changes

1. To restart the Bindplane agent in Linux, run the following command:

   sudo systemctl restart bindplane-agent
   

2. To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:

   net stop BindPlaneAgent && net start BindPlaneAgent
   

Install Secure Tunnel

1. Make sure that your Machine ID is unique, even when the machines are deployed in multiple domains.
2. Download the Privilege Cloud software package from Deploy the Privilege Cloud Connector (Standard), copy the Secure Tunnel ZIP file, and unzip it.
3. Run the installation from the unzipped folder.
4. On the Select Installation Folder page, enter the location of the installation folder, and click Next.
5. On the Ready to Install page, click Install.
6. When the installation is complete, click Finish; the configuration tool is launched.

Configure Secure Tunnel

1. On the Authenticate to Privilege Cloud page, enter the following details and then click Next:
   • Subdomain or Customer ID: The subdomain is your system identifier in the system address, as displayed in the Privilege Cloud Portal FQDN: https://<subdomain>.Privilegecloud.cyberark.com. Enter only the <subdomain> identifier, not the whole URL. Alternatively, use the Customer ID provided to you by CyberArk.
   • User name & Password: Enter the credentials provided by CyberArk Support.
2. On the Configure on-premise components page, add the components that you want to connect through the Secure Tunnel, and click Configure Components.
3. Provide the following configuration details:
   • Component Type: Select SIEM.
   • Host Address: Enter the Bindplane agent host address (SIEM component must include a hostname).
   • Destination Port: Enter the Bindplane agent port number.
   • Remote Port: The port used by the CyberArk to interface with your Secure Tunnel (The Remote Port is provided to you by CyberArk support, typically the port is 1468).
   • Click Advanced to display this column.
   • Access through Secure Tunnels: You can configure which Secure Tunnels your servers will access through, even if these Secure Tunnels are running on a different machine.
4. Click Configure Components > Close.

UDM mapping table

Need more help? Get answers from Community members and Google SecOps professionals.