DEPARTMENT OF THE NAVY
OFFICE OF THE CHIEF OF NAVAL OPERATIONS
2000 NAVY PENTAGON
WASHINGTON, DC 20350-2000
OPNAVINST 3432.1A
N2/N6
4 Aug 2011
OPNAV INSTRUCTION 3432.1A
From: Chief of Naval Operations
Subj: OPERATIONS SECURITY
Ref: (a) CJCSI 3213.01C
(b) DoD Directive 5205.02 of 6 March 2006
(c) JP 3-13.3, Operations Security, 29 Jun 2006
(d) NTTP 3-54M/MCWP 3-40.9 of March 2009
(e) DoD 5205.02-M, DoD Operations Security (OPSEC)
Program Manual, 3 November 2008
(f) DUSD(CIS) Memo of 27 Aug 2007 (NOTAL)
Encl: (1) Navy OPSEC Program Management Responsibilities and
Governance
1. Purpose. To establish policy, procedures and
responsibilities for the Navy Operations Security (OPSEC)
program.
2. Cancellation. OPNAVINST 3432.1.
3. Applicability. The provisions of this instruction are
applicable to the U.S. Navy, all contractors assigned to Navy
activities, and all personnel conducting contracted service for
the Navy (e.g., research, development, test and evaluation
agencies and their contracted agents), effective on the date
signed.
4. Background
a. OPSEC is a critical process for all Navy activities.
The Department of Defense (DoD) has reaffirmed OPSEC practices
must be followed in the daily application of military
operations. The practice of OPSEC enables mission success by
preventing inadvertent compromise of sensitive or classified
activities, capabilities, or intentions at the tactical,
operational and strategic levels. OPSEC processes provide
