On -line logs. The hub shall produce a daily log to the commission on request. The hub must produce at a minimum the following logs in a format prescribed by the commission:

1. (1) Teller/machine history log showing for every wagering device operated during a performance:

   1. (a) Each time the wagering device was opened and closed;
   2. (b) Each wagering transaction, the wagers made, tickets issued, and total value of the transaction;
   3. (c) Each cashing, canceling, or refunding transaction, the identification numbers of the tickets processed, the wagers paid out, and the value of the wagers paid out;
   4. (d) Any special function, including teller balance, accessed through the wagering device; and
   5. (e) The times of day each of the transactions listed in this subdivision were made;
      [if !supportLineBreakNewLine]
      [endif]

2. (2) A ticket history log showing for every ticket issued:

   1. (a) The identification number of each cashed or canceled ticket;
   2. (b) The wagering device location and number;
   3. (c) The wagers and the amount of each wager;
   4. (d) The cashing or canceling machine location and number;
   5. (e) The amount paid out;
   6. (f) The time of day each transaction occurred; and
   7. (g) An indication as to whether each transaction was manual or automatic;

3. (3) A user terminal log showing the time of day of each entry for each:

   1. (a) Terminal other than a wagering device operating during a day including each:

      1. (i) Log-on and log-off and the operator's ID code;
      2. (ii) Command or transaction entered;
      3. (iii) Stop betting, order of finish, official, and sales open command and the device that issued it;
      4. (iv) Occurrence of loss or restoration of communication between computers or sites; and
      5. (v) Occurrence of discrepancy between computers or sites when comparing databases; and

   2. (b) Wagering device operated during a performance including each:

      1. (i) Log-on and log-off and the teller's ID code, if applicable; and
      2. (ii) Instance of loss or restoration or communication and the wagering device;
4. (4) A system error log showing the date and time of each error;

5. (5) A system journal log, including date and time of each entry, including remote access, showing for every day the system is operated for wagering, maintenance, or other purpose:

   1. (a) System shutdown commands, the device from which the commands were issued, and the user ID of the individual issuing the commands;
   2. (b) The individual user ID used and the originating device for every attempt, successful or unsuccessful, to access the operating system;
   3. (c) The individual user ID used and the originating device for every attempt, successful or unsuccessful, to access the application programs;
   4. (d) All commands that affect the operating environments issued from the operating system command line;
   5. (e) All commands issued from within the application program in an attempt to access the operating system; and
   6. (f) A listing of every operational or operating terminal during computer operations; and

6. (6) An account history log showing for every account:

   1. (a) The identification number of the account;
   2. (b) Each time the account was accessed, the location and time of each access point;
   3. (c) For each wagering transaction, the amount, time, betting interest selected, and type of wagers made, the wagering device used to make the wager, and total value of the transaction;
   4. (d) For each cashing, canceling, or refunding transaction, the identification numbers of the tickets processed, the wagers paid out, the location and time and the value of the wagers paid out; and
   5. (e) For each withdrawal and deposit the amount, the location and time.

Source: 34 SDR 200, effective January 29, 2008.

General Authority: SDCL 42-7-56(13 )( 16).

Law Implemented: SDCL 42-7-56(16) , 42-7-58.1.