Change the paradigm from risk- to threat-based decision-making
By AMIT GAVISH

The horrific tragedy of the massacre on the Virginia Tech campus raises numerous questions, not the least of which is how best to secure our schools, campuses, businesses and buildings from threats of low frequency threats we may think have a low probability of occurring.

In a press conference hours after the attack, a speaker from Virginia Tech University said the attack was “a low-probability high-stake” attack that could not have been prevented. That type of statement is a recipe for failure and raises the need to reconsider how we “think” and “do” security.

In recent years, the generally accepted security paradigm called for risk-based decision making, one that considers risks through a cost benefit analysis to mitigate and minimize costs and consequences.

Security risks are comprised of three variables: the probability of an occurrence, our vulnerability at a given time and place, and potential consequences. The problem with looking at prevention only through these variables is that it ignores the fact that threats are ever present though the probability of an attack may be low. The question is, “Can we protect our businesses, schools, universities and facilities based on a different thought process?”

We believe we need to strike a balance between risk-based decision-making that provides a road map, generates a security master plan and determines resource allocation and a threat-based process. We need a decision-making process that is cost-effective yet offers a threat-based scenario-driven plan that considers all credible, realistic threats that may occur at a facility.

Threat-based thinking has as one of its underlying assumptions that we must do everything possible to prevent any attack at a facility. To focus on one or two likely threats is folly.

A security plan can’t be based solely on an analysis of frequency of events but must include preventive measures, not just responses. Questions about the effectiveness of the security, emergency plans and crisis-response plan of Virginia Tech Campus will continue to arise and be closely examined. Was there a plan to prevent such attack? Was the response of law enforcement agencies rapid and adequate? Were there any warning signs that should have been picked up by campus law enforcement and university officials? Were there any emergency and crisis policies and procedures in place, and if so, were they tested and practiced?

These questions are important for a critical analysis of this attack and there are certainly lessons that will be learned. But is it going to change the way we think about security?

Our obligation as security professionals is not solely to reduce risks and losses, but to protect the life of those we serve. Campus buildings and facilities are not more important than human life and “open environment” is a state of mind, not a question of security measures. Our challenge is to provide guidance that will allow facilities and institutions to be welcoming and secure at the same time.

When strategizing our security program from a threat-based perspective we need to follow these steps:

  • Identify categories of threats that are applicable and credible to our specific environment. These include, but are not limited to, terrorism, shooting, inside threats, workplace violence, information security, natural disasters and thefts.
  • Define the protected environment and security mission and goals. We need to identify the “real” asset. Is it our building and its contents or the lives of our people, or both?
  • Identify our resources, capabilities and limitations. Not all locations are alike and our limitations and capabilities will differ. We need to ask these questions: What are the threats we know? What are the threats we don’t know? What are the threats we can protect against? What are the threats that can’t be protected?
  • Define the design base threat (DBT). What are these threats that we design our security to protect against? Who are our adversaries and what capabilities, tactics, motives, methods of operation and intentions do they possess? Are we facing an organized terrorist group or is the likely threat a solitary unbalanced gunman? Do we know what we are looking for when utilizing metal detectors? Is it an assembled gun or are there just parts and pieces which can be reassembled later?
  • Identify vulnerabilities for each one of the threats identified.
  • Implement countermeasures and safeguards that will encompass physical elements, technology, policies and procedures and the human factor elements of security.
  • Test and practice our security and emergency policies and procedures. It is essential that we do so from the adversary’s viewpoint If we know how the adversary works his tactics, methods of operation and his capabilities we can design the adequate countermeasures.
  • Re-evaluation of the security program. Security is dynamic and requires constant checks and tests. What worked in one location may no longer be applicable in another or at another time.

The right balance between risk-based and threat-based security decision-making will enable us to focus on the prevention of future attacks, not just on the reduction and mitigation of its consequences. This approach will help insure the safety of our institutions and workplaces and decrease the likelihood of “low-probability threats” striking terror upon us.

Amit Gavish is senior corporate adviser for international security issues at SSC Inc. of Shelton. He conducts risk assessments and security training seminars on detection, prevention and preparedness for terrorist and suicide bombings.

For inquiries about SSC’s services, please call 1-866-704-6140.
Home · President's Message · Our People · Investigation Services
Uniformed Security ·Security Computing · Risk Consulting Services
Electronic Security · Partners · Upcoming Events
Hot Topic · Employment · Links
Press Releases · Contact Us

SSC, Inc.    25 Controls Drive    Shelton, CT 06484
Toll Free: 866-704-6140  ·  Telephone: 203-925-6140  ·  FAX: 203-402-0387