Threat is not Random
More often than not, security systems miss the mark when they skip a vital step in developing their security standards and procedures. They do not first clearly define the threat. But only once you understand the threat, can you understand what is suspicious and then have a road map for procedures.
Take random checks as an example. Think about how ambiguous it is when an officer is asked to “randomly” check a given number of people or objects. Given the open-ended nature of that directive, the officer chooses what to check motivated by what amounts to whim: perhaps the officer has a non-confrontational personality and will avoid anything or anyone that appears troublesome. What and whom he chooses to check could likewise be motivated by subconscious sexism, racism or some other psychological mindset. With humans, there is no such thing as random. A random check procedure can translate to a real vulnerability for a security system because it allows an officer to make screening decisions based on his own inclinations.
What’s more, a random check procedure is passive. It requires no (more…)

















