2-56
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
Relaying Syslog Messages from 3rd-Party Syslog Servers
You can rapidly deploy MARS by forwarding messages from existing syslog-ng or Kiwi syslog servers.
This feature eliminates the network and device changes required to insert MARS into an operational
network. You are no longer required to configure each network device to publish its syslog messages
directly to MARS, which saves time, avoids device change approval processes, preserves packet
processing performance of the network devices, and ensures daily network operations proceed without
interruption. This relay feature also allows the correlation and inspection of syslog messages from
reporting devices, such as those on the DMZ, for which corporate policies might prohibit the existence
of or connection to configuration information.
If your network devices already publish syslog messages to syslog-ng or Kiwi syslog servers, you can
configure those servers to forward messages to the MARS Appliance and identify the syslog servers in
MARS. Currently, MARS parses the syslog messages generated by the following devices: Cisco PIX,
Cisco IOS, Cisco CatOS, Cisco ICS, Cisco ASA, Cisco FWSM, Cisco VPN 3000, Cisco Secure ACS,
Snort IDS, Juniper/Netscreen firewalls, Solaris, Linux, and Microsoft Internet Information Server (ISS),
Microsoft Windows running the SNARE agent. For other devices, you can define custom log parsers.
The MARS Appliance can begin processing and storing the events while you define the reporting devices
using the MARS user interface. You are still required to define the reporting device by IP address and
device type in MARS to ensure proper event correlation; however, you are not required to configure
device to publish syslog messages directly to MARS.
To configure MARS to work with a syslog relay server, perform the following tasks:
1.
Configure the syslog relay server to forward correctly formatted messages to MARS. See
Configure
Syslog-ng Server to Forward Events to MARS, page 2-56
or
Configure Kiwi Syslog Server to
Forward Events to MARS, page 2-57
.
2.
Identify the MARS Appliance as a forward target.
3.
Add the syslog relay server to the MARS user interface. See
Add Syslog Relay Server to MARS,
page 2-57
.
4.
Add the reporting devices monitored by the syslog relay server to the MARS user interface. See
Add
Devices Monitored by Syslog Relay Server, page 2-58
.
Configure Syslog-ng Server to Forward Events to MARS
We recommend the following settings in the configuration options of the syslog-ng.conf file to ensure
good integration of syslog-ng with MARS:
options { long_hostnames(off); use_dns(0); keep_hostname(yes); };
where
•
The long_hostnames(off) setting conforms to RFC 3164, which recommends that the HOSTNAME
does not contain domain name.
•
The use_dns(0) setting ensures that the IP address is used in HOSTNAME rather than the
hostnames.
•
The keep_hostname(yes) setting preserves the original sending device’s HOSTNAME even when it
is relayed more than once.
In addition to configuring the message format, you must specify that the MARS Appliance is a
destination loghost on UDP port 514. The following lines must appear in the syslog-ng.conf file:
destination loghost { udp("
IP address of MARS Appliance
" port(514)); };
log { source(src); destination(loghost); };
Содержание CS-MARS-20-K9 - Security MARS 20
Страница 20: ...Contents xx User Guide for Cisco Security MARS Local Controller 78 17020 01 ...
Страница 356: ...17 16 User Guide for Cisco Security MARS Local Controller 78 17020 01 Chapter 17 Network Summary Summary Page ...
Страница 420: ...20 28 User Guide for Cisco Security MARS Local Controller 78 17020 01 Chapter 20 Queries and Reports Reports ...
Страница 580: ...Glossary GL 4 User Guide for Cisco Security MARS Local Controller 78 17020 01 ...