Cisco Cisco Firepower Management Center 2000 Notas de publicación
23
FireSIGHT System Release Notes
Resolved Issues
Resolved an issue where, if you edited a local rule on the intrusion rule editor when viewing rule documentation, the
system displayed the current local rule configuration for already-generated event data instead of the rule
configuration that triggered it. (145118/CSCze95346)
system displayed the current local rule configuration for already-generated event data instead of the rule
configuration that triggered it. (145118/CSCze95346)
Resolved an issue where, if you backed up and restored a Defense Center, Security Intelligence objects were not
backed up or restored. (CSCur42337, CSCur35624)
backed up or restored. (CSCur42337, CSCur35624)
Resolved an issue on Series 3 managed devices where inline connectivity could be lost for up to 25 seconds on
bypass-enabled inline sets during device reboot. (CSCur64678)
bypass-enabled inline sets during device reboot. (CSCur64678)
Resolved an issue where, in some cases, you were not able to get URL category or URL reputation information.
(CSCur38971, CSCus59492)
(CSCur38971, CSCus59492)
Resolved an issue where the system did not display the associated hosts if you expanded a vulnerability based on
a client application from the vulnerabilities tab of the Network Map. (CSCur86191)
a client application from the vulnerabilities tab of the Network Map. (CSCur86191)
Resolved an issue where, in some cases, the host did not always display the block page if one of your access control
rule actions was set to block or interactive block. (CSCus06868)
rule actions was set to block or interactive block. (CSCus06868)
Resolved an issue where the system did not support generating multiple report types when using Windows File
Sharing (SMB) due to unsupported characters in the report name. (CSCus21871)
Sharing (SMB) due to unsupported characters in the report name. (CSCus21871)
Resolved an issue where, if you create an SSL policy set to Do Not Decrypt and attempted to establish a session,
the system erroneously reported the session was blocked when it was not. (CSCus41127)
the system erroneously reported the session was blocked when it was not. (CSCus41127)
Resolved an issue where, if you placed an access control rule referencing a file policy with a Block Malware rule
positioned after an access control rule with a web application condition, the system did not identify malware files.
(CSCus64393, CSCus64526)
positioned after an access control rule with a web application condition, the system did not identify malware files.
(CSCus64393, CSCus64526)
Resolved an issue where, if both the management interface and the control interface of your system used the same
VLAN and the management interface used an IPv6 address, the management interface was inoperable.
(CSCus64678)
VLAN and the management interface used an IPv6 address, the management interface was inoperable.
(CSCus64678)
Resolved an issue where, if your system included an SSL Visibility Appliance (SSLVA) or a Cisco SSL Appliance and
you created a file policy containing a web application category and a Block Malware rule, your first attempt to
download a file over HTTPS failed. Note that this issue is resolved when the SSL appliance is running Version 3.8.4. ()
you created a file policy containing a web application category and a Block Malware rule, your first attempt to
download a file over HTTPS failed. Note that this issue is resolved when the SSL appliance is running Version 3.8.4. ()
Resolved an issue where the system experiences issues if you applied an access control policy referencing a URL
Filtering license, Security Intelligence license, and an SSL policy configured for inspection on any of the following
devices: the 7000 Series, ASA5506-X, ASA5506H-X, and the ASA5506W-X. (CSCut02823)
Filtering license, Security Intelligence license, and an SSL policy configured for inspection on any of the following
devices: the 7000 Series, ASA5506-X, ASA5506H-X, and the ASA5506W-X. (CSCut02823)
Improved pruning for correlation event tables. (CSCut02984)
Resolved an issue where, if you created a file policy with Spero analysis and file capture enabled, the system did not
capture files detected in incoming traffic. (CSCut06837)
capture files detected in incoming traffic. (CSCut06837)
When an applied access control policy with a rule set has all source IPv4 addresses, the system evaluates traffic with
an IPv6 source address as if source addresses were not set in the rules. When an applied access control policy with
a rule set has all source IPv6 addresses, the system evaluates traffic with an IPv4 source address as if source
addresses were not set in the rules. When an applied access control policy with a rule set has all destination IPv4
addresses, the system evaluates traffic with an IPv6 destination address as if destination addresses were not set in
the rules. When an applied access control policy with a rule set has all destination IPv6 addresses, the system
evaluates traffic with an IPv4 destination address as if destination addresses were not set in the rules. (CSCut48596)
an IPv6 source address as if source addresses were not set in the rules. When an applied access control policy with
a rule set has all source IPv6 addresses, the system evaluates traffic with an IPv4 source address as if source
addresses were not set in the rules. When an applied access control policy with a rule set has all destination IPv4
addresses, the system evaluates traffic with an IPv6 destination address as if destination addresses were not set in
the rules. When an applied access control policy with a rule set has all destination IPv6 addresses, the system
evaluates traffic with an IPv4 destination address as if destination addresses were not set in the rules. (CSCut48596)
Resolved a rare issue where, if a Series 3 device detected traffic targeted for stacked devices, the system
experienced issues and could not process traffic. (CSCut53335)
experienced issues and could not process traffic. (CSCut53335)