The system logically secures player data and wagering data (accounting, reporting, significant events and other sensitive information) against alteration, tampering and unauthorised access: input is validated and corrupt data rejected; workstations with access to critical applications and databases are limited; files and directories are encrypted or password protected, otherwise viewing is restricted with segregation of duties and monitored, recorded access; equipment holding data has no option that compromises it and no mechanism by which an error clears it; data in equipment memory cannot be removed before transfer to the database; data is stored in encrypted server areas secured internally and externally; production databases sit on networks separated from user interface servers; data survives loss of power; and data is not lost when parts are replaced in maintenance.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.