1. (a) These minimum technical rules shall be met, where applicable, when downloading/activating control programs from the CSS Server to the client terminal.

2. (b)

   1. (1) The client terminal and/or the CSS server must have a method to monitor and report to the MCS all external door access during a foreground program download and/or activation process.
   2. (2) If the CSS does not have the ability to monitor the door access during the foreground program download and/or activation process, an independent test laboratory’s report shall indicate as such so that internal controls can be developed to ensure the security of the client terminal’s security, primarily with regard to the cash compartments, where applicable.

3. (c) Below are the methods to store the current game data that is pertinent to the individual client terminal when updating the control program in an SSGS configuration:

   1. (1)

      1. (A) Where applicable, the game data is uploaded and security stored on the CSS server and is maintained:

4. (i) For a minimum of twenty-four (24) hours and archived after that time; or

   1. (ii) In a log or script file.

      1. (B) If this method is used, the process in downloading the new control program to the client terminal must ensure that all critical areas of memory are overwritten by a default value;
   2. (2) The game data is maintained at the client terminal; or

   3. (3)

      1. (A) If the CSS is not capable of meeting the above rule, regulatory control may be required on the CSS server for new client terminal control program downloads.
      2. (B) In addition, the alternate methods used will be reviewed by an independent test laboratory and the Arkansas Racing Commission on a case-by-case basis.

Codification Notes: “CSS” means client-server system. "SSGS" means system-supported game systems.