Console
    Start free

    Collect SailPoint IdentityIQ logs

    Supported in:

    This document explains how to ingest SailPoint IdentityIQ logs to Google Security Operations using the Bindplane agent.

    SailPoint IdentityIQ is an identity governance platform for access certification, provisioning, and compliance management. It supports syslog-level logging through its Log4j configuration, allowing audit events and application logs to be forwarded to a remote syslog collector.

    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 SailPoint IdentityIQ application server
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
    • Privileged access to the SailPoint IdentityIQ application server with administrator permissions

    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.

    4. 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 IDfrom the Organization Detailssection.

    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 Promptor PowerShellas 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 .

    Configure 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/sailpoint_iiq 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 SAILPOINT_IIQ 
  
 raw_log_field 
 : 
  
 body 
 service 
 : 
  
 pipelines 
 : 
  
 logs/sailpoint_iiq_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/sailpoint_iiq

    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 ingestion authentication file:
        • Linux: /etc/bindplane-agent/ingestion-auth.json
        • Windows: C:\Program Files\observIQ OpenTelemetry Collector\ingestion-auth.json
      • customer_id : Customer ID copied from the Google SecOps console
      • endpoint : Regional endpoint URL:
        • US: malachiteingestion-pa.googleapis.com
        • Europe: europe-malachiteingestion-pa.googleapis.com
        • Asia: asia-southeast1-malachiteingestion-pa.googleapis.com
        • See Regional Endpoints for complete list

    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 SailPoint IdentityIQ syslog forwarding

    SailPoint IdentityIQ uses Log4j for logging. Configure a syslog appender to forward logs to the Bindplane agent.

    1. Log in to the SailPoint IdentityIQ server as an administrator.
    2. Locate the Log4j configuration file:
      • IdentityIQ 7.x and earlier: <TOMCAT_HOME>/webapps/identityiq/WEB-INF/classes/log4j.properties
      • IdentityIQ 8.0 and later: <TOMCAT_HOME>/webapps/identityiq/WEB-INF/classes/log4j2.properties

    3. Add or update a syslog appender in the configuration file. For Log4j 1.x ( log4j.properties ):

       log4j.appender.SYSLOG=org.apache.log4j.net.SyslogAppender
log4j.appender.SYSLOG.syslogHost=<BINDPLANE_AGENT_IP>
log4j.appender.SYSLOG.port=514
log4j.appender.SYSLOG.facility=LOCAL0
log4j.appender.SYSLOG.layout=org.apache.log4j.PatternLayout
log4j.appender.SYSLOG.layout.ConversionPattern=%d{ISO8601} %-5p %c - %m%n

    4. For Log4j 2.x ( log4j2.properties ), add a Syslog appender:

       appender.syslog.type = Syslog
appender.syslog.name = SYSLOG
appender.syslog.host = <BINDPLANE_AGENT_IP>
appender.syslog.port = 514
appender.syslog.protocol = UDP
appender.syslog.facility = LOCAL0
appender.syslog.format = RFC5424

    5. Add the syslog appender to the root logger:

      • Log4j 1.x: log4j.rootLogger=INFO, file, SYSLOG
      • Log4j 2.x: rootLogger.appenderRef.syslog.ref = SYSLOG

    6. Save the configuration file and restart the IdentityIQ application server (for example, Apache Tomcat) for changes to take effect.

    UDM mapping table

    Log Field UDM Mapping Logic
    api_module
    		about.labels Merged
    data_label
    		additional.fields Merged
    ou1_label
    		additional.fields Merged
    ou2_label
    		additional.fields Merged
    ou3_label
    		additional.fields Merged
    ou4_label
    		additional.fields Merged
    ou5_label
    		additional.fields Merged
    ou6_label
    		additional.fields Merged
    ou7_label
    		additional.fields Merged
    temp_value_label
    		additional.fields Merged
    type_label
    		additional.fields Merged
    type_label1
    		additional.fields Merged
    type_temp_label
    		additional.fields Merged
    value_label
    		additional.fields Merged
    has_principal
    		extensions.auth.type Mapped: true → AUTHTYPE_UNSPECIFIED
    desc
    		metadata.description Directly mapped
    description
    		metadata.description Directly mapped
    left_message_data_doctype
    		metadata.description Renamed/mapped
    left_message_systemd
    		metadata.description Renamed/mapped
    created
    		metadata.event_timestamp Parsed as UNIX_MS
    event_type
    		metadata.event_type Directly mapped
    product_event_type
    		metadata.product_event_type Directly mapped
    id
    		metadata.product_log_id Directly mapped
    application
    		principal.application Directly mapped
    client_host
    		principal.asset.hostname Directly mapped
    host
    		principal.asset.hostname Directly mapped
    client_ip
    		principal.asset.ip Merged
    client_host
    		principal.hostname Directly mapped
    displayName
    		principal.hostname Directly mapped
    host
    		principal.hostname Directly mapped
    identity
    		principal.hostname Directly mapped
    log_origin
    		principal.hostname Directly mapped
    client_ip
    		principal.ip Merged
    ref
    		principal.url Directly mapped
    display
    		principal.user.user_display_name Directly mapped
    lauer
    		principal.user.userid Directly mapped
    launcher
    		principal.user.userid Directly mapped
    source
    		principal.user.userid Directly mapped
    username
    		principal.user.userid Directly mapped
    action
    		security_result.action_details Directly mapped
    field_
    		security_result.detection_fields Merged
    event_level
    		security_result.severity Mapped values (5 total, e.g. (?i)Low → LOW , (?i)Informational → INFORMATIONAL , `(?i)...
    server
    		target.asset.hostname Directly mapped
    server_host
    		target.asset.hostname Directly mapped
    server
    		target.hostname Directly mapped
    server_host
    		target.hostname Directly mapped
    N/A
    		 extensions.auth.type Constant: AUTHTYPE_UNSPECIFIED
    N/A
    		 metadata.event_type Constant: SERVICE_START
    N/A
    		 metadata.product_name Constant: IAM
    N/A
    		 metadata.vendor_name Constant: SAILPOINT
    N/A
    		 security_result.severity Constant: LOW
    N/A
    		 target.application Constant: SailPointIIQ Web Application

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

    Design a Mobile Site
    View Site in Mobile | Classic
    Share by: