Study guide
6.2 Threat/Hazard–Vulnerability Pairing & Loss Event Profiles
ASIS Physical Security Professional PSP
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current PSP Exam Facts 1.2 Eligibility, Fees, Scheduling & Recertification 1.3 Experience-Based Testing, References & Study Approach
2 Assessment Planning & Methods
2.1 Assessment Plan, Stakeholders, Budget & Resources 2.2 Inside-Out, Outside-In, Site-Specific & Functional Models 2.3 Qualitative vs Quantitative Assessment Methods 2.4 Standards, Regulations, Codes & Where to Find Them
3 Asset Identification & Valuation
3.1 Asset Types, Terminology, Value, Criticality & Loss Impact 3.2 Valuing Tangible and Intangible Assets for Operations 3.3 Criticality, Key Areas & Loss-Impact Prioritization
4 Threats, Hazards & Operating Environment
4.1 Criminal, Terrorist, Insider & Sociopolitical Threats 4.2 Natural Disasters, Accidental & Cyber-Physical Hazards 4.3 Geography, Crime, Socioeconomics & Existing Countermeasures 4.4 Neighbors, Competitors, Legal, Reputation & Supply Chain
5 Vulnerability Assessment & Surveys
5.1 Surveys, Interviews, Incident Data, Crime Stats & Benchmarking 5.2 Evaluating Technology, Personnel & Procedures 5.3 Plans, Schematics & Environmental/Site Factors
6 Risk Analysis & Countermeasure Selection
6.1 Risk Analysis Strategies, Principles & Data Interpretation 6.2 Threat/Hazard–Vulnerability Pairing & Loss Event Profiles 6.3 Matching Countermeasures to Specific Risks 6.4 ROI, Total Cost of Ownership, Privacy, PII & Life Safety
7 Performance Requirements & Security Concepts
7.1 Design Constraints & Incorporating Risk Analysis 7.2 CPTED, Defense-in-Depth, 4 Ds & Security Terminology 7.3 Operational, Functional, Performance Requirements, Codes & Metrics
8 Structural Measures & CPTED Application
8.1 Fences, Gates & Perimeter Barriers 8.2 Blast Mitigation, Ballistic Protection & Hostile Vehicle Mitigation 8.3 Lighting, Locks, Doors, Windows & Glazing 8.4 Applying CPTED to Site Planning & Landscaping
9 Electronic Security Systems
9.1 Electronic Access Control Architecture & Credentials 9.2 Biometrics, Electrified Locks, Anti-Passback & Mantraps 9.3 Video Surveillance Design, Storage & Analytics 9.4 Intrusion Detection Sensors & Alarm Communications
10 Screening, Communications, Power & Networks
10.1 Personnel, Package & Vehicle Screening and Visitor/Vendor Policy 10.2 Mass Notification, Audio Comms, Consoles & Central Stations 10.3 Data Storage, Retention, PII & Physical Network Security 10.4 Primary/Backup Power and Copper, Fiber & Wireless Transmission
11 System Design & Project Documentation
11.1 Pre-Design, Schematic, Construction Docs, Calculations & Drawings 11.2 CSI MasterFormat, Owner Standards & AIA MasterSpec 11.3 Systems Integration, Scheduling, Cost Estimation & Value Engineering
12 Pre-Bid Meetings & Solicitation Packages
12.1 Site Visits, RFIs, Substitution Requests & Pre-Bid Meetings 12.2 RFP, RFQ, IFB & Sole Source 12.3 SOW, Timelines, Costs, Personnel & Documentation 12.4 Evaluation Criteria, Technical Compliance & Contracting Ethics
13 Procurement Planning & Vendor Selection
13.1 Procurement Process for Security Goods & Services 13.2 Interviews, Due Diligence, References & Selection 13.3 Project Management Functions in Procurement
14 Installation, Commissioning & Acceptance
14.1 Installation & Inspection Techniques 14.2 Commissioning & Implementation-Phase Integration 14.3 FAT, SAT & Final Acceptance Testing Criteria 14.4 Punch Lists, As-Builts, Config Management & End-User Training
15 Security Personnel Requirements
15.1 Roles, Limits, Proprietary vs Contract Staffing 15.2 Recruiting, KPIs, Discipline & Professional Development 15.3 Post Orders, Uniforms/Equipment & Non-Security Awareness
16 Lifecycle Maintenance & Program Evaluation
16.1 Preventive/Corrective Maintenance, Calibration, Service Agreements & Warranties 16.2 Upgrade Training, System Evaluation & Replacement
6.2 Threat/Hazard–Vulnerability Pairing & Loss Event Profiles
Key Takeaways Explain This Topic AI
A loss-event profile pairs one specific threat or hazard with one specific vulnerability, then states who/what, how, and consequence
Unpaired lists—every crime type, every leaky door—cannot justify a countermeasure
Name consequence in categories: death/injury, downtime, data/privacy, theft, and brand; one profile may carry more than one
Tailgating plus an unlocked, unattended loading dock is a cargo-theft profile, not a generic theft cell
Flood plus generators, ACS panels, and VMS servers in a basement is campus electronic-security loss, not a camera-mounting-height problem
Last updated: September 2026
Threat/Hazard–Vulnerability Pairing and Loss Event Profiles
A loss-event profile is not a mood about the neighborhood and not a heat-map color. It is a pair : one specific threat or hazard plus one specific vulnerability, then a plain-language statement of who or what is harmed, how the event unfolds, and what consequence follows. Independent ExamFinch teaching for published PSP Domain 1 tasks is that unpaired lists—every crime type on one page, every unlatched door on another—cannot justify a countermeasure. Task 5 knowledge on pairing exists so you stop recommending “more security” at a building.
Exam focus: Name the threat or hazard, name the vulnerability, then write who/what, how, and consequence. If any field says only “the warehouse,” you do not yet have a profile.
Why Pairing Beats Two Separate Lists
“Theft” is not a profile. “Unlocked dock” is not a profile. Cargo theft of staged electronics when an unauthorized person tailgates through an unlocked, unattended loading dock during shift change is a profile. The first two phrases describe a threat class and a condition. The third describes a mechanism. Countermeasures attach to mechanisms. Cameras, locks, attendants, and trailer-seal checks either interrupt that how or they do not.
Pairing also stops double-counting. A dock door that is unlatched is one vulnerability. It may pair with tailgating theft, with weather-driven product damage, and with an insider walking a carton to a car. Those are three profiles if the hows differ. They are not thirty profiles because you listed ten crime types against the same leaf.
Who/What, How, and Consequence
Write three fields for every pairing you intend to treat or formally accept.
Who/what names the asset and the actor or force. Weak version: “the warehouse.” Usable version: palletized consumer electronics staged at door 4; opportunistic thief or insider-assisted crew. People belong in this field when injury is plausible. A driver who might tackle a thief is part of who/what, not a footnote.
How is the mechanism that joins the threat or hazard to the vulnerability. Weak version: “someone could get in.” Usable version: walk-in at the 14:00 shift change through a dock door left unlatched, no attendant, no trailer-seal check, apron unsecured to a public lane. If you cannot walk the how in a sentence, you cannot match a measure in 6.3.
Consequence names the harm that actually follows, using categories rather than the word “bad.” Weak version: “bad for security.” Usable version: theft of a pallet; possible injury if a driver intervenes; downtime to rebuild the load; brand harm if customer lot codes appear in online resale.
Field Question it answers Weak version Usable version
Who/what Which asset and which actor or force The warehouse Staged electronics at door 4; opportunistic thief or collusive driver
How The joining mechanism Someone could get in Tailgate at 14:00 through an unlatched, unattended dock to a waiting van
Consequence Harm that follows Bad for security Theft, possible injury, rebuild downtime, brand hit from resale lot codes
Consequence Categories You Should Name on Purpose
Score, or at least name, these categories even when the analysis stays qualitative. They keep a theft-only brain from missing a life-safety pairing, and they keep a brand workshop from substituting for injury.
Death/injury — people first. You do not “accept” preventable death as residual in a footnote. Workplace violence in an unsecured lobby, vehicle impact through unrated storefront glazing, and fire-plus-locked-egress pairings live here even when Finance wants a theft number.
Downtime — hours or days the process cannot run. A flooded generator room that kills access control and video is downtime of the electronic security program and often of the occupancy that depended on it.
Data/privacy — drawings, credentials, visitor logs, badge photos, and packing lists leaving the site. Physical paths still steal information.
Theft — cash, cargo, tools, metals, pharmaceuticals, copper. Theft is common on PSP items; it is not the only category.
Brand — public trust, customer flight, license to operate. Brand is often a follower of the first four. It is not a substitute for naming injury or downtime. A social-media rumor with systems still powered is a different profile from a flood that takes the campus dark.
One profile may carry several categories. Flood water that kills generators is downtime; if delayed-egress hardware or emergency lighting depend on that power path, it is also death/injury; if drives die with no backup, it is data; if the outage is public, brand follows.
Worked Profile: Tailgating Plus Unlocked Loading Dock Equals Cargo Theft
Threat: opportunistic thief or collusive driver who already knows when staging happens.
Vulnerability: dock door unlatched, no attendant, cameras that record to an NVR nobody watches at shift change, no trailer-seal check, apron open to a public lane.
Who/what: palletized consumer electronics staged at door 4; also the driver who might intervene.
How: walk-in during the 14:00 swap; roll a pallet to a waiting van; gone before the next scan.
Consequences: theft (primary), injury if challenged, downtime to reconstruct the load, brand if the customer SKU hits resale with your lot codes.
Notice what this profile is not . It is not “theft in the metro area.” It is not “the dock needs cameras.” Cameras without a dock procedure do not break this how. An unlocked door plus an unwatched recording is still an open path.
Worked Profile: Flood Plus Generators in the Basement Equals Total ACS/VSS Loss
Hazard: storm-drain backup or overland flood; the parcel has history, which Task 3 should already have recorded.
Vulnerability: emergency generator, ACS panels, and VMS servers share the same basement with no flood barrier, no elevated pads, and no alternate recording path off-site.
Who/what: electronic access, video, and lock power for the campus; occupants who depend on those systems in an emergency.
How: a few inches of water; generators fault; UPS dies; readers and maglocks go to whatever fail state the hardware actually has; the NVR never records the looting or the medical emergency in the dark.
Consequences: downtime of ACS and VSS (primary), death/injury if egress hardware is now in the wrong state, data/privacy if drives are destroyed without backup, brand when the outage is public.
Raising camera heads on the first floor does not treat this pairing if the brains and the power sit in the water. The profile forces a different treatment conversation: relocate power and servers, flood-protect, or avoid putting critical electronics in that basement.
Five Profiles on One Campus (Use This Shape, Not a 200-Row Grid)
Profile Threat or hazard Vulnerability Who/what How Primary consequence
Dock cargo theft Opportunistic thief or collusive driver Unlatched, unattended dock at shift change Staged electronics; intervening driver Tailgate and roll a pallet to a van Theft; injury; downtime; brand
Basement flood Storm-drain backup / flood Generators, ACS, VMS in the same basement Campus electronic security; occupants Water kills power and recording Downtime; possible death/injury; data; brand
Insider drawings Trusted contractor after hours Unlocked lateral files in engineering Tool drawings; customer process know-how Badge in, fill a backpack, walk out Data/privacy; brand; later theft of product
Lobby violence Aggrieved visitor or former employee Unsecured reception desk, no duress, glass not rated Receptionist; waiting patients Walk straight to the desk with a weapon Death/injury; downtime; brand
Storefront ram Vehicle as tool Unrated glazing, no bollards on a straight approach Occupants near glass; high-value display Vehicle through the leaf, smash and grab Death/injury; theft; brand
Trap: Pairing Everything With Everything
A matrix of every threat class against every door is not analysis. It is combinatorial explosion that hides the five pairings that would actually stop operations. Profile the pairings that are credible for this site given Task 3 threats and Task 4 vulnerabilities. Depth beats a 200-row spreadsheet. If a row cannot state a how, delete the row. If two rows share the same how, merge them.
A second trap is copying another campus’s profiles. A coastal clinic’s flood-plus-basement pairing may be irrelevant on a hilltop plant. A hilltop plant’s vehicle-ram pairing may be irrelevant in a pedestrian mall with no approach speed. Site-specific pairing is the same discipline Chapter 2 required of assessment models.
The output of 6.2 is a short, defensible set of profiles. Section 6.3 matches countermeasures to those profiles instead of to a vendor shopping list.