Accenture MDR Quick Start Guide for Cisco Firepower Threat Defense (FTD) using Syslog configuration

This quick start guide will help Accenture MDR customers configure Cisco Firepower Threat Defense (FTD) to send logs to the Log collection Platform (LCP).

This document includes the following topics:

Supported Versions

A list of supported versions is available in the Accenture MDR Supported Products List document (Accenture_MDR_Supported_Products_List.xlsx) which can be found in Accenture MDR Portal.

Port Requirements

Table 1-1: Port requirements for LCP communication.

Configuring Cisco FTD

You have to configure the below settings to send the FTD events

To configure Audit Log Messages 

1. Log in to the Cisco Firepower management center console.

2. Navigate to Devices > Platform Settings

3. ​Click Audit Log.

4. Select Enabled from the Send Audit Log to Syslog drop-down menu.

5. Enter the Syslog IP Address or fully qualified host name of the syslog server in the Host field.

6. Select Syslog from the Facility drop-down menu. 

7. Select INFO from the Severity drop-down menu

8. Click Save.   

 To Configure Syslog Alerts:

1. Navigate to Policies > Actions > Alerts,.

2. Create a new syslog object for MDR.

3. Enter the Name for syslog server object.

4. Enter the LCP IP Address in the Host field.

5. Enter the Port 514 in the Port field.

6. Select Local 4 from the Facility drop-down menu. 

7. Select INFO from the Severity drop-down menu. 

8. Click Save.

9. Apply the created object to the rest of the tabs.

Syslog settings for the FTD device:

1. Navigate to Devices > Platform Settings > FTD Device > Syslog

2. Under Logging Setup, check the following:

• Check the Enable Logging and Enable logging on the failover standby unit

• Check the send syslog in EMBLEM format

• Check the Send debug messages as syslogs

• Set the memory size of the internal buffer.                                                                  

  Open

  

  NOTE: MxDR doesn't support Names feature. This feature needs to be kept disabled. 

• To send syslog messages in Emblem format - enable checkbox for "Send syslog in EMBLEM format" to start receiving logs in emblem format.

• Cisco Emblem log forwarding will only be supported by UDP. It does not support TCP as per vendor.

• Current handling of emblem format is based on versions : versions 7.0.5 and later, and 7.2.x and later. Emblem format for previous versions might change and may not be supported by collector.

Open

3. Under logging destinations, create a new syslog destination by clicking Add or edit the required logging destination from the list.                                                                

•  Choose the syslog servers as logging destination from the Logging Destination drop-down.

• Choose Filter on Severity from the Event class drop-down and choose debugging as the logging level.

• To add the below event classes to this Logging filter, click Add under the Event list tab.

• Choose the Event Class from above list in the Event Class drop-down list.

•  Choose the Syslog severity from the Syslog Severity drop-down list. 

4. Under Rate Limit tab, select the logging level and enter the Number of messages.

5. Under Syslog Settings tab,

• Select the Facility as LOCAL 4 from drop-down menu.

• Check Enable timestamp for syslog messages box

• Select the Timestamp Format as RFC 5424 (yyyy-MM-ddTHH:mm:ssZ) from drop-down menu.

• Check the Enable syslog ID as Host name.

• Enable the Syslog ID's as need.

6. Under syslog server tab,

• Select the LCP IP address from the drop-down menu.

• Choose the protocol as TCP or UDP

• Enter the port number as 514/601

• Check Device management Interface.

• Click OK.                                                                        

 Configuring Syslog Alerting for Access Control

1. Navigate to Access Control.

2. Enable the Access policy to send logs to Syslog

3. Check the box Log at End of Connection

4. Select Log files as File events . 

5. Send the connection events to Syslog server                                                                           

Configuring File Events

1. Navigate to Policies >> Malware & File and create a file policy.                                                                 

Note: Select Log Files in order to enable logging of prohibited files or malware events. File policy must be selected in the rule to configure this option. The option is enabled by default if a file policy is selected for the rule. Cisco recommends to leave this option enabled

  2. Select the Inspection tab and choose already created file policy under MDR drop down menu

3. The log file is automatically highlighted and checked. Log file selection is optional.                                   

Configuring Syslog Alerting for Intrusion Events

1. Under the intrusion policy editor's navigation pane, click Advanced Settings. 

2. Make sure Syslog Alerting is enabled and click Edit

Note: A message at the bottom of the page identifies the intrusion policy layer that contains the configuration. The Syslog Alerting page is added under Advanced Settings.                                                       

3. Enter the IP Address of the Logging Hosts where you want to send syslog alerts

Note: If the Logging Hosts field is left blank, the logging hosts details are taken from the Logging tab in the associated Access Control Policy.

4. Choose Facility and Severity levels as described in below.

5. To save the changes, choose Policy Information, then click Commit Changes.

LCP Configuration Parameter

Table 1-2 : The Cisco FTD syslog event collector (Syslog -5003) properties to be configured by MDR are shown in the table