Significant event information maintained and backed up includes failed logins; program errors and authentication mismatches; significant unavailability of any critical component; large wins and large wagers, single and aggregate, above regulator-set values with the wager record; system voids, overrides and corrections; changes to live data files outside normal execution; changes to the download data library; changes to the policies and parameters of the operating system, the database, the network and applications; changes to the master time server; changes to established event or market criteria other than live line changes; changes to results; changes to promotion or bonus parameters; player account adjustments, changes to player data, deactivations and large financial transactions above regulator-set values; irrecoverable loss of sensitive information; other activity needing user intervention outside normal operation; and other events the regulator deems significant.
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.