Collect Broadcom Symantec SiteMinder Web Access logs

This document explains how to collect Broadcom Symantec SiteMinder Web Access logs to Google Security Operations using a Bindplane agent. The parser transforms raw JSON formatted logs into a structured Unified Data Model (UDM). It extracts fields from the raw log messages using grok patterns, renames and maps them to the UDM schema, handles different event types and user formats, and ultimately enriches the data for security analysis.

Before you begin

• Ensure that you have a Google SecOps instance.
• Ensure that you are using Windows 2016 or later, or a Linux host with systemd.
• If running behind a proxy, ensure firewall ports are open.
• Ensure that you have privileged access to Symantec SiteMinder.

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

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

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

1. Access the configuration file:

   1. Locate the config.yaml file. Typically, it's in the /etc/bindplane-agent/ directory on Linux or in the installation directory on Windows.
   2. Open the file using a text editor (for example, nano, vi, or Notepad).

2. Edit the config.yaml file as follows:

   receivers:
       udplog:
           # Replace the port and IP address as required
           listen_address: "0.0.0.0:514"
   
   exporters:
       chronicle/chronicle_w_labels:
           compression: gzip
           # Adjust the path to the credentials file you downloaded in Step 1
           creds: '/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
           ingestion_labels:
               log_type: CA_SSO_WEB
               raw_log_field: body
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               exporters:
                   - chronicle/chronicle_w_labels
   

3. Replace the port and IP address as required in your infrastructure.

4. Replace <customer_id> with the actual customer ID.

5. 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 on Symantec SiteMinder - 12.8

1. Verify that an X-windows server is running on your system.
2. Open a terminal window.

3. Set the DISPLAY variable with the following command:

   export DISPLAY=<IP_ADDRESS>:0.0
   

   • Replace <IP_ADDRESS> with the IP address of the system from which you are connecting to the console. (For example, 192.168.1.100).

4. Sign in to the system hosting the console.

5. Go to the <installation_directory>/siteminder/bin directory.

   • Replace <installation_directory> with the location in the file system where the Policy Server is installed. (For example, /opt/CA/siteminder).

6. Open the console by running the following command:

   ./smconsole
   

7. Click the Data tab.

8. Click the Database drop-down list, and then select Audit Logs.

9. Click the Storage drop-down list, and then select Syslog.

10. Select the value LOG_INFO in the Priority field.

11. Select the value LOG_LOCAL0 in the Facility field.

12. Click OK.

Restart the UNIX Policy Server

1. Sign in to the system hosting the Policy Server with the same user account that installed the Policy Server originally.
2. Open the Management Console.
3. Click the Status tab, and then click the Stop buttons.
4. Wait for all services to stop.
5. in the same Status tab, click the Start buttons.

UDM Mapping Table

Changes

2024-06-25

Enhancement:

• Added a Grok pattern to parse newly ingested syslog format.

2022-08-08

Enhancement:

• Added the header.
• Added conditional check and grok pattern for the field 'ClientIp' mapped to 'principal.ip'.
• Added conditional checks for the fields :
• 'Action' mapped to 'network.http.method'.
• 'AgentName' mapped to 'target.hostname'.
• 'sm_user' mapped to 'target.user.email_addresses'
• 'sm_group' mapped to 'target.user.group_identifiers'.

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