Cisco Cisco Firepower Management Center 4000 Release Notes

Version 5.2.0.3

Sourcefire 3D System Release Notes

Known Issues

The following known issues were reported in Version 5.2.0.3:

•

If you modify the device configuration on a clustered stack and immediately

apply your changes, the apply fails and the system displays an error

message in the task status queue. The device configuration apply succeeds

after a second attempt. (121625)

•

In some cases, custom intrusion rule classifications referenced by

correlation rules revert to predefined rule classifications after you install an

intrusion rule update. (122163)

•

If you configure a custom analysis dashboard widget based on the

Connection Summary Data table and the Ingress Interface, Ingress Security

Zone, Egress Interface, or Egress Security Zone fields, the widget displays no

data. (122857)

•

If you edit and save your access control policy ten or more times without

applying the changes to your devices and then install a new version of the

Sourcefire 3D System, the system shows your access control policy as

unapplied. To avoid this issue, apply access control policies completely

before installing system updates. (123003)

•

If the DNS entries in your network environment for your LDAP server's

hostname and IP address do not match, LDAP authentication may fail.

(123447)

•

In rare cases, the Defense Center may not back up events onto remote

storage. (124350)

•

In some cases, if you set an operating system identity from the host profile

or network map, the system displays Please wait, loading... even after the

pop-up window has loaded completely. (124918, 128594)

•

In some cases, executing large Nmap scans may cause system issues. As a

workaround, reduce the size of the Nmap scans to include fewer targets.

(124999)

•

If you attempt to install a version of the Sourcefire Geolocation Database

(GeoDB) that is already installed on your system, the system does not

inform you that the update failed because the GeoDB version was already

installed. (125183)

•

If you configure an Nmap scan and specify a device in the Remote Device

Name field, the system runs the scan from the device even if you are using a

remediation where Scan from reporting device is disabled. (125608)

•

In some cases after importing a new intrusion rule update, the number of

imported rules in the intrusion policy may not match the number of rules in

the import log. (125900)