For wagering software installed locally on a device, all critical components (wagering rules, elements controlling communication with the system, other components needed for proper operation) can be authenticated each time the software loads and, where supported, on demand as the regulator requires; a failed authentication prevents wagering and shows an error message; verification mechanisms are evaluated case by case and approved by the regulator and the laboratory.
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.