Collect Cisco Secure Workload (formerly Tetration Analytics) logs

Supported in:

Google secops SIEM

This document explains how to ingest Cisco Secure Workload (formerly Tetration Analytics) logs to Google Security Operations using the Bindplane agent.

Cisco Secure Workload is an on-premises workload protection platform that provides micro-segmentation, application dependency mapping, and compliance monitoring for data center and cloud workloads. It generates logs about policy violations, flow events, and security incidents. The platform supports built-in syslog export for forwarding alert and flow data to external collectors.

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 Cisco Secure Workload cluster
If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
Privileged access to the Cisco Secure Workload cluster with administrator or site admin role

Get a Google SecOps ingestion authentication file

Sign in to the Google SecOps console.
Go to SIEM Settings > Collection Agents.
Download the Ingestion Authentication File.
Save the file securely on the system where Bindplane will be installed.

Note: This JSON file contains credentials for authenticating the Bindplane agent to Google SecOps.

Get a Google SecOps customer ID

Sign in to the Google SecOps console.
Go to SIEM Settings > Profile.
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

Open Command Prompt or PowerShell as an administrator.

Run the following command:

msiexec /i "https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi" /quiet

Wait for the installation to complete.
Verify the installation by running:
```
sc query observiq-otel-collector
```
The service should show as RUNNING.

Linux installation

Open a terminal with root or sudo privileges.

Run the following command:

sudo sh -c "$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)" install_unix.sh

Wait for the installation to complete.
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/cisco_secure_workload:
        compression: gzip
        creds_file_path: '/etc/bindplane-agent/ingestion-auth.json'
        customer_id: '<customer_id>'
        endpoint: malachiteingestion-pa.googleapis.com
        log_type: CISCO_SECURE_WORKLOAD
        raw_log_field: body

service:
    pipelines:
        logs/cisco_secure_workload_to_chronicle:
            receivers:
                - udplog
            exporters:
                - chronicle/cisco_secure_workload

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

Verify the service is running:

sudo systemctl status observiq-otel-collector

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 Cisco Secure Workload syslog forwarding

Sign in to the Cisco Secure Workload web console.
Go to Manage > External Integrations > Syslog.

Note: In earlier versions of Cisco Secure Workload (Tetration), navigate to Manage > Workloads > Connectors and add a new Syslog connector.
Click Create New Syslog Export (or Add Connector).
Provide the following configuration details:
- Name: Enter a name (for example, chronicle-syslog-export).
- Host: Enter the IP address of the Bindplane agent host.
- Port: Enter 514 (or the port configured in the Bindplane agent receiver).
- Protocol: Select UDP.
- Facility: Select local7 (or your preferred facility).
- Severity: Select Informational or lower to capture all events.
Click Save.
Verify that logs are being sent by checking the Bindplane agent logs for incoming syslog messages.

Note: Cisco Secure Workload sends alerts, policy violation events, flow data, and enforcement events via syslog. Ensure the Bindplane agent host is reachable from the Cisco Secure Workload cluster on the configured port.

UDM field mapping reference

Log Field	UDM Mapping	Logic
connection, event_name	additional.fields	Merged as labels if not empty
alert_time	metadata.collected_timestamp	Converted from epoch ms to timestamp
	metadata.event_type	Set to "NETWORK_FLOW" if has_principal is true, else "GENERIC_EVENT"
root_scope_id	metadata.product_deployment_id	Value copied directly
type	metadata.product_event_type	Value copied directly
key_id	metadata.product_log_id	Value copied directly
	metadata.product_name	Set to "SECURE WORKLOAD"
	metadata.product_version	Set to "1"
	metadata.vendor_name	Set to "CISCO"
alert_details_json.protocol	network.ip_protocol	Value copied directly if type COMPLIANCE
details.HostName	principal.asset.hostname	Value copied directly if type ENFORCEMENT
alert_details_json.constituent_flows.0.consumer_address, details.IP	principal.asset.ip	Value from consumer_address if type COMPLIANCE, else from details.IP, then remove trailing space and beyond
details.CurrentVersion	principal.asset.platform_software.platform_version	Value copied directly if type ENFORCEMENT
details.Bios	principal.asset.software	Value copied directly if type ENFORCEMENT
alert_details_json.time_range.0	principal.domain.first_seen_time	Converted from epoch ms to timestamp if type COMPLIANCE
alert_details_json.time_range.1	principal.domain.last_seen_time	Converted from epoch ms to timestamp if type COMPLIANCE
details.HostName	principal.hostname	Set to "UNKNOWN" if type COMPLIANCE, else value from details.HostName if type ENFORCEMENT
alert_details_json.constituent_flows.0.consumer_address, details.IP	principal.ip	Value from consumer_address if type COMPLIANCE, else from details.IP, then remove trailing space and beyond
details.Platform	principal.platform_version	Value copied directly if type ENFORCEMENT
alert_details_json.provider_port	principal.port	Converted to integer if type COMPLIANCE
pid	principal.process.pid	Value copied directly
alert_details_json.provider_scope_ids, alert_details_json.provider_scope_names, alert_details_json.internal_trigger.label	principal.resource.attribute.labels	Merged as labels if type COMPLIANCE
alert_details_json.application_id	principal.resource.product_object_id	Value copied directly if type COMPLIANCE
details.AgentType	principal.user.attribute.roles	Value copied directly if type ENFORCEMENT
alert_details_json.policy_category	security_result.category_details	Merged from array if type COMPLIANCE
alert_text	security_result.description	Value copied directly
alert_conf_id	security_result.rule_id	Value copied directly if type COMPLIANCE
alert_details_json.internal_trigger.rules.field	security_result.rule_name	Value copied directly if type COMPLIANCE
alert_details_json.internal_trigger.rules.type	security_result.rule_type	Value copied directly if type COMPLIANCE
severity	security_result.severity	Value copied directly
alert_details_json.policy_type	security_result.summary	Value copied directly if type COMPLIANCE
alert_details_json.constituent_flows.0.provider_address	target.asset.ip	Value copied directly if type COMPLIANCE
tenant_id	target.group.product_object_id	Value copied directly if not empty or "0"
	target.hostname	Set to "UNKNOWN"
alert_details_json.constituent_flows.0.provider_address	target.ip	Value copied directly if type COMPLIANCE
alert_details_json.constituent_flows.0.consumer_port	target.port	Converted to integer if type COMPLIANCE
alert_details_json.consumer_scope_ids, alert_details_json.consumer_scope_names	target.resource.attribute.labels	Merged as labels if type COMPLIANCE

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