Collect Proofpoint Sendmail Sentrion logs

Supported in:

This document explains how to ingest Proofpoint Sendmail Sentrion logs to Google Security Operations using the Bindplane agent.

Proofpoint Sendmail Sentrion is an enterprise mail transfer agent (MTA) that provides security controls, message tracking, and policy enforcement for outbound and inbound email. It logs mail transactions through the standard syslog mail facility.

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 Proofpoint Sendmail Sentrion MTA server
  • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
  • Privileged access to the Proofpoint Sendmail Sentrion server with root or 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 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 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.

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/proofpoint_sentrion:
        compression: gzip
        creds_file_path: '<CREDS_FILE_PATH>'
        customer_id: '<CUSTOMER_ID>'
        endpoint: <REGION_ENDPOINT>
        log_type: PROOFPOINT_SENDMAIL_SENTRION
        raw_log_field: body
        ingestion_labels:
            env: production

service:
    pipelines:
        logs/sentrion_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/proofpoint_sentrion

Configuration parameters

  • Replace the following placeholders:

  • Receiver configuration:

    • udplog: Receives syslog over UDP. Use tcplog if you configured TCP transport in the syslog configuration.
    • 0.0.0.0:514: Listens on all interfaces on port 514. Change the port if needed (for example, 1514 for non-root Linux).

  • 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 from the Get Google SecOps customer ID step.
    • <REGION_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 Proofpoint Sendmail Sentrion syslog forwarding

Sendmail Sentrion uses the standard syslog mail facility to write mail transaction logs. The default log locations depend on the operating system:

OS Default log path
RHEL / CentOS /var/log/maillog
Debian / Ubuntu /var/log/mail.log
Solaris /var/log/syslog (filtered by mail.*)

Option 1: Configure syslog forwarding using rsyslog

  1. Edit the syslog configuration file on the Sentrion MTA server:

    sudo nano /etc/rsyslog.d/sentrion.conf

  2. Add the following rule to forward mail facility logs to the Bindplane agent:

    mail.*    @BINDPLANE_AGENT_IP:514

  3. Save the file and restart the rsyslog service:

    sudo systemctl restart rsyslog

  4. Verify that logs are being forwarded by checking the Bindplane agent logs.

Option 2: Configure syslog forwarding via the Sentrion management console

  1. Sign in to the Sentrion management console.
  2. Navigate to Configuration > Logging (or System > Log Settings).
  3. Configure remote syslog settings:
    • Syslog server: Enter the IP address of the Bindplane agent host (for example, 192.168.1.100).
    • Port: Enter 514 (must match the Bindplane agent receiver port).
    • Protocol: Select UDP (must match the Bindplane agent receiver configuration).
    • Log level: Set to capture all mail transaction events.
  4. Click Apply or Save.
  5. Verify that logs are being forwarded by checking the Bindplane agent logs.

UDM mapping table

Log Field UDM Mapping Logic
additional.fields Merged from tty_label and pwd_label
action security_result.action_details Value copied directly
action_result security_result.summary Value copied directly if present
app principal.application Value copied directly
app_proto network.application_protocol Value copied directly
auth security_result.detection_fields Merged as auth_label (key: auth, value: auth)
bits security_result.detection_fields Merged as bits_label (key: bits, value: bits)
categorization security_result.category_details Value copied directly
cipher network.tls.cipher Value copied directly
class security_result.detection_fields Merged as class_label (key: class, value: class)
cluster principal.resource.attribute.labels Merged as cluster_label (key: cluster, value: cluster)
COMMAND principal.process.command_line Value copied directly
daemon security_result.detection_fields Merged as daemon_label (key: daemon, value: daemon)
delay security_result.detection_fields Merged as delay_label (key: delay, value: delay)
description security_result.description Value copied directly
details metadata.description Value copied directly
disposition security_result.detection_fields Merged as disposition_label (key: disposition, value: disposition)
dsn security_result.detection_fields Merged as dsn_label (key: dsn, value: dsn)
event_type metadata.event_type Value copied directly
from network.email.from Extracted as valid_from using grok pattern if valid email
host principal.asset.hostname, principal.hostname Value copied directly
ip principal.asset.ip, principal.ip Value copied directly
job_name principal.resource.attribute.labels Merged as job_name_label (key: job_name, value: job_name)
mailer security_result.detection_fields Merged as mailer_label (key: mailer, value: mailer)
msgid network.email.mail_id Value copied directly after removing < and >
mtaqid principal.resource.product_object_id Value copied directly
nw_direction network.direction Set to OUTBOUND if matches (?i)Outbound
nrcpts security_result.detection_fields Merged as nrcpts_label (key: nrcpts, value: nrcpts)
pid principal.process.pid Value copied directly
port principal.port Value copied directly and converted to integer
pri security_result.detection_fields Merged as pri_label (key: priority, value: pri)
processor principal.resource.attribute.labels Merged as processor_label (key: processor, value: processor)
product_event_type metadata.product_event_type Value copied directly
reject_msg security_result.summary Value copied directly if action_result, stat, and status empty
relay_domain intermediary.hostname Value copied directly
relay_ip intermediary.ip Value copied directly
ruleset security_result.rule_name Value copied directly
severity security_result.severity Set to INFORMATIONAL if matches (?i)info
size network.sent_bytes Value copied directly and converted to uinteger
STARTTLS security_result.detection_fields Merged as starttls_label (key: STARTTLS, value: STARTTLS)
stat security_result.summary Value copied directly if action_result empty
status security_result.summary Value copied directly if action_result, stat, and reject_msg empty
subject network.email.subject, security_result.detection_fields Value copied directly and merged as subject_label (key: subject, value: subject)
tls_verify, verify security_result.action, security_result.description Set to ALLOW if matches (?i)OK, BLOCK if matches (?i)FAIL; description set to tls_verify - tls_verify; tls_verify from verify if tls_verify empty
to network.email.to Extracted as valid_to from array using grok pattern for each email
USER, user principal.user.userid Value from USER if not empty, else from user
version network.tls.version Value copied directly
xdelay security_result.detection_fields Merged as xdelay_label (key: xdelay, value: xdelay)
metadata.product_name Set to "Proofpoint Sendmail Sentrion"
metadata.vendor_name Set to "PROOFPOINT_SENDMAIL_SENTRION"

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