A barrier is any obstacle that affects the speed, time and tools an adversary needs to get past it; barriers may be natural site features, prefabricated structures, passive fixtures or deployable temporary units. The cheapest effective ones are features already on the site or designed into a new one (ponds, ditches, level changes); natural traffic flows can reveal natural surveillance points; and deployable barriers can be pre-positioned for events needing a temporary increase, planned before the need arises. Cost and reliability depend on the barrier's role. Barriers can: mark the legal boundary; channel entry through a controlled point by discouraging entry elsewhere; create a zone for detection, surveillance, lighting and guards; deter unauthorised entry; force an intruder to show intent; delay access so detection and response become more likely; create stand-off distance from the protected area or asset; deter psychologically; cut the number of guards needed; and show the organization takes security seriously. Effectiveness depends on delay time and on detecting a breach: after the moment of detection, each further barrier must hold the adversary long enough for responders to judge the alarm (false, nuisance or real) and act.
This control maps to 1 controls across 1 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.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.