Collect Cisco Wireless Intrusion Prevention System (WIPS) logs

This document explains how to ingest Cisco Wireless Intrusion Prevention System (WIPS) logs to Google Security Operations using Bindplane. The parser extracts key-value pairs from the syslog messages, then maps those values to Unified Data Model (UDM) fields. It determines the appropriate event_type based on the presence of principal, target, and user information, and categorizes security events based on eventType and other fields.

Before you begin

Make sure you have the following prerequisites:

• Google SecOps instance
• Windows 2016 or later, or a Linux host with systemd
• If running behind a proxy, ensure firewall ports are open
• Privileged access to Cisco Access Point (AP) / Wireless LAN Controller (WLC)

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:
       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_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: 'CISCO_WIPS'
           raw_log_field: body
           ingestion_labels:
   
   service:
       pipelines:
           logs/source0__chronicle_w_labels-0:
               receivers:
                   - udplog
               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 Adaptive Wireless Intrusion Prevention System (aWIPS) on Cisco Catalyst

1. Sign in to Cisco Catalyst using SSH.

2. Enter global config to enable aWIPS under the AP profile:

   configure terminal
   ap profile <profile-name>
   awips
   

3. Configure syslog throttle interval for 60 seconds:

   awips-syslog throttle period 60
   

Configure Syslog using Cisco AP profiles

1. In AP-join profile (via CLI):

   configure terminal
   ap profile <profile-name>
     syslog host <Bindplane_IP_address>
     syslog level informational
     syslog facility local0
   end
   

Configure Syslog on Cisco WLC (GUI)

1. Sign in to the WLC web UI.
2. Go to Management > Logs > Config.
3. Enter the Bindplane agent IP address in the Syslog Server IP Address field.
4. Click Add.
5. Provide the following configuration details:
   • Syslog Severity: Select Informational.
   • Syslog Facility: Select Local Use 0.
6. Click Apply.
7. Click Save Configuration.

Configure Syslog on Access Points using WLC (CLI)

1. Global AP syslog host:

   config ap syslog host global <Bindplane_IP_address>
   

2. Configure the specific AP syslog host:

   config ap syslog host specific <AP-name> <Bindplane_IP_address>
   

3. Set the AP syslog severity:

   config ap logging syslog level informational
   

4. Set the facility for AP messages:

   config logging syslog facility local0
   

UDM mapping table

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