Wagering software communicates only with authorised components through secure communications, and when communication with the system is lost it prevents further wagering and shows an error message, which may be detected when the device next tries to communicate.
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.