Cisco Cisco Firepower Management Center 2000

Seite von 36
3
FireSIGHT System Release Notes
New Features and Functionality
bypass function to allow traffic to continue flowing through the appliance when there is a loss of power. The ISA 3000 
can be managed as a standalone device or a managed device. You manage standalone ASA FirePOWER modules 
through ASA FIREPOWER Configuration in ASDM and managed ASA FirePOWER modules with a Defense Center.
Terminology
If you reference documentation for Version 5.3.1.x or Version 5.3.0.x, you may notice the terminology differs from the 
documentation for Version 5.4.0.3 and Version 5.4.1.2.
Cisco
Formerly Sourcefire
FireSIGHT System
Formerly Sourcefire 3D System
Defense Center
FireSIGHT Defense Center
Cisco FireSIGHT Management Center
Formerly Sourcefire Defense Center
device
managed device
Formerly Sourcefire managed device
Cisco NGIPS for Blue Coat X-Series 
Formerly Sourcefire Software for X-Series
FireSIGHT managed devices
Refers to all devices managed by a FireSIGHT Defense Center (managed devices 
and ASA devices)
Cisco Adaptive Security Appliance (ASA)
ASA device
Refers to the Cisco ASA hardware
Cisco ASA with FirePOWER Services
Refers to ASA devices with the ASA FirePOWER module installed
ASA FirePOWER module
Refers to the hardware and software modules installed on compatible ASA 
devices
ASA software
Refers to the base software installed on Cisco ASA devices
Adaptive Security Device Management 
(ASDM)
Refers to the Adaptive Security Device Manager used to manage ASA 
functionality
Direct management
Refers to management of the ASA FirePOWER module on the ASA5506-X using 
ASDM
Centralized management
Refers to management of the ASA FirePOWER module on the ASA5506-X using 
a FireSIGHT Defense Center
Tip: 
Cisco documentation may refer to the Defense Center as the FireSIGHT Management Center. The Defense Center 
and the FireSIGHT Management Center are the same appliance.
Changed Functionality
You must apply the same access control policy to all devices that you plan to stack or cluster before you configure 
the stack or cluster.
You are now able to choose to not inspect traffic during policy apply to prevent network disruption.
The system no longer reports the discovery event status to the Health Policy page.
Table 1
Changes to Terminology 
Version 5.4.0.3 and Version 5.4.1.2 
Terminology
Description