6. Reports and Logs

Last Updated

The slot machine server report requirements of this section may be satisfied by the slot machine server and/or the slot accounting/monitoring system.

6.1  Server Requirements for Reports and Audit Logs

6.1.1  Logical access to the slot machine server shall be logged on the server and on a secondary logging device which resides outside the server room and is not accessible to the individual accessing the server room. This information is not required to be logged on the secondary logging device if the information has been rendered unalterable on the server. Logged data shall include time and date of the access and the identification of the accessing individual(s). The resulting logs shall be retained for a minimum of ninety days.

6.1.2  A slot machine server must create a log entry, at a minimum, every time any critical software component is added, removed or altered including any configuration or paytable/game theme changes in the slot machine server, which must contain:

  1. The date and time of the action;
  2. Identification of the software affected, both removed and installed;
  3. The names and unique identification (e.g. registration ID) of the individuals performing the modification; and
  4. The reason for the modification and any pertinent validation information.

6.1.3  The slot machine server must create a log entry whenever any change is made to software in a server-assisted slot machine or client station, including but not limited to software programs, graphics, sound information paytable/game theme, and configuration changes. This log entry must contain the date and time of the event, an identification of the software affected, the name of the individual performing the modification, and any pertinent software identification information. The log entries must be retained on the slot machine server for a minimum of ninety days; provided that logged events older than ninety days can be retained.

6.1.4  The slot machine server must be capable of generating a record detailing any software modification to the slot machine server, or, if not capable of generating such a record, an alternative method of record keeping must be performed.

6.1.5  The slot machine server must generate daily monitoring logs with the date and time of:

  1. User access; and
  2. Any other logged events which reasonably indicate that the system is not operating as expected, e.g. memory corruption, authentication failure.

6.1.6  The slot machine server must be capable of maintaining the logs on the slot machine server and the other logging device referenced in sections 6.1.1, 6.1.2, 6.1.3 and 6.1.4 above, for a minimum of ninety days.

6.1.7  The slot machine server must be capable of retaining a record and generating a report pursuant to section 6.2.1 and 6.2.2 below of all titles of all active games offered on all server-assisted slot machines or client stations, and all changes made to any of the games, for each twenty-four hour period the games are in operation.

6.2  Server-Assisted Slot Machine and Client Station Requirements for Reports and Audit Logs:

6.2.1  Whenever any change is made to software in a server-assisted slot machine, including but not limited to software programs, graphics, sound information, paytable/game theme, or config- uration changes, a log entry must be made on the server-assisted slot machine which must contain the date and time of the event and an identification of the software affected. The logs must be capable of being retained on the server-assisted slot machine for a minimum of 100 logged events.

6.2.2  Whenever any change is made to software in a client station, including but not limited to software programs, graphics, sound information, paytable/game theme, or configuration changes, a log entry must be made which must contain the date and time of the event and an identification of the software affected. This log entry must be made either on the client station, or on a secondary logging device which resides outside the server room and is not accessible to the individual making the program modification. This information is not re- quired to be logged on the secondary logging device if the information has been rendered unalterable on the server.

6.3  General Requirements for Reports and Audit Logs:

6.3.1  Each report contained herein must include the report title and date and time the report was generated. The slot machine server must be able to generate reports with all or any subset of the following information as it pertains to the system:

  1. User access rights by user and by role;
  2. System configurations;
  3. List of all active gaming devices;
  4. List of all deactivated gaming devices;
  5. All software installed on the slot machine server;
  6. All games and paytables installed on the slot machine server;
  7. All games and paytables active on the gaming floor with location and gaming device infor- mation;
  8. All game and paytable changes to be reported in daily, weekly and monthly periods; and
  9. A report of all progressive jackpots listing the participating games.

6.3.2  All information required to be logged pursuant to this section must be available on demand in a report format. Each log report required herein must include the report title and the date and time the report is generated. Where applicable, audit logs must include the source and destination IP addresses, port numbers and MAC addresses. At a minimum, the following log reports must be available and include the information in the referenced requirement:

  1. A firewall log report;
  2. A software integrity log report pursuant to section 2.1.2b) above;
  3. A slot machine server log report pursuant to sections 6.1.2, 6.1.4 and 6.1.5 above;
  4. A server-assisted slot machine and client station log report pursuant to sections 6.1.3 and 6.2.1 above;
  5. A daily monitoring log report pursuant to section 6.1.5 above;
  6. A scheduling log report pursuant to sections 3.1.2 and 6.3.1c) above;
  7. A server-assisted log report pursuant to section 6.1.7 above;
  8. A server-based log report pursuant to section 6.1.7 above; and
  9. Software authentication log reports pursuant to section 2.1.2 above
  10. Progressive jackpot reconciliation reports or alternative means of enabling reconciliation to be performed must be available for each progressive jackpot level and must include suffi- cient information to enable reconciliation to be successfully performed for each progressive level.