10-28-2015 12:26 AM - edited 03-11-2019 11:48 PM
Hello,
I am just curious to know why did cisco move from CX module to SFR module?
As far as I know, Sourcefire has been know for it's strong IPS features and SNORT technology. CX module is capable of doing NGFW services. What makes SFR a better solution as compared to CX module? I am just concerned about technical part, not about the business part.
Hoping valubale respones ASAP.
Thanks,
Rakesh Kumar
Solved! Go to Solution.
10-28-2015 08:29 AM
Hello,
ASA CX was developed by Cisco in order to have a product in class of Next Generation Firewalls. The idea was great: they bought IronPort and so that Cisco got one of the best web-proxy servers. After that cisco introduced CX software module for ASA appliances. This module was built on the basics of IronPort web security appliance. Later Cisco added the functions of NGIPS to CX module.
I had a chance to install and work with CX module in 2013 year. And I found out for my self, that CX module had a lot of bugs and doesn't work stable those days. After some years cisco correctred a plenty of bugs, and as far as I know, modern versions of CX module works fine. But the moment was missed. They still needed the NGFW, which is better than competitor's. Moreover, classic Cisco IPS and NGIPS on CX module were not among the leaders on the IT and Security marked.
From my point of view, this situation became the main trigger for buying SourceFIRE company. After creating the sfr module for ASA, Cisco took the first place in gartner magic quadrant for NGFWs.
Also, all Cisco classic IPS were EoS after they had bought SourceFIRE:
ASA CX module became EoS too:
From the technical perspective, from my point of view, we should compare ASA CX with SFR within two classes: as NGFW and as NGIPS.
If comparing the functions within NGFW class, both modules are good. Some functions work better on CX, some - on SFR. For example, AVC is better (only from my point of view) on SFR. SFR can recognice web applications and other types of applications more correct and deeply. But the question of Authentication is better on CX module. On CX module you can configure both Active, Active with SSO and Passive Authentication. On SFR at this moment you can use only Passive Authentication. Decryption policies exists on CX. Decryption for SFR on ASA is in the road map. Reporting works better on SFR. And so on...
If comparing the functions within NGIPS class, SFR is much much better and provide a great number of services, which can help to make the network secure. For example, nework discovery - on SFR with FireSIGH management you can get host profiles for every host in the network. In host profile you can find infos about OSs, Indicators of Compromise, Vulnarablilities and so on. Moreover, SFR can be used with AMP licenses, which introduce the services of antimalware. So that you can search for malware in the files, which are uploaded or downloaded through the SFR module.
10-28-2015 08:29 AM
Hello,
ASA CX was developed by Cisco in order to have a product in class of Next Generation Firewalls. The idea was great: they bought IronPort and so that Cisco got one of the best web-proxy servers. After that cisco introduced CX software module for ASA appliances. This module was built on the basics of IronPort web security appliance. Later Cisco added the functions of NGIPS to CX module.
I had a chance to install and work with CX module in 2013 year. And I found out for my self, that CX module had a lot of bugs and doesn't work stable those days. After some years cisco correctred a plenty of bugs, and as far as I know, modern versions of CX module works fine. But the moment was missed. They still needed the NGFW, which is better than competitor's. Moreover, classic Cisco IPS and NGIPS on CX module were not among the leaders on the IT and Security marked.
From my point of view, this situation became the main trigger for buying SourceFIRE company. After creating the sfr module for ASA, Cisco took the first place in gartner magic quadrant for NGFWs.
Also, all Cisco classic IPS were EoS after they had bought SourceFIRE:
ASA CX module became EoS too:
From the technical perspective, from my point of view, we should compare ASA CX with SFR within two classes: as NGFW and as NGIPS.
If comparing the functions within NGFW class, both modules are good. Some functions work better on CX, some - on SFR. For example, AVC is better (only from my point of view) on SFR. SFR can recognice web applications and other types of applications more correct and deeply. But the question of Authentication is better on CX module. On CX module you can configure both Active, Active with SSO and Passive Authentication. On SFR at this moment you can use only Passive Authentication. Decryption policies exists on CX. Decryption for SFR on ASA is in the road map. Reporting works better on SFR. And so on...
If comparing the functions within NGIPS class, SFR is much much better and provide a great number of services, which can help to make the network secure. For example, nework discovery - on SFR with FireSIGH management you can get host profiles for every host in the network. In host profile you can find infos about OSs, Indicators of Compromise, Vulnarablilities and so on. Moreover, SFR can be used with AMP licenses, which introduce the services of antimalware. So that you can search for malware in the files, which are uploaded or downloaded through the SFR module.
12-27-2015 08:46 PM
Thanks for the reply Boris.
Do you have more information to share on technically differentiating between CX and SFR?
12-27-2015 11:08 PM
Hello,
I just want to add, that with new version of SFR (6.0.0.0 was released in November 2015) Active Authentication, integration with Cisco ISE and Decryption were introduced for Cisco ASA and its SFR module. For more information, see the Relase Notes:
Unfortunately I don't have the document, which can show technical differences between CX and SFR, and I'm not sure if such document exists.
You can find more information about SFR module here (Documentation Roadmap):
http://www.cisco.com/c/en/us/td/docs/security/firepower/roadmap/firepower-roadmap.html
12-28-2015 08:17 AM
Thanks for the helpful information Boris.
I think all we need is the practical working experience to figure out how they behave when implemented in a real environment.
12-28-2015 11:12 PM
Yes, sure.
If you have ASA appliance with SSD disk, you can install sfr module:
and FireSIGHT System to control SFR:
If the links above are not available for you, you can ask your Authorized Cisco Reseller or Representative to provide the software for you for testing purposes.
You will need also to ask Cisco Representative to provide trial licenses for you for testing purposes.
If you don't have ASA with SSD disk, which you can use for testing, you can deploy a Virtual IPS Sensor for VMWare ESXi host:
It has almost the same functionality, as SFR module.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide