512AWI10-701 — Operations Security (opsec)

512AWI10-701 governs the 512 AW Operations Security program, including responsibilities and guidelines for protecting critical or sensitive information.

Search 512AWI10-701

  • Publication number: 512AWI10-701
  • Title: OPERATIONS SECURITY (OPSEC)
  • Date: 2024-05-16

View 512AWI10-701 on armypubs.army.mil


It establishes a continuous OPSEC process, program roles, training, vulnerability analysis, information review, and coordination with Public Affairs. It requires personnel to protect critical information, report unsolicited requests, and coordinate public releases.

Topics covered

  • Critical information protection
  • OPSEC coordinators
  • Critical Information and Indicator List
  • Content vulnerability analysis
  • Public information releases
  • OPSEC awareness training
  • Unsolicited information requests

Questions and answers

What is the purpose of OPSEC under 512AWI10-701?

The purpose of OPSEC is to identify, evaluate and protect critical or sensitive information, relating to the 512 AW daily and wartime activities. (paragraph 1)

How often must the effectiveness of the Wing Commander's shredding guidance be evaluated?

Evaluate (at a minimum, annually) the effectiveness of the Wing Commander’s guidance for 100% shredding of all internally generated paperwork. (paragraph 2)

What must unit OPSEC coordinators do for external web or SharePoint sites?

Ensure their organization conducts an annual content vulnerability analysis if they maintain any external web or SharePoint sites that do not require a DoD Common Access Card. (paragraph 2)

When must AFOSI be notified about information requests?

Notify AFOSI immediately when becoming aware of an unsolicited request (verbal, electronic or written) for critical or sensitive information. (paragraph 2)

What coordination is required before information is released to the public?

Ensure all information that is to be released to the public is coordinated with the 512 AW Public Affairs Office. (paragraph 2)

Ask Reggie.Bot a question about 512AWI10-701