Periodic technical security tests on production, as the regulator requires, guarantee no vulnerabilities put the system's security and operation at risk: a third-party attack simulation following a known methodology, with vulnerability analysis identifying and passively quantifying risks, unauthorised access attempts to the highest level possible with and without credentials (white box and black box), assessing operating systems and hardware configurations through UDP and TCP port scanning, stack fingerprinting and TCP sequence prediction, banner grabbing, HTTP and HTTPS web scanning, and router scanning over BGP, BGMP and SNMP.
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.