Threat Response Updates will generally be a week or 2 behind the sensor signature update (so generally one sig level behind the sensor updates). This is because of the extra work involved in determining how to validate if a host on the network has been compromised by the new vulnerabilities being detected by the new signatures.
NOTE: The Threat Response GUI can display the alarms for the new signatures, it is just the additional analysis that is not done for these alarms until the Threat Response update is available.
For this particular update, the update was an additional few weeks behind because of bug fixes that were having to be done in the product.
The 2.0.2 update for Threat Response was released today and covers the signature updates through S57.
Thanks, I did see a new version was released yesterday. Unfortunately, I'm having problems upgrading, and have an open case with TAC. When I run the setup, it says that the upgrade was interrupted before your new software was fully installed. Any idea about this? I had no problems with it and no problems upgrading prior to this.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :