Guest

Preview Tool

Cisco Bug: CSCsg31434 - windows pulling gets old data right after Activate or dbchange.

Last Modified

Feb 22, 2014

Products (1)

  • Cisco Security Monitoring, Analysis and Response System

Known Affected Releases

4.2(2)

Description (partial)

A new issue in windows pulling occurs since MARS 4.2.2.

There is a flaw in implementation of dbchange handling in cswin module, so that whenever GUI "Activate" button is clicked, or dbchange command is issued by backend after scheduled discovery is done, and if there are no changes (reporting IP, username, password) in correctly pulled windows servers, old windows event log data will be pulled although they should not be.


Symptom:

Old windows event logs are pulled into MARS database, which results in duplicated events and possibly duplicated incidents. If there are large amount of event log entries, a temporary traffic spike between MARS and the pulled windows machines can be observed.

Conditions:

This issue starts occuring in 4.2.2.

Whenever GUI "Activate" button is clicked, or dbchange command is issued by backend after scheduled discovery is done (as in the 1:05 AM spike noticed by customer), and if there are no changes (reporting IP, username, password) in correctly pulled windows servers, old windows event log data will be pulled although they should not be.
Bug details contain sensitive information and therefore require a Cisco.com 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.