The system can verify that every critical control program component on it is an authentic copy of the approved component, when installed, on request, and no less than once in each 24 hours by a method the regulatory body approves; the mechanism uses a hash producing a digest of at least 128 bits, covers every critical component that can affect wagering operations (executables, libraries, wagering and system configurations, operating system files, reporting components, database elements affecting operations) and indicates an authentication failure when any component is invalid.
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.