Rsa Netwitness Platform: Cisco Firepower and Sourcefire Defense Center
Rsa Netwitness Platform: Cisco Firepower and Sourcefire Defense Center
Note: RSA is qualifying support for the major version. In case of any configuration changes or logs not
parsing in a minor version, please open a case and we will add support for it.
2
Event Source Log Configuration Guide
Configure Sourcefire/Firepower
I. Configure Syslog Output on Sourcefire
II. Configure Sourcefire to Send Intrusion and AMP Events
III. Configure Audit Logging
IV. (Optional) Configure Health Monitoring Alerts
2. Connect to the Defense Center web management console and log in.
3. Depending on your version of Sourcefire Snort, do one of the following:
l For versions 4.6, 4.8, or 4.9, click Policy & Response > Responses > Alerts.
l For version 5.0 and higher, click Policies > Action > Alerts.
a. Select Syslog from the drop down box.
b. In the Name field, enter a name for the Alert (for example, Sourcefire48).
c. In the Host field, enter the IP address of the RSA NetWitness Log Decoder or
Remote Log Collector.
d. In the Port field, type 514.
e. In the Facility drop down list, select USER.
f. In the Severity drop down list, select the level of alerts you want to send to
RSA NetWitness Platform.
g. In the Tag field, enter a tag name (for example, Sourcefire48).
3 Configure Sourcefire/Firepower
Event Source Log Configuration Guide
h. Check the Active check box.
Note: In version 5.0 and higher, please skip 4h. There is no Activebox to be
checked.
i. Click Save to apply the changes.
Note: If you choose to configure Health Monitoring alerts, use the name of the
alert you created in this step.
5. Depending on your version of Source Fire Snort, do one of the following:
l For versions 4.6, 4.8, or 4.9, click Policy & Response > Responses > Impact
Flag Alerts in the top menu bar.
b. Click Save to apply the changes.
7. Depending on your version of Source Fire Snort, do one of the following:
l For versions 4.6, 4.8, or 4.9, click Policy & Response > Responses > RNA
Event Alerts in the top menu bar.
8. In the Event area, do the following:
b. Click Save to apply the changes.
3. Click on the policy for which you want to send alerts.
4. Edit the rule for which logging needs to be activated.
5. Click on the Logging tab.
Note: To assign Intrusion and File policy, use the Inspection tab (located to the left of
the Logging tab in the menu bar).
3. Create a new policy, or edit an existing one.
4. Set the audit log settings as follows:
Field Action
Host Enter the IP address of your RSA NetWitness Platform Log
Decoder or RSA NetWitness Platform Remote Log
Collector.
Facility Select AUTH or choose a value that fits the needs of your
organization.
Severity Select INFO or choose a value that fits the needs of your
organization.
5. Save the policy and exit.
Note: For version 5.0 and up, hover over the Health tab in the top menu bar to show
its options.
4. In the Health Alert Name field, enter the name for your health alert.
5. Select severity and modules based on kind of messages that you want to send to
RSA NetWitness Platform
Note: Select all severities and modules to get the maximum set of messages.
7. Click Save to apply the changes.
l Configure Syslog Collection
2. In the Services grid, select a Log Decoder, and from the Actions menu, choose View
> Config.
3. In the Service Parsers Configuration panel, search for your event source, and ensure
that the Config Value field for your event source is selected.
Note: The required parser is snort.
Note: You only need to configure Syslog collection the first time that you set up an event
source that uses Syslog to send its output to NetWitness.
You should configure either the Log Decoder or the Remote Log Collector for Syslog. You
do not need to configure both.
2. In the Services grid, select a Log Decoder, and from the Actions menu, choose View
> System.
3. Depending on the icon you see, do one of the following:
l If you see , click the icon to start capturing Syslog.
l If you see , you do not need to do anything; this Log Decoder is
already capturing Syslog.
2. In the Services grid, select a Remote Log Collector, and from the Actions menu,
choose View > Config > Event Sources.
3. Select Syslog/Config from the drop-down menu.
The Event Categories panel displays the Syslog event sources that are configured, if
any.
4. In the Event Categories panel toolbar, click +.
The Available Event Source Types dialog is displayed.
5. Select either syslog-tcp or syslog-udp. You can set up either or both, depending on
the needs of your organization.
7. Enter 514 for the port, and select Enabled. Optionally, configure any of the
Advanced parameters as necessary.
Click OK to accept your changes and close the dialog box.
Once you configure one or both syslog types, the Log Decoder or Remote Log Collector
collects those types of messages from all available event sources. So, you can continue
to add Syslog event sources to your system without needing to do any further
configuration in NetWitness.
Copyright © 2019 Dell Inc. or its subsidiaries. All Rights Reserved.
Trademarks
For a list of RSA trademarks, go to www.emc.com/legal/emc-corporation-
trademarks.htm#rsa .