2-54
User Guide for Cisco Security MARS Local Controller
78-17020-01
Chapter 2 Reporting and Mitigation Devices Overview
Integrating MARS with 3
rd
-Party Applications
•
System Rule: Security Posture: Vulnerable Host Found
For information on configuring reporting devices and mitigation devices with NAC support, see
Enable
NAC-specific Messages, page 3-4
.
Integrating MARS with 3
rd
-Party Applications
MARS provides multiple integration methods with 3
rd
-party applications. The following topics describe
how to integrate using these methods:
•
Forwarding Alert Data to 3
rd
-Party Syslog and SNMP Servers, page 2-54
•
MARS MIB Format, page 2-54
•
Relaying Syslog Messages from 3rd-Party Syslog Servers, page 2-56
Forwarding Alert Data to 3
rd
-Party Syslog and SNMP Servers
You can forward alert data from MARS to third-party syslog and SNMP servers. The data is forwarded
on a per rule basis. In other words, you must configure those rules for which you want to forward alert
data to include either SNMP, syslog, or both as a notification methods. When a rule fires, the
notifications will be sent in the selected formats to the specified recipients, which should be the desired
servers in the case of SNMP and syslog.
For more information on configuring notification methods for a rule, see
Setting Alerts, page 21-23
. To
learn more about the SNMP MIB format sent by MARS, see
MARS MIB Format, page 2-54
.
MARS MIB Format
The MARS management information base (MIB) is defined for all MARS releases. The SNMP
notification contains the same content as the syslog generated by MARS.
The MARS MIB definition is as follows:
enterprises.16686.1.0 string “MARS-1-101”
enterprises.16686.2.0 string “<alert_content>”
enterprises.16686.3.0 string "<optional_port_list_for_sudden_traffic_increase_incident>"
The MARS private enterprise number is 16686 and <alert_content> is defined as follows:
<<priorityInfo>> <current_time> %MARS-1-101: Rule <ruleid> (<rulename>) fired and caused
<color> Incident <incidentId>, starting from <starttime> to <endtime>.
In the following two examples of the SNMP notification output, 10.1.1.1 is the IP address of the MARS
Appliance:
SNMPv2-SMI::enterprises.16686 10.1.1.1 SNMPv2-SMI::enterprises.16686.1.0 "MARS-1-101"
SNMPv2-SMI::enterprises.16686.2.0 "<34>Mon Apr 28 20:11:43 2003 %MARS-1-101: Rule 45513
(Nimda Attack) fired and caused red Incident 12265001, starting from Mon Apr 28 19:58:47
2003 to Mon Apr 28 20:11:21 2003"
SNMPv2-SMI::enterprises.16686 10.1.1.1 SNMPv2-SMI::enterprises.16686.1.0 "MARS-1-101"
SNMPv2-SMI::enterprises.16686.2.0 "<34>Wed Mar 14 12:28:24 2007 %MARS-1-101: Rule 489722
(System Rule: Sudden Traffic Increase To Port) fired and caused red Incident 204368256,
starting from Wed Mar 14 12:28:14 2007 to Wed Mar 14 12:28:14 2007"
SNMPv2-SMI::enterprises.16686.3.0 "sudden traffic increase to ports: 445 "