Preview Tool

Cisco Bug: CSCum79301 - TP tunings are not applied when sig is tuned other than status fields

Last Modified

Nov 11, 2016

Products (1)

  • Cisco Security Manager

Known Affected Releases


Description (partial)

TP tunings are not applied when signature is tuned other than status fields.
As we know, If there are already customer tunings existing before a template is applied, it will be ensured that conflicting tunings if any are resolved with the customer tuning taking precedence. 
However if the customer tuning is other than status fields (enabled/retired) say severity, event action then along with customer tunings say severity/event action, TP tunings will/should also be applied but CSM doesn't apply the TP tunings, it still retains the old status value only.
As there is no tunings done to status fields, TP tunings should be applied even though other parameters are tuned.

Signature id which was included in any of the template should have a user defined tunings other than status field.
Now apply threat profile and check the status field
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.