How to Store Gaming Machine Operation Data Safely With Backup and Encryption
Gaming machine operation data — revenue records, payout logs, audit trails, configuration settings, and error logs — must be stored safely to prevent unauthorized access, tampering, or loss. Safe storage has three components: encryption (the data cannot be read if the storage medium is stolen), backup (the data is preserved even if the primary storage fails or is destroyed), and access control (only authorized personnel can access the data). This article explains how to implement these three components for gaming machine operation data.
Component 1: Encryption of Stored Data
Encryption converts the data into an unreadable format that can only be decrypted with the correct encryption key. For gaming machine data, the encryption should be applied at the storage level (the entire storage medium is encrypted) or at the file level (individual files are encrypted). Storage-level encryption protects the entire data store — if the storage medium is removed from the machine, the data cannot be read without the encryption key. File-level encryption protects individual files — if one file is accessed without authorization, the other files remain protected.
Implementation: most modern gaming machines support AES-128 or AES-256 encryption of the data partition. Enable encryption in the machine’s configuration menu. The encryption key is stored in the machine’s secure element (a tamper-resistant chip) and is not accessible to external devices. If the storage medium (hard drive, SSD, or microSD card) is removed from the machine, the data cannot be decrypted without the key stored in the secure element. For older machines that do not support encryption, add an external encryption module (30-80 dollars) that encrypts the data as it is written to the storage medium. The encryption module connects between the mainboard and the storage interface (SATA, IDE, or SD card slot).
Component 2: Automated Backup to a Remote Location
Backup creates a copy of the data that is stored separately from the primary storage. If the primary storage fails (hardware failure, physical damage, or theft), the backup provides a complete copy of the data. The backup should be automated (no manual intervention required) and should run daily (or more frequently for high-value machines). The backup destination can be a remote server (cloud or physical) or a separate storage device at the same venue (a network-attached storage device or a secondary hard drive).
Implementation: configure the machine (or the background recording device described in the previous article) to back up the operation data daily. The backup includes all data files: revenue records, payout logs, audit trails, configuration settings, and error logs. The backup is transmitted to the remote server over an encrypted connection (SFTP or HTTPS). The remote server stores the backup in a write-once format (the backup files cannot be modified or deleted after they are written). The backup is verified after each transmission — the server calculates a checksum of the received files and compares it against the checksum calculated by the sending device. If the checksums match, the backup was transmitted correctly. If they do not match, the backup is retransmitted.
Component 3: Access Control for Data Retrieval
Access control restricts who can view, modify, or delete the stored data. The access control should be implemented at three levels. Level 1: the machine’s service menu — protect the service menu with a strong password (12 or more characters, mixed case, numbers, and symbols). Change the default password immediately after machine installation. Level 2: the backup server — protect the server with strong authentication (password plus two-factor authentication if possible). Restrict access to specific IP addresses (the machine’s IP address and the operator’s office IP address). Level 3: physical access to the storage medium — lock the cabinet panel that provides access to the storage medium. Use a tamper-evident seal in addition to the lock. Photograph the seal daily as part of the external inspection checklist.
The three levels of access control work together: Level 1 prevents unauthorized access through the service menu; Level 2 prevents unauthorized access to the backup data; and Level 3 prevents unauthorized physical access to the storage medium. For venues with multiple staff members, configure the service menu with multiple user accounts — one account for the operator (full access), one account for venue staff (view-only access to revenue data), and one account for technicians (access to diagnostic functions but not to revenue data modification). The principle of least privilege: each user has only the access necessary for their role.
Testing the Storage Safety: Periodic Restore and Verification
A backup that cannot be restored is useless. Periodically (quarterly for most venues, monthly for high-value venues), test the backup by restoring a sample of files from the backup server to a test machine or a computer. Verify that the restored files are complete and readable. The test restore validates both the backup process (the files were backed up correctly) and the backup storage (the server’s files are not corrupted). The test takes 15-30 minutes per machine per quarter. The time investment is justified by the confirmation that the backup will work when needed.
In addition to the test restore, verify the integrity of the stored data (both primary and backup) using cryptographic hashing (as described in the data protection system article). Calculate the hash of stored files and compare against the previously calculated hash values. Any mismatch indicates data corruption or tampering. The integrity verification is performed monthly for the primary storage and quarterly for the backup storage.
Frequently Asked Questions
Q: What is the cost of implementing safe storage for one machine?
A: Component 1 (encryption): 0 dollars if the machine’s firmware supports it; 30-80 dollars for an external encryption module. Component 2 (backup): 0 dollars if using a free cloud service with limited storage; 10-50 dollars per month for a paid cloud service; or 200-500 dollars one-time for a physical server. Component 3 (access control): 0 dollars (password configuration and IP restriction) plus 20-50 dollars for a cabinet lock upgrade. Total: 20-130 dollars per machine plus optional 10-50 dollars per month.
Q: How long should the backup be retained?
A: 12 months for standard venues. 24-36 months for high-value venues or venues in high-risk areas. Check the specific requirements of your insurance policy — some policies require 24 months of backup retention. Retain the backup for the duration of any open insurance claim or legal proceeding related to the machine’s operation.
Q: Can the machine’s operation data be stored in the cloud?
A: Yes, if the cloud service provides encryption at rest (the data is encrypted on the server) and encryption in transit (the data is encrypted during transmission). Verify the cloud service’s security certifications (SOC 2, ISO 27001) before using it for gaming machine data. For venues with regulatory requirements for data sovereignty (the data must remain in the same country), use a cloud service with servers in that country or use a physical server at the operator’s headquarters.