6.1.1 All significant events must be communicated from Player Terminal to the Backend System in real time or as soon as it becomes technically possible. The significant events include, but are not limited to: Player Terminal security events and error conditions, Game transactions and Game configuration changes.
6.1.2 The data communicated to/from the Player Terminal must be validated for proper logic and/ or sequence, before the Player Terminal determines its action, e.g. a bill stacked message cannot be the first message for bill acceptance and crediting.
6.1.3 Any loss of communication with Associated Equipment that impacts Game operation must be reported on Player Terminal and logged automatically.
6.1.4 During the loss of communication with external Associated Equipment, any critical informa- tion related to revenue, integrity, and security of the cGaming Equipment must be preserved and transmitted as soon as the communication resumes.
6.1.5 All Associated Equipment internal to the Player Terminal must immediately disable itself upon loss of communication with the Player Terminal.
6.1.6 All Associated Equipment internal to the Player Terminal and capable of executing a software authentication/validation process and communicating the result must have a means to do so when initiated by the Player Terminal. Player Terminal must initiate such authentication/valida- tion processes upon Game reset as a minimum.
6.1.7 Any Critical Game Data communication between Player Terminal and Backend System, such as player input, Game outcome, financial transactions, and Game recall information must be secured, e.g. encrypted using a strong encryption.
6.1.8 After program interruption (e.g. processor reset), upon program resumption, any Game func- tion or communications to an external device must not begin until the program resumption routine, including self-tests.