Recently in our WinCurity newsletter we posted a story:
- Compliance & configuration management – Daylight Saving Time – Don’t let your computer fall behind
For the U.S. and Canada, daylight saving time was supposed to happen 2007-03-11. Time synchronisation is a service managed by NIST for most of the U.S.
NIST – National Institute of Standards & Technology (U.S.) is responsible for achieving the following laudable objective:
- GOAL: To provide the foundation of frequency measurements and civil timekeeping for our nation.
Moreover, many information security standards we use in our work were issued by NIST
- NIST – CSRC – Computer Security Guidance / Publications / Library
2007-03-12 (Monday) after Dalight Saving Time should have arrived, many North American users discovered that neither:
- time.windows.com and time.nist.gov serve summer time
Things still seem to fail to work properly until yesterday, just about a week later when NIST time servers had begun again to serve the correct time.
7 days time snchronisation failed in North America for most computer users.
Today we still got:
An error occurred while Windows was synchronizing with time.nist.gov.
But maybe the system is just still trying to cope with the fact that over here in Europe, summer time while not arrive until the last weekend of March 
.
But this synchronization problem indicates that even in organizations that seem to do so many things right such as bringing us the Common Malware Enumeration (CME) or the Common Vulnerabilities and Exposures (CVE), computer assets can go haywire…..