The entity must implement anti-spoofing measures that detect forged source IP addresses and stop them getting into the trusted network. The guidance gives the example of blocking packets from the internet that claim an internal source address, notes that many products enable anti-spoofing by default, and advises consulting vendor documentation. Applicability: no special notes; applies to every assessed entity. Customized approach objective: packets carrying falsified source IP addresses cannot enter a trusted network.
This control maps to 20 controls across 8 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 1.4.3 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 20 it maps to, and the evidence behind each claim, over MCP and REST.