Cisco Cisco Firepower Management Center 4000 發佈版本通知

Version 5.2.0.3

Sourcefire 3D System Release Notes

33

Features Introduced in Previous Versions

In rare cases, the system does not terminate a rule update installation if the 

installation fails in an early stage. If this occurs, you should attempt a rule 

update reinstallation and contact Support if the issue persists. (125368)

In some cases, enabling sensitive data detection in your intrusion policy 

may not generate events for all packets containing sensitive data. (125588)

If a managed device processes traffic only from the initiator of a TCP 

connection, the system does not log a connection event at the end of the 

connection. (126040)

If you create a custom saved search for intrusion events with the Generator 

(GID) field populated, the search returns empty. (126109)

In some cases after completing a scheduled rule update import and 

subsequent intrusion policy reapply, Defense Centers in a high availability 

configuration may incorrectly show intrusion policies as out-of-date. 

(126670)

If you create a custom analysis dashboard widget based on a saved 

connection event search that uses data in fields without an asterisk (

*

), the 

widget displays incorrect data. Only the fields that constrain connection 

summaries can constrain custom analysis dashboard widgets based on 

connection events. (127324, 127327)

If you register a managed device as the only device on a Defense Center 

with an existing custom network discovery policy configuration, the device 

does not detect hosts or users until you edit, modify, and reapply the 

existing network discovery policy. (127633)

If you apply a VPN deployment on a stack, cluster, or clustered stack and 

then unregister the stack, cluster, or clustered stack from its managing 

Defense Center, the VPN deployment remains active on the stack, cluster, 

or clustered stack when you register the appliances to another Defense 

Center. Additionally, you cannot manage the VPN deployment from the new 

Defense Center. As a workaround, remove the VPN deployment from the 

stack, cluster, or clustered stack before unregistering it from the Defense 

Center. (128816, 130728)

In some cases, the system experiences issues with user account 

management if devices running Version 5.1.1.x are managed by a Defense 

Center running Version 5.2.x.x. As a workaround, update your managed 

devices to Version 5.2. (130024)

Features Introduced in Previous Versions

No new features were introduced in Version 5.2.0.3. Functionality described in 

previous versions may be superseded by other new functionality or updated 

through resolved issues.