Internal IP addresses and routing information may be disclosed only to authorised parties. The guidance explains this keeps attackers from learning internal addressing, notes that methods vary with the technology (IPv4 and IPv6 may differ), and lists examples such as network address translation, placing components behind proxy servers or NSCs, filtering route advertisements, and private or privacy-extension addressing for outgoing sessions. Applicability: no special notes; applies to every assessed entity. Objective under the customized approach: internal network details are shielded from unauthorised disclosure.
This control maps to 23 controls across 10 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.5 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 23 it maps to, and the evidence behind each claim, over MCP and REST.