Vulnerabilities are managed, and the infrastructure is watched for unauthorised access, with a set of tools and technologies such as intrusion detection, and detection, along with the security tools and technologies, feeds into incident management and into general event monitoring: a range of supported technologies, services and assets (vulnerability scanners, fuzzers and sniffers, protocol analysers) is used to find vulnerabilities continually; risk scenarios are defined and communicated so they are readily recognised and their likelihood and impact are understood; event logs are reviewed regularly for possible incidents; security incident tickets are raised promptly when monitoring spots a possible incident; and security events are logged and the records kept for a suitable period.
This control maps to 3 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 3 it maps to, and the evidence behind each claim, over MCP and REST.