Each component functions per a documented secure communication protocol: all protocols use error detection and recovery built to stop intrusion, tampering, interference and eavesdropping, alternatives being reviewed case by case; all communications critical to wagering or account management use encryption and authentication; and communication on the secure network is possible only between enrolled, authenticated components with no unauthorised communications to components or access points.
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.