Where the system communicates with third-party providers (loyalty programmes, banks and payment processors, location services, cloud services, statistics and line services, identity verification): communication uses encryption and strong authentication; all third-party login events are recorded to an audit file; the communication does not interfere with or degrade system functions, third-party data does not affect player communications, third-party connections do not share the player network infrastructure, wagering is disabled on every connection but the player network, packets are not routed directly between third parties and the player network, and the system does not act as an IP router between them; and all financial transactions are matched against the records of banks and payment processors each day, or on the regulator's schedule.
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.