Cisco Cisco FirePOWER Appliance 7020 Notas de publicación
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Version 5.3.0.3
Sourcefire 3D System Release Notes
39
Features Introduced in Previous Versions
•
When you configure a device inline between a host and a web server, block
the web server by URL in your access control policy, enable the
Cisco-provided block response page, then attempt to access the web server
from the host, a session timeout may result if the open connection limit of
the server’s operating system is reached. (141440/CSCze92753)
•
In some cases, excessive saved revisions to the intrusion policy may cause
system performance issues. (141501/CSCze92792, 141754/CSCze92960)
•
On 3D9900 devices, passive interfaces not in security zones do not
generate intrusion or connection events. As a workaround, create and
specify a security zone for all passive interfaces on this device model.
(141663/CSCze93022)
•
When you edit a saved search, the previously configured name of the
search does not appear in the Name field; the field is empty.
(142060/CSCze93463)
•
When the system sends a file for sandbox analysis and the cloud does not
respond within 50 minutes, the file’s status still appears as Sent for Analysis
instead of indicating that analysis has timed out. (142309/CSCze93757)
•
When you are using two Defense Centers in a high availability configuration,
you cannot generate troubleshooting reports for a Defense Center from the
web interface of its high availability peer. You must generate
troubleshooting reports directly from the Defense Center you need the
reports for. (142645/CSCze93908)
Features Introduced in Previous Versions
Functionality described in previous versions may be superseded by other new
functionality or updated through resolved issues.
5.3.0.x
The following features and functionality were introduced in Version 5.3.0.x:
•
As of Version 5.3.0.1, LDAP usernames are not case-sensitive. In Version
5.3, usernames were case-sensitive.
•
As of Version 5.3.0.1, you can no longer perform joins using the
application_tag_id
field in the
application_host_map
table when
querying the external database.
5.3
The following features and functionality were introduced in Version 5.3: