Where a player downloads an application or uses a browser to wager: the software does not let players send data to each other, apart from chat functions and approved files such as profile pictures; the software does not automatically alter device firewall rules to open blocked ports; it accesses no ports beyond those needed to communicate with the server, automatically or by prompting the user; additional non-wagering functionality does not alter the software's integrity; it cannot override the device's volume settings; and it stores no sensitive information, with auto-complete and password caching recommended off by default.
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.