1. (a) flash download functionality shall be, at a minimum, password-protected and should be at a supervisor level. The MCS can continue to locate and verify versions currently running, but the MCS is not permitted to load code that is not currently running on the system without user intervention;
2. (b) an audit log shall record the time and date of a flash download and some provision shall be made to associate such log with the version, or versions, of code that was downloaded and with the user who initiated such download. A separate flash audit log report is recommended; and

3. (c) all modifications to the download-executable or flash file or files shall be submitted to and licensed independent testing laboratory for approval. Such approved laboratory shall perform a flash download to the system existing at such approved laboratory and verify operation. Such approved laboratory shall then assign signatures to any relevant executable code and flash file or files that can be verified by a commission representative in the field. Additionally, each flash file shall be available to the commission to verify the signature of such file.

   Subdivisions (a) through (c) of this section refer to loading of new system-executable code only. Other program parameters may be updated so long as the process is controlled securely and subject to audit.

If supported, a MCS may use flash technology to update interface element software if all of the following requirements are met: