The organization is to define security perimeters and use them around areas holding information and other associated assets. Purpose: keep unauthorized people out and prevent physical harm to or tampering with the organization's information and assets. Guidance: where appropriate, define each perimeter and decide its location and strength according to the security requirements of the assets inside; make the perimeter of a building or site containing processing facilities physically sound, with no gaps or easy break-in points, solid exterior roofs, walls, ceilings and floors, external doors protected by bars, alarms, locks or similar, doors and windows locked when unattended, added outside protection considered for windows, above all on the ground floor, and ventilation openings taken into account; and alarm, monitor and test every fire door in a perimeter together with the walls so the required resistance is achieved to suitable standards, with the doors failing safe. Other information: protection comes from one or more barriers around the premises and facilities; a secure area might be one lockable office or a group of rooms inside a continuous internal barrier; extra internal barriers may separate areas with different requirements; and measures should be capable of being strengthened when threat levels rise.
This control maps to 60 controls across 32 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.
ISO 27002:2022 7.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of ISO 27002:2022 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 79 of 93 ISO 27002:2022 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. 180 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 60 it maps to, and the evidence behind each claim, over MCP and REST.