CSO

  Springing forward has never been more of an adventure…  A few weeks ago, I mentioned the importance of security professionals getting the word out in front the new mid-March date for implementing DST. Since then, there’s been a flood of new websites, articles and information available to help governments make it over the hump.

 Yes, there are issues around calendars appointments and other things. If you’re not watching this closely, your late March appointments may already be messed up.

 Oregon has launched an excellent website which guides their state agencies and others in what the problems are what needs to get done.

 Articles have popped-up in Government Technology Magazine which provides advice.

 The Multi-State Information Sharing and Analysis Center (MS-ISAC) released recommendations for dealing with this issue:

• Identify all time dependent applications.
• Update and apply all appropriate patches to applicable systems after appropriate testing.
• Ensure that your users are aware of the change and pay particular attention to calendar entries during the new daylight saving time periods.
• Validate that all critical systems have the correct time after each rotation of DST to mitigate any possible issues on those hosts.

  There’s plenty of information available, but time is short. A Google search on this topic  now yields almost a million results, so more and more people are thinking about the topic.