Collect CyberArk Privilege Cloud logs

Supported in:

Google secops SIEM

This document explains how to ingest CyberArk Privilege Cloud logs to Google Security Operations using Bindplane. CyberArk Privilege Cloud is a SaaS-based privileged access management solution that secures, manages, and monitors privileged credentials in the cloud. It provides automated credential rotation, session isolation and recording, just-in-time access provisioning, and comprehensive audit logging for privileged account activities across hybrid and multi-cloud environments.

Before you begin

Make sure you have the following prerequisites:

A Google SecOps instance.
A Windows 2016 or later or Linux host with systemd.
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements.
Privileged access to the CyberArk Privilege Cloud administration portal with Vault Admin permissions.
A valid TLS certificate for the Bindplane agent host (required for syslog over TLS on port 6514).

Get Google SecOps ingestion authentication file

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

Get Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
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

Open the Command Prompt or PowerShell as an administrator.

Run the following command:

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

Linux installation

Open a terminal with root or sudo privileges.

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 this installation guide.

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

Access the Configuration File:
- Locate the config.yaml file. Typically, it's in the /opt/observiq-otel-collector/ directory on Linux or in the installation directory on Windows.
- Open the file using a text editor (for example, nano, vi, or Notepad).

Edit the config.yaml file as follows:

receivers:
    tcplog:
        # Replace the port and IP address as required
        listen_address: "0.0.0.0:6514"
        tls:
            cert_file: '/path/to/server.crt'
            key_file: '/path/to/server.key'

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: <PLACEHOLDER_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 <PLACEHOLDER_CUSTOMER_ID> with the actual Customer ID.
Update /path/to/ingestion-authentication-file.json to the file path where the authentication file was saved in the Get Google SecOps ingestion authentication file section.
Update /path/to/server.crt and /path/to/server.key with the actual paths to your TLS certificate and key files.

Note: CyberArk Privilege Cloud requires TLS for syslog connections. The Bindplane agent must be configured with a valid TLS certificate. If you use a self-signed certificate, you must import the CA certificate into CyberArk Privilege Cloud.

Configuration without TLS (TCP only)

If your network architecture includes a TLS-terminating proxy between CyberArk Privilege Cloud and the Bindplane agent, you can use plain TCP:
```
receivers:
    tcplog:
        listen_address: "0.0.0.0:514"
```

Restart the Bindplane agent to apply the changes

To restart the Bindplane agent in Linux, run the following command:
```
sudo systemctl restart observiq-otel-collector
```
To restart the Bindplane agent in Windows, you can either use the Services console or enter the following command:
```
net stop observiq-otel-collector && net start observiq-otel-collector
```

Configure CyberArk Privilege Cloud syslog forwarding

Configure SIEM integration in Privilege Cloud

Sign in to the CyberArk Privilege Cloud administration portal.
Go to Administration > Configuration Options > Options > SIEM Integration.
Select Enable SIEM Integration to activate syslog forwarding.
Provide the following configuration details:
- SIEM Type: Select Syslog.
- Syslog Server Address: Enter the IP address or FQDN of the Bindplane agent host (for example, syslog.example.com).
- Syslog Server Port: Enter 6514.
- Protocol: Select TLS.
- Format: Select CEF (Common Event Format).
Note: CyberArk Privilege Cloud does not support UDP. Only TCP and TLS protocols are available for syslog forwarding.
In the Event Types section, select the event categories to forward:
- Vault Audit: Vault access and credential retrieval events.
- Session Audit: Privileged session monitoring events.
- Safe Management: Safe creation, modification, and deletion events.
- User Management: User provisioning and permission changes.
- Policy Changes: Platform and policy modification events.
Click Save.

Verify the TLS connection

Verify the Bindplane agent is listening on port 6514:
```
sudo ss -tlnp | grep 6514
```
Verify logs are being received by checking the Bindplane agent logs:
```
sudo journalctl -u observiq-otel-collector -f
```
If no logs are received, verify the following:
- The Bindplane agent host is reachable from the internet (CyberArk Privilege Cloud is a SaaS service).
- Firewall rules allow inbound TCP connections on port 6514.
- The TLS certificate is valid and not expired.
- The TLS certificate CN or SAN matches the hostname configured in CyberArk Privilege Cloud.

For more information about CyberArk Privilege Cloud SIEM integration, see the CyberArk Privilege Cloud documentation.

UDM mapping table

Log Field	UDM Mapping	Logic
`Header.deviceVendor`	`metadata.vendor_name`	Mapped from the CEF header vendor field. Set to "CyberArk".
`Header.deviceProduct`	`metadata.product_name`	Mapped from the CEF header product field. Set to "Privilege Cloud".
`Header.deviceVersion`	`metadata.product_version`	Mapped from the CEF header version field.
`Header.signatureId`	`metadata.product_event_type`	The audit action code from CEF signature ID.
`Header.name`	`metadata.description`	The event name from CEF header.
`Header.severity`	`security_result.severity`	Mapped from CEF severity (0-3=LOW, 4-6=MEDIUM, 7-8=HIGH, 9-10=CRITICAL).
`suser`	`principal.user.userid`	The user who performed the action.
`src`	`principal.ip`	The source IP address of the session.
`shost`	`principal.hostname`	The source hostname.
`duser`	`target.user.userid`	The target privileged account.
`dhost`	`target.hostname`	The target system hostname.
`dst`	`target.ip`	The target system IP address.
`cs1`	`security_result.detection_fields`	Safe name (key: cs1Label value).
`cs2`	`security_result.detection_fields`	Account name or additional context (key: cs2Label value).
`cs3`	`security_result.detection_fields`	Platform ID or policy information (key: cs3Label value).
`act`	`security_result.action_details`	The action performed (for example, Retrieve, Connect, Update).
`reason`	`security_result.description`	The reason provided for the privileged access.
`rt`	`metadata.event_timestamp`	The event receipt time.

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