6.3 Matching Countermeasures to Specific Risks
Key Takeaways
- Select a measure because it changes a named loss-event profile along deter, detect, delay, deny, or respond—not because it appears on a shopping list
- Combine structural, electronic, procedural, and personnel families; one catalog does not replace the other three
- Camera-only treatment of insider theft of drawings is under-control: weak after-the-fact detect without deny
- Over-control is a mantrap or armed post whose burden exceeds the pairing and often gets bypassed, which raises residual
- Domain 2 designs the 4 Ds into systems; Task 5 decides which functions this pairing still lacks
Matching Countermeasures to Specific Risks
A countermeasure earns its place only if it changes a named loss-event profile. Independent OpenExamPrep teaching for published PSP Domain 1 tasks is that Task 5 is selection logic, not a mall list. Domain 2 will teach how to design CPTED, barriers, ACS, and video into a system. Here you decide which family of measure, and enough of it, for this pairing—along deter, detect, delay, deny, and respond. Those five functions return in Domain 2 as design vocabulary. On Task 5 they are a test: which function is missing in the how you wrote in 6.2?
Exam focus: Match the measure to the how. Cameras are not a treatment for an unlocked drawing cabinet. A mantrap is not a treatment for a low-inherent public lobby.
Four Families, Used as a Set
| Family | What it is | Typical contribution to a profile |
|---|---|---|
| Structural | Barriers, rated doors, locks, glazing, vehicle measures, layout that is hard to abuse | Delay and deny; sometimes deter when the barrier is obvious and real |
| Electronic | Access control, video, intrusion detection, lighting control, notification | Detect; deter if the system is obvious and believed; delay/deny only when tied to locking hardware |
| Procedural | Key control, escorts, dual control, opening and closing, staging rules, incident reporting | All five functions if people actually practice them; none if they live only in a binder |
| Personnel | Officers, dock attendants, reception, SOC operators | Detect and respond; deter by presence; delay when the post sits on the adversary path |
The trap is treating one family as a religion. An integrator who only sells cameras will discover a camera need in every profile. A contract-guard company will discover a post. A locksmith will discover hardware. Your job is to assign functions across families so the how actually breaks.
Deter, Detect, Delay, Deny, Respond as Selection Logic
Deter makes the pairing look unattractive before it starts: lighting that works, a post that is actually present, signage that tells the truth. False signage (“premises video recorded 24/7”) that the night crew knows is a lie trains insiders to ignore the rest of the program.
Detect means someone or something knows the event is happening in time to act: a door contact, a watched camera, an attendant, a duress button that reaches a person. Recording is not detecting. Storage is not detecting. A 14-day NVR that nobody queries except after Finance notices shrinkage is after-action evidence, not detection.
Delay consumes adversary time after detection so response can arrive: locks, fences, safes, mantraps, vehicle distance. Delay without detect is a silent stopwatch. Detect without delay is a loud stopwatch with no time on the clock.
Deny means the asset is simply not reachable along that how: a vault, a locked cabinet, a badge that does not open the lab, an air gap for drawings. Some programs fold deny into delay. PSP-style items still expect you to say when access is not granted at all, versus merely slowed.
Respond is people and procedures that interrupt or recover: officer, police, process shutdown, medical. A console with no trained operator is not response. A police-call policy that assumes a 30-second arrival in a rural plant is a fantasy delay budget.
Selection test, used on every profile: which function is missing? If the how is tailgating an unattended dock, detect might exist on video and still be missing in real time; delay might exist as a latch that is not used; deny does not exist while the door is unlatched; respond does not exist if nobody is posted. Buying a newer camera platform does not fill those gaps.
Under-Control Versus Over-Control
Under-control is a measure that does not touch the how. Cameras as the answer to insider theft of drawings from an unlocked cabinet are under-control. A fence as the answer to a basement flood is under-control. Extra lighting as the answer to an unrated storefront with a straight vehicle approach is under-control if the pairing is ram, not night-time concealment.
Over-control is a measure whose cost, delay to legitimate users, or life-safety burden exceeds the pairing. A mantrap plus an armed post on a public clinic lobby with no violence history and a need for rapid egress is over-control. Over-control is not “seriousness.” Staff will bypass a painful control—wedge the mantrap, prop the dock, share the PIN—and residual risk rises. Over-control also shows up as procedure piles that nobody can finish on a live dock.
Match intensity to inherent risk and to the legal and life-safety floor. A high-inherent, high-consequence pairing (pharmacy, cash vault, infant nursery) can justify stacked families. A low-inherent pairing already inside appetite should not get a new platform because a demo was impressive.
Worked Mismatch: Insider IP Theft Versus Camera-Only “Solution”
Engineering office. Unlocked lateral files of tool drawings. Contractors with after-hours badges. Corridor cameras that record to a 14-day NVR. Nobody reviews video unless Finance asks. Leadership’s first instinct: “put in better cameras.”
Camera-only against this how:
- Deter: weak. Insiders know the cameras and know nobody is watching.
- Detect: after the fact, and only if someone looks.
- Delay / deny: none on the files. The backpack is still a valid container.
- Respond: no one is posted to the office at 19:00.
That is under-control dressed as a technology refresh.
A matched package for the same profile:
- Structural: lockable cabinets; possibly a lockset change on the office leaf.
- Electronic: ACS on the office so after-hours contractor access is a logged event; camera as after-action and limited deterrence, not the treatment; optional cabinet alarm if the drawings truly warrant it.
- Procedural: checkout log, clean-desk rule that supervisors actually inspect, contractor hour limits, a USB and paper-out policy facilities can enforce at the door rather than at a help-desk slogan.
- Personnel: a named closing check by a role that exists on the roster—not “security in general.”
The cameras may stay. They are no longer pretending to be deny.
Combining Families on the Dock Profile
Return to tailgating plus an unattended dock. A matched selection assigns functions instead of products:
- Structural: latch that is used; dock leveler control; if needed, a barrier between staging and the public apron.
- Electronic: door contact that alarms when unlatched without a valid attendant or badge state; camera on the apron watched or alarmed, not merely recorded.
- Procedural: door may be unlatched only with an attendant present; trailer-seal check; staging time limits so pallets do not live at the threshold.
- Personnel: attendant or officer during staging windows.
Each 4 D function has an owner. That is selection. Hardware catalogs, cable schedules, and CSI spec sections arrive in Domain 2 and Domain 3. If an exam item offers a shopping list (newest analytics, extra PTZ, decorative bollards on the wrong side of the building) against a how those products do not touch, the list is wrong even if every device is real.
What Not to Do on Task 5 Items
Do not select a measure because it is new, because it is expensive, or because a peer site bought it. Do not use personnel as a default when the how is a flood in a basement. Do not use electronics as a default when the how is an unlocked cabinet. Do not stack delay on a required egress path until 6.4’s life-safety rules are satisfied. Selection that imprisons occupants is not mitigation; it is a new death/injury profile you just wrote.
The output of 6.3 is a short matched set per profile: families, functions, and intensity. Section 6.4 asks whether that set is affordable over its life, lawful for privacy and PII, and survivable in a fire.
The sound reason to select a physical security countermeasure is which of the following?
Using cameras alone as the response to insider theft of drawings from an unlocked engineering cabinet is an example of which error?
Structural, electronic, procedural, and personnel measures should be combined so that which of the following is true?