Daylight Savings Time (DST) 2007 Information

• Situation
• Impact
• Solution
• Frequently Asked Questions
  

Situation:

The United States has planned a change to its Daylight Saving Time (DST) observance beginning in 2007. The Energy Policy Act of 2005 mandates that DST will start on the second Sunday in March and end on the first Sunday in November. In 2007, the start and stop dates will be March 11 and November 4, respectively. These dates are different from previous DST start and stop dates. In 2006, the dates were the first Sunday in April (April 2, 2006) and the last Sunday in October (October 29, 2006).

This change affects the DST 2007 rules for North America (U.S. and some regions in Canada), except for Mexico. Mexico will not be following the updated DST 2007 rules.

Impact:

Affected versions of Application Security’s products will have recorded time stamps displayed and stored incorrectly by a difference of 1-hour for the window of time between the original DST dates and the new DST dates. Thus, the 1-hour difference will start on the first day that the new DST rules go into effect and will correct itself on the day of the previous start of start of Daylight Saving Time, April 2, 2007. The issue will present itself again during the later window of the DST change from October 29, 2007 through November 4, 2007.

All of Application Security, Inc.'s latest products properly adhere to the 2007 changes in DST. The following is a list of our compliant products and versions.

• AppSecInc Console for AppDetective version 3.0 and above
• AppRadar version 3.0 and above
• AppDetective, all versions are compliant (operating system patches are necessary, see below)
  

Earlier versions of AppSecInc Console for AppDetective and AppRadar were shipped with Java Runtime Environments (JRE) that Sun Microsystems says are not compliant with the new US DST rules.

To determine if your Application Security products are affected, please follow the simple process below.

Solution:

Step 1: Check Your Software Version

1. Open your browser and connect to the established URL of your product
2. Supply your authentication credentials
3. Navigate to Help > About. The version number will be displayed as a format similar to this: 3.0.xyz
4. If the version number is 3.0 or greater, then no further action is required. If the version number is prior to 3.0, please follow the instructions below in Step 2: Becoming DST Compliant.

1. Open your browser and connect to the established URL of your product
2. Supply your authentication credentials
3. At the bottom of each page, you will find a footer that contains the version similar to this:
   © 2007, Application Security, Inc. All Rights Reserved
   ver: 3.2.0 (build 214)


4. If the version number is 3.0 or greater, then no further action is required. If the version number is prior to 3.0, please follow the instructions below in Step 2: Becoming DST Compliant.
   

AppDetective

1. No action is required.

1. Versions prior to 3.0 of AppSecInc Console for AppDetective and AppRadar were shipped with Java Runtime Environments (JRE) that Sun Microsystems says are not compliant with the new US DST rules.
   
   To update the Java Runtime Environments to be DST Compliant, please refer to these details from Sun: http://java.sun.com/developer/technicalArticles/Intl/USDST/
   
   
2. Each operating system that AppDetective, and an AppRadar sensor are installed on must be updated in accordance with the operating system vendors. Below are the links to the operating system vendors DST compliance information.
   
   Microsoft Windows:
   http://www.microsoft.com/windows/timezone/dst2007.mspx
   
   Solaris Operating Systems:
   http://sunsolve.sun.com/search/document.do?assetkey=1-26-102775-1
   
   Red Hat Linux:
   http://kbase.redhat.com/faq/FAQ_80_7909.shtm

If there are any concerns, please contact AppSecInc Customer Support at support@appsecinc.com or by phone at (212) 912-4159. If you have not already upgraded to the latest versions of AppSecInc software and would like assistance in doing so, please contact your Account Manager or AppSecInc Customer Support.