AlienVault® USM Anywhere™

Cisco Router

When you configure Cisco IOS routers or Cisco Catalyst switches to send log data to USM Anywhere, you can use the Cisco Router plugin to translate the raw log data into normalized events for analysis.

Device Details
Device vendor Cisco
Device type Router
Connection type Syslog
Vendor link

Integrating Cisco Router

Before you configure the integration, you must have:

  • The IP Address of the USM Anywhere Sensor
  • Router configuration to obtain time from any NTP server

To configure Cisco Router to send log data to USM Anywhere

  1. Enter configuration mode:

    router# conf t

  2. Configure the host to receive syslog messages:

    router(config)# logging host <USM-Anywhere-Sensor-IP-Address>

  3. Configure the host to log the desired traps:

    router(config)# logging traps {0|1|2|3|4|5...}

  4. (Optional) Specify a particular IP address for syslog messages:

    router(config)# logging source-interface Loopback0

  5. (Optional) Display the state of system logging (syslog) and the contents of the standard system logging message buffer:

    router# show logging



    Syslog logging: enabled

    Console logging: disabled

    Monitor logging: level debugging, 266 messages logged.

    Trap logging: level informational, 266 messages logged.

    Logging to

    SNMP logging: disabled, retransmission after 30 seconds

    0 messages logged


Plugin Enablement

The Cisco Router plugin automatically processes all messages whose syslog tag matches the regular expression:




















Note: To use the Cisco Router plugin to process logs from the Cisco Catalyst switches, you need to assign the plugin to the asset, see Manual Plugin Management for details.

Available Plugin Fields

The following plugin fields are important attributes extracted from the syslog message. The USM Anywhere reports use these fields, and you can also reference them when creating custom reports. In addition to reporting, the USM Anywhere correlation rules make use of these fields.

  • customfield_0
  • customheader_0
  • destination_address
  • destination_port
  • device_inbound_interface
  • event_description
  • event_name
  • rep_device_outbound_interface
  • source_address
  • source_port
  • transport_protoco


For troubleshooting, refer to the vendor documentation.