Console
    Start free

    Collect Cisco Wireless Intrusion Prevention System (WIPS) logs

    Supported in:

    This document explains how to ingest Cisco Wireless Intrusion Prevention System (WIPS) logs to Google Security Operations using the Bindplane agent.

    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:

    • A Google SecOps instance
    • Windows Server 2016 or later, or Linux host with systemd
    • Network connectivity between the Bindplane agent and the Cisco Access Point (AP) or Wireless LAN Controller (WLC)
    • If running behind a proxy, ensure firewall ports are open per the Bindplane agent requirements
    • Privileged access to Cisco Access Point (AP) or 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

    4. Save the file securely on the system where the Bindplane agent 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 the Bindplane agent to ingest syslog and send to Google SecOps

    Locate the configuration file

    • Linux:

       sudo  
nano  
/etc/bindplane-agent/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_wips 
 : 
  
 compression 
 : 
  
 gzip 
  
 creds_file_path 
 : 
  
 '/etc/bindplane-agent/ingestion-auth.json' 
  
 customer_id 
 : 
  
 '<customer_id>' 
  
 endpoint 
 : 
  
 malachiteingestion-pa.googleapis.com 
  
 log_type 
 : 
  
 CISCO_WIPS 
  
 raw_log_field 
 : 
  
 body 
 service 
 : 
  
 pipelines 
 : 
  
 logs/cisco_wips_to_chronicle 
 : 
  
 receivers 
 : 
  
 - 
  
 udplog 
  
 exporters 
 : 
  
 - 
  
 chronicle/cisco_wips

    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 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>
syslog level informational
syslog facility local0
end

    2. Replace <BINDPLANE_IP> with the Bindplane agent IP address.

    Configure syslog on Cisco WLC (GUI)

    1. Sign in to the WLCweb UI.
    2. Go to Management > Logs > Config.
    3. Enter the Bindplane agent IP address in the Syslog Server IP Addressfield.
    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>

    2. Configure the specific AP syslog host:

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

    3. Set the AP syslog severity:

       config ap logging syslog level informational

    4. Set the facility for AP messages:

       config logging syslog facility local0

    5. Replace <BINDPLANE_IP> with the Bindplane agent IP address.

    UDM mapping table

    Log Field UDM Mapping Logic
    applicationCategoryData
    		security_result.summary Directly mapped.
    applicationSpecificAlarmID
    		target.resource.attribute.labels.applicationSpecificAlarmID Converted to a label on the target resource.
    attackerMacAddr
    		target.mac Directly mapped.
    authEntityId
    		principal.resource.attribute.labels.authEntityId Converted to a label on the principal resource.
    category
    		security_result.category_details Directly mapped.
    detectingApCount
    		target.resource.attribute.labels.detectingApCount Converted to a label on the target resource.
    description
    		metadata.description Directly mapped.
    displayName
    		principal.user.userid Extracted using regular expression host/(?P<user_id>[\\w-]+) from displayName if the pattern matches.
    eventType
    		metadata.product_event_type Directly mapped.
    instanceId
    		principal.resource.attribute.labels.instanceId Converted to a label on the principal resource.
    instanceUuid
    		metadata.product_log_id Directly mapped.
    instanceVersion
    		principal.resource.attribute.labels.instanceVersion Converted to a label on the principal resource.
    macInfo
    		target.resource.attribute.labels.macInfo Converted to a label on the target resource.
    notificationDeliveryMechanism
    		target.resource.attribute.labels.notificationDeliveryMechanism , network.ip_protocol Converted to a label on the target resource. If the value contains "snmp" (case-insensitive), network.ip_protocol is set to "UDP".
    previousSeverity
    		target.resource.attribute.labels.previousSeverity Converted to a label on the target resource. Set to "AUTHTYPE_UNSPECIFIED" if eventType is "USER_AUTHENTICATION_FAILURE" and user_id is not empty. Copied from the log's timestamp . Determined by parser logic based on several conditions:
    "USER_LOGIN" if eventType is "USER_AUTHENTICATION_FAILURE" and user_id is not empty.
    "NETWORK_CONNECTION" if both is_target_present and is_principal_present are true.
    "STATUS_UPDATE" if is_principal_present is true.
    "USER_UNCATEGORIZED" if user_id is not empty.
    "GENERIC_EVENT" otherwise. Hardcoded to "CISCO_WIPS". Hardcoded to "Wireless Intrusion Prevention System (WIPS)". Hardcoded to "Cisco". Set to "UDP" if notificationDeliveryMechanism contains "snmp" (case-insensitive). Mapped from either reportingEntityAddress or source if they are not IPs. Mapped from either reportingEntityAddress or source if they are IPs. Extracted using regular expression from source if it is a MAC address. Converted to a label on the principal resource. Converted to a label on the principal resource.
    reportingEntityAddress
    		principal.ip , principal.hostname If it's an IP address, mapped to principal.ip . Otherwise, mapped to principal.hostname .
    severity
    		security_result.severity Mapped based on these conditions:
    "CRITICAL" if severity is "0", "1", "CRITICAL", or "VERY-HIGH".
    "HIGH" if severity is "2", "3", "4", or "HIGH".
    "MEDIUM" if severity is "5" or "MEDIUM".
    "LOW" if severity is "6", "7", or "LOW".
    sigAlertDescription
    		security_result.description Directly mapped.
    signatureName
    		target.resource.attribute.labels.signatureName Converted to a label on the target resource.
    source
    		principal.hostname , principal.ip , principal.mac If it's an IP address, mapped to principal.ip . If it's a MAC address, mapped to principal.mac . Otherwise, mapped to principal.hostname .
    srcObjectClassId
    		principal.resource.attribute.labels.srcObjectClassId Converted to a label on the principal resource.
    srcObjectId
    		principal.resource.attribute.labels.srcObjectId Converted to a label on the principal resource.
    subclassName
    		security_result.rule_name Directly mapped. Set to "BLOCK" if applicationSpecificAlarmID contains "BlockList" (case-insensitive) or if eventType is one of "SIGNATURE_ATTACK", "MALICIOUS_ROGUE_AP_DETECTED", or "USER_AUTHENTICATION_FAILURE". Determined by parser logic based on eventType :
    "NETWORK_MALICIOUS" if eventType is "MALICIOUS_ROGUE_AP_DETECTED".
    "NETWORK_SUSPICIOUS" if eventType is "SIGNATURE_ATTACK".
    "AUTH_VIOLATION" if eventType is "USER_AUTHENTICATION_FAILURE".
    timestamp
    		metadata.event_timestamp The seconds and nanos fields are directly mapped.

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

    Create a Mobile Website
    View Site in Mobile | Classic
    Share by: