Operations security

Operations security (OPSEC) is a process that identifies critical information to determine if friendly actions can be observed by enemy intelligence, determines if information obtained by adversaries could be interpreted to be useful to them, and then executes selected measures that eliminate or reduce adversary exploitation of friendly critical information.

Women's Army Corps anti-rumor propaganda (1941–1945)
"OPSEC" redirects here. For the 501(c)(4) group, see Special Operations OPSEC Education Fund.
"OPSEC" redirects here. It is not to be confused with OPSEK.

World War II propaganda poster which popularized the cautionary phrase "Loose lips sink ships"

In a more general sense, OPSEC is the process of protecting individual pieces of data that could be grouped together to give the bigger picture (called aggregation). OPSEC is the protection of critical information deemed mission-essential from military commanders, senior leaders, management or other decision-making bodies. The process results in the development of countermeasures, which include technical and non-technical measures such as the use of email encryption software, taking precautions against eavesdropping, paying close attention to a picture you have taken (such as items in the background), or not talking openly on social media sites about information on the unit, activity or organization's Critical Information List.

The term "operations security" was coined by the United States military during the Vietnam War.

Social engineering is the art of manipulating people into performing actions or divulging confidential information, rather than by breaking in or using technical cracking techniques

Process

OPSEC is a five-step iterative process that assists an organization in identifying specific pieces of information requiring protection and employing measures to protect them:

  1. Identification of Critical information: Critical information is information about friendly intentions, capabilities and activities that allow an adversary to plan effectively to disrupt their operations. U.S. Army Regulation 530-1 has redefined Critical Information into four broad categories, using the acronym CALI – Capabilities, Activities, Limitations (including vulnerabilities), and Intentions.[1] This step results in the creation of a Critical Information List (CIL). This allows the organization to focus resources on vital information, rather than attempting to protect all classified or sensitive unclassified information. Critical information may include, but is not limited to, military deployment schedules, internal organizational information, details of security measures, etc.
  2. Analysis of Threats: A Threat comes from an adversary – any individual or group that may attempt to disrupt or compromise a friendly activity. Threat is further divided into adversaries with intent and capability. The greater the combined intent and capability of the adversary, the greater the threat. This step uses multiple sources, such as intelligence activities, law enforcement, and open source information to identify likely adversaries to a planned operation and prioritize their degree of threat.
  3. Analysis of Vulnerabilities: Examining each aspect of the planned operation to identify OPSEC indicators that could reveal critical information and then comparing those indicators with the adversary's intelligence collection capabilities identified in the previous action. Threat can be thought of as the strength of the adversaries, while vulnerability can be thought of as the weakness of friendly organizations.
  4. Assessment of Risk: First, planners analyze the vulnerabilities identified in the previous action and identify possible OPSEC measures for each vulnerability. Second, specific OPSEC measures are selected for execution based upon a risk assessment done by the commander and staff. Risk is calculated based on the probability of Critical Information release and the impact if such as release occurs. Probability is further subdivided into the level of threat and the level of vulnerability. The core premise of the subdivision is that the probability of compromise is greatest when the threat is very capable and dedicated, while friendly organizations are simultaneously exposed.
  5. Application of Appropriate OPSEC Measures: The command implements the OPSEC measures selected in the assessment of risk action or, in the case of planned future operations and activities, includes the measures in specific OPSEC plans. Countermeasures must be continually monitored to ensure that they continue to protect current information against relevant threats.[2] The U.S. Army Regulation 530-1[3] refers to "Measures" as the overarching term, with categories of "Action Control" (controlling one's own actions); "Countermeasures" (countering adversary intelligence collection); and "Counteranalysis" (creating difficulty for adversary analysts seeking to predict friendly intent) as tools to help an OPSEC professional protect critical information.

An OPSEC Assessment is the formal application of the process to an existing operation or activity by a multidisciplinary team of experts. The assessments identify the requirements for additional OPSEC measures and required changes to existing ones.[4] Additionally, OPSEC planners, working closely with Public Affairs personnel, must develop the Essential Elements of Friendly Information (EEFI) used to preclude inadvertent public disclosure of critical or sensitive information.[5] The term "EEFI" is being phased out in favor of "Critical Information", so all affected agencies use the same term, minimizing confusion.

History

Vietnam

In 1966, United States Admiral Ulysses Sharp established a multidisciplinary security team to investigate the failure of certain combat operations during the Vietnam War. This operation was dubbed Operation Purple Dragon, and included personnel from the National Security Agency and the Department of Defense.[6]

When the operation concluded, the Purple Dragon team codified their recommendations. They called the process "Operations Security" in order to distinguish the process from existing processes and ensure continued inter-agency support.[7]

NSDD 298

In 1988, President Ronald Reagan signed National Security Decision Directive (NSDD) 298. This document established the National Operations Security Program and named the Director of the National Security Agency as the executive agent for inter-agency OPSEC support. This document also established the Interagency OPSEC Support Staff (IOSS).[8]

International and private-sector application

Although originally developed as a US military methodology, Operations Security has been adopted worldwide for both military and private-sector operations. In 1992, the North Atlantic Treaty Organization (NATO) added OPSEC to its glossary of terms and definitions.[9]

The private sector has also adopted OPSEC as a defensive measure against competitive intelligence collection efforts.[10]

Military and private-sector security and information firms often require OPSEC professionals. Certification is often initially obtained from military or governmental organizations, such as:

  • U.S. Army OPSEC Support Element[11]
  • U.S. Navy OPSEC Support Team[12]
  • U.S. Marine OPSEC Support Team[13]
  • U.S. Air Force OPSEC Support Team[14]
  • U.S. Coast Guard Office of Security Policy and Management[15]
  • Joint OPSEC Support Element.[16]
  • Interagency OPSEC Support Staff.[17]

Other measures that impact OPSEC
gollark: YOU ARE MISGENDERING ME!
gollark: My ~~title~~ pronoun would of course be Supreme Overlord, Master of All Space and Time, Devourer of Souls, He Who Rules All, Taper of Fish to ATMs, gollark (or possibly osmarks).
gollark: <@241757436720054273> TOML is arguably just a way to parse this "text" anyway...
gollark: But *should* you?
gollark: Nobody really seems to want to actually rigorously define XML schemae.

See also

References
  1. https://fas.org/irp/doddir/army/ar530-1.pdf
  2. "The OPSEC Process". The Operations Security Professional's Association. Retrieved April 12, 2011.
  3. https://fas.org/irp/doddir/army/ar530-1.pdf
  4. "OPSEC Glossary of Terms". Interagency OPSEC Support Staff. Retrieved June 16, 2016.
  5. "Joint Operation Planning Process and Public Affairs Actions" (PDF). Defense Technical Information Center (DTIC). Archived from the original (PDF) on 2016-08-08. Retrieved June 16, 2016.
  6. "PURPLE DRAGON: The Formations of OPSEC". Information Assurance Directorate. National Security Agency. Retrieved June 15, 2016.
  7. "The Origin of OPSEC- from the dragon's mouth". www.opsecprofessionals.org. Retrieved 2016-06-16.
  8. "About the IOSS". National OPSEC Program. Interagency OPSEC Support Staff. Retrieved June 15, 2016.
  9. "NATO Glossary of Terms and Definitions" (PDF). AAP-6. NATO. Retrieved June 16, 2016.
  10. Kahaner, Larry (1997). Competitive Intelligence. Simon & Schuster. pp. 252–255.
  11. "Army OPSEC Support Element (OSE) Training". 1stiocmd.army.mil. Ft. Belvoir, VA: 1st Information Operations Command. Retrieved June 20, 2018.
  12. "Naval Operations Security Support Team". Navy.mil. Washington, DC: U.S. Navy. Retrieved June 20, 2018.
  13. "The Marine Corps Operations Security (OPSEC) Program". Marines.mil. Washington, DC: U.S. Marine Corps. Retrieved June 20, 2018.
  14. "Air Force OPSEC Support Team". Washington, DC: U.S. Air Force. Retrieved June 20, 2018 – via Facebook.com./
  15. Commandant of the Coast Guard (April 22, 2014). Commandant Instruction M5510.24A, Operations Security (OPSEC) Program (PDF). Washington, DC: U.S. Coast Guard. p. 1.
  16. "JIOWC OPSEC Support". Lackland Air Force Base: U.S. Joint Information Operations Warfare Center. Retrieved June 20, 2018 – via Facebook.com.
  17. "National OPSEC Program". iad.gov/ioss/. Ft. George G. Meade, MD: Interagency OPSEC Support Staff (IOSS). Retrieved June 20, 2018.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.