Collect Delinea PAM logs

Parser Version: 1.0

Supported in:

Google SecOps SIEM

This document explains how to ingest Delinea Privileged Access Manager (PAM) logs to Google Security Operations using the Bindplane agent.

Delinea PAM (Privilege Manager) generates syslog messages in CEF format for application actions, justification events, change history, password disclosures, and security events. The parser extracts fields and maps them to the Unified Data Model (UDM).

Before you begin

Make sure you have the following prerequisites:

• A Google SecOps instance
• Windows Server 2016 or later, or Linux host with systemd
• Network connectivity between the Bindplane agent and the Delinea PAM server
• If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
• Privileged access to the Delinea PAM web UI

Get Google SecOps credentials for the Bindplane agent

To authenticate the Bindplane agent to Google SecOps, choose one of the following methods:

• New deployments: Use the Chronicle API (Option 1).
• Legacy deployments: Continue using the ingestion authentication file (Option 2) until the Ingestion API is discontinued on July 20, 2027.

Option 1: Create a service account for the Chronicle API (recommended)

1. Sign in to the Google Cloud console and select the Google Cloud project that is linked to your Google SecOps instance.
2. Go to IAM & Admin > Service Accounts.
3. Click Create service account.
4. Provide the following configuration details:
   • Service account name: Enter a name for the account (for example, bindplane-ingest).
   • Service account description: Enter a description (for example, Bindplane agent log ingestion).
5. Click Create and continue.
6. In the Grant this service account access to project section, click Select a role and select Chronicle Editor.
7. Click Continue, and then click Done.
8. Click the service account you created, and then go to the Keys tab.
9. Click Add key > Create new key.
10. Select JSON and click Create. The key file is downloaded to your computer.
11. Save the key file as ingestion-auth.json in the Bindplane collector directory (/opt/observiq-otel-collector/ingestion-auth.json on Linux or C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json on Windows), or update creds_file_path in config.yaml to match the path where you save it.
12. Go to IAM & Admin > Settings and copy the Project number. You'll need it for the exporter configuration.

Note: The JSON key is a credential. Restrict access to the file on the Bindplane host and rotate the key according to your organization's policy.

Option 2: Download the ingestion authentication file (legacy)

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

Note: This file authenticates the agent to the legacy Ingestion API (malachiteingestion-pa.googleapis.com), which Google has scheduled for end of life on July 20, 2027. Plan to move to Option 1 before that date.

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.

   Note: The customer ID is required for configuring the Bindplane agent exporter.

Install the Bindplane agent

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

Windows installation

1. Open 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
   

3. Wait for the installation to complete.

4. Verify the installation by running:

   sc query observiq-otel-collector
   

   The service should show as RUNNING.

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
   

3. Wait for the installation to complete.

4. Verify the installation by running:

   sudo systemctl status observiq-otel-collector
   

   The service should show as active (running).

Additional installation resources

For additional installation options and troubleshooting, see the Bindplane agent installation guide.

Note: The Chronicle API exporter configuration requires Bindplane collector v1.106.0 or later. The previous commands install the latest release. If you're updating an existing installation, upgrade the collector before changing the configuration.

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

Locate the configuration file

• Linux:

  sudo nano /opt/observiq-otel-collector/config.yaml
  

• Windows:

  notepad "C:\Program Files\observIQ OpenTelemetry Collector\config.yaml"
  

Edit the configuration file

• Replace the entire contents of config.yaml with the following configuration:

  receivers:
    udplog:
      listen_address: "0.0.0.0:514"
  
  exporters:
    chronicle/delinea_pam:
      protocol: https
      # Region of your instance, for example us, europe, asia-southeast1
      location: <LOCATION>
      # Project number of the Google Cloud project linked to the instance
      project: '<PROJECT_NUMBER>'
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: chronicle.googleapis.com
      log_type: DELINEA_PAM
      raw_log_field: body
  
  service:
    pipelines:
      logs/delinea_pam_to_chronicle:
        receivers:
          - udplog
        exporters:
          - chronicle/delinea_pam
  

Configuration parameters

Replace the following placeholders:

• Receiver configuration:

  • listen_address: IP address and port to listen on:
    • 0.0.0.0 to listen on all interfaces (recommended)
    • Port 514 is the standard syslog port (requires root on Linux; use 1514 for non-root)

• Exporter configuration:

  • creds_file_path: Full path to the service account JSON key file (Option 1):
    • Linux: /opt/observiq-otel-collector/ingestion-auth.json
    • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
  • customer_id: Customer ID copied from the Google SecOps console
  • location: Replace <LOCATION> with the region of your Google SecOps instance (for example, us, europe, or asia-southeast1). The exporter prefixes chronicle.googleapis.com with this value. See Regional Endpoints for the complete list.
  • project: Replace <PROJECT_NUMBER> with the project number from IAM & Admin > Settings.
  • endpoint: Keep set to chronicle.googleapis.com.

Legacy ingestion API exporter

• If you use the ingestion authentication file from Option 2, replace the exporters block with the following. Set creds_file_path to the path to the ingestion authentication file, and if your instance is outside the US, replace malachiteingestion-pa.googleapis.com with your regional endpoint (for example, europe-malachiteingestion-pa.googleapis.com).

  exporters:
    chronicle/delinea_pam:
      compression: gzip
      creds_file_path: '/opt/observiq-otel-collector/ingestion-auth.json'
      customer_id: '<customer_id>'
      endpoint: malachiteingestion-pa.googleapis.com
      log_type: DELINEA_PAM
      raw_log_field: body
  

Note: This exporter will stop working when the Ingestion API is discontinued on July 20, 2027.

Save the configuration file

• After editing, save the file:
  • Linux: Press Ctrl+O, then Enter, then Ctrl+X
  • Windows: Click File > Save

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
  

  1. Verify the service is running:

     sudo systemctl status observiq-otel-collector
     

  2. Check logs for errors:

     sudo journalctl -u observiq-otel-collector -f
     

• To restart the Bindplane agent in Windows, choose one of the following options:

  • Command Prompt or PowerShell as administrator:

    net stop observiq-otel-collector && net start observiq-otel-collector
    

  • Services console:

    1. Press Win+R, type services.msc, and press Enter.
    2. Locate observIQ OpenTelemetry Collector.
    3. Right-click and select Restart.

    4. Verify the service is running:

       sc query observiq-otel-collector
       

    5. Check logs for errors:

       type "C:\Program Files\observIQ OpenTelemetry Collector\log\collector.log"
       

Configure syslog in Delinea Privilege Manager

Note: The Send policy feedback option needs to be enabled on all policies that are supposed to send syslog formatted events.

1. Sign in to the Delinea PAM web UI.
2. Go to Admin > Configuration > Foreign Systems.
3. Click Create on Syslog Page.
4. Provide the following configuration details:
   • Name: Enter a descriptive name for the server.
   • Protocol: Select UDP (you can also select TCP, depending on your Bindplane agent configuration).
   • Host: Enter the Bindplane agent IP address.
   • Port: Enter the Bindplane agent port number (514 for UDP).
5. Click Save Changes.

Configure syslog server tasks in Delinea Privilege Manager

1. Go to Admin > Tasks > expand Server Tasks folder > expand Foreign Systems folder.
2. Select Syslog.
3. Click Create.
4. Template options:
   • Send SysLog Application Action Events: Generic information about the application that ran, which policy was triggered, date, timestamp, computer, and user.
   • Send SysLog Application Justification Events: Events when a user runs an application requiring a justification workflow.
   • Send SysLog Bad Rated Application Action Events: Events when an application with a bad security rating is being installed or executed.
   • Send SysLog Change History Events: Change history events (first run sends all history; subsequent runs send only new events).
   • Send SysLog Events: All syslog events based on the options selected during syslog server setup.
   • Send SysLog Newly Discovered File Events: Newly discovered file events (requires Default File Inventory Policy and resource discovery schedules).
   • Send SysLog Password Disclosure Events: All password disclosure events.
5. Provide the following configuration details:
   • Template: Select a syslog template (for example, Send Syslog Events to send all the events).
   • Name: Enter a meaningful name for the task.
   • Event Name: Enter a name for the events.
   • Event Severity: Enter a severity level threshold for the events to be sent.
   • Syslog System: Select the syslog server foreign system Bindplane agent server you created in the previous step.

6. Click Create.

   Note: After creating the task, the Scheduled Task page is displayed, where you can run the task on demand or specify how often events are sent (hourly, every 30 minutes, or daily).

UDM mapping table

Log Field	UDM Mapping	Logic
`CEF:0	...	column1`
`CEF:0	...	column2`
`CEF:0	...	column3`
`CEF:0	...	column5`
`CEF:0	...	column7`
%{HOSTNAME}	principal.hostname	Extracted from the log message using the grok pattern "%{HOSTNAME}".
%{TIMESTAMP_ISO8601}	metadata.event_timestamp	Extracted from the log message using the grok pattern "%{TIMESTAMP_ISO8601}".
	metadata.event_type	Hardcoded to "STATUS_UPDATE" in the parser code.
	metadata.log_type	Hardcoded to "DELINEA_PAM" in the parser code.
timestamp	timestamp	The event timestamp is parsed from the "timestamp" field in the raw log, converting it to a UDM timestamp format.

Change Log

View the Change Log for this parser

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