Visitor logs must keep a physical record of visitor activity inside the facility and inside sensitive areas, capturing: who the visitor is and which organization they come from; the visit date and time; and the name of the person who authorized their physical access. The log is to be retained for at least three months where the law permits. Recording both arrival and departure times, and checking the visitor's ID against the name they record, is described in the guidance as good practice, not a requirement. Applicability: all entities. Objective under the customized approach: visitor access is recorded in a way that lets individuals be identified.
This control maps to 18 controls across 12 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 9.3.4 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 18 it maps to, and the evidence behind each claim, over MCP and REST.