Collect Archer IRM logs

This document explains how to ingest Archer IRM (Integrated Risk Management) logs to Google Security Operations using Bindplane. The parser first attempts to structure the SYSLOG data using a specific Grok pattern. If the pattern doesn't match, it assumes a key-value format, extracts fields, and maps them to the Unified Data Model (UDM), handling different event types and database resource information along the way.

Before you begin

Make sure you have the following prerequisites:

• Google SecOps instance
• A Windows 2016 or later, or a Linux host with systemd
• If running behind a proxy, firewall ports are open
• Archer IRM 6.x on-premises instance with the Audit Logging feature licensed
• Administrative access to the Archer Control Panel

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: 'ARCHER_IRM'
           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

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

  sudo systemctl restart bindplane-agent
  

• 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
  

Configure Syslog for Archer IRM Audit Logging

1. Open the Archer Control Panel on the application server.
2. Go to Instance Management > All Instances and double-click the target instance.
3. On the General tab, find the Audit section and select the Enable Audit Logging for this instance checkbox.
4. Provide the following configuration details:
   • HostName or IP Address – Enter the Bindplane agent IP address.
   • Port – Enter the Bindplane agent port number (for example, 6514).
   • IP Version – Select IPv4.
   • IP Traffic Method – Select TCP.
5. Click Test Connection (only available when TCP is selected) to verify connectivity.
6. Click Save.

UDM mapping table

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