Logs from every other in-scope system component, meaning those not covered by the daily review in 10.4.1, must be reviewed on a periodic basis. Applies to all entities. Applicability: covers every remaining in-scope component outside the scope of 10.4.1. The guidance notes these reviews can reveal signs of trouble or attempts to reach critical systems by way of less critical ones. Customized approach objective: suspicious or anomalous activity on these other components is reviewed in line with the risk the entity has identified.
This control maps to 25 controls across 17 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.
PCI DSS 4.0 10.4.2 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.
The graph holds this control, the 25 it maps to, and the evidence behind each claim, over MCP and REST.