Email this Article Email   

CHIPS Articles: DCNO for Information Warfare Issues End of Life of CVR Teams and Protecting Controlled Unclassified Information Guidance

DCNO for Information Warfare Issues End of Life of CVR Teams and Protecting Controlled Unclassified Information Guidance
By Vice Adm. Jeffrey E. Trussler, Deputy Chief of Naval Operations for Information Warfare, OPNAV N2N6 - March 25, 2021
REF/A/DOC/DOD CIO/26MAR2020// Department of Defense Chief Information Officer Memo on the temporary authorization to use Impact Level (IL) T 2 Cloud Environment for certain basic Controlled Unclassified Information (CUI)

REF/B/DOC/DOD/6MAR2020//.// DODI 5200.48, Controlled Unclassified Information Program

REF C IS SECNAVINST 5510.36B, 5510.36B, The Department of the Navy Information Security Policy.//

NAVADMIN 063/21 serves to provide attentiveness and understanding of what constitutes Controlled Unclassified Information (CUI), and its proper handling and protection, as the Commercial Virtual Remote (CVR) environment reaches End of Life (EOL) 15 June 2021. CVR, a cloud-based solution accessible from personal devices (using CAC login), allowed the processing of CUI. When CVR goes away, users must be vigilant as CUI is not allowed on non-government devices (ie. personal desktop and laptop computers, tablets, and mobile phones). Additional information regarding the transition off CVR will be provided separately.

Key definitions from references (a) and (b):

a. CUI. UNCLASSIFIED information the Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls, but does not meet the requirements for classification IAW Executive Order 13526 or the Atomic Energy Act.

b. Legacy for Official Use Only (FOUO). Prior to the CUI program, this was a dissemination control marking applied to unclassified information that disclosure to the public of that particular Record, or portion thereof, would reasonably be expected to cause a foreseeable harm to an interest protected by one or more Exemptions of the Freedom of Information Act (FOIA). FOUO information does not automatically become CUI and is not interchangeable with CUI.

(1) Legacy FOUO material is not required to be re-marked or redacted while it remains under Department of Defense (DoD) control or is accessed online and downloaded for use within the DoD.

(2) Legacy FOUO material or new derivative documents must be marked as CUI if the information qualifies as CUI, particularly if it is being shared with other government departments.

c. DoD CUI Registry. Provides an official list of Categories used to identify the various types of CUI. Individuals must use to ensure proper identification of all CUI material. The registry can be located at: http://www.dodcui.mil/Home/DoD-CUI-Registry.

d. Authorized Holders. Individuals that designate or handle CUI and are responsible for determining, at the time of creation, whether information in a document falls into a CUI category. If so, the authorized holder is responsible for applying CUI markings and dissemination instructions accordingly.

e. Lawful Government Purpose. Any activity, mission, function, operation, or endeavor that the U.S. Government authorizes or recognizes as within the scope of its legal authorities or the legal authorities of non-executive branch entities (such as state and local law enforcement).

f. Limited Dissemination Controls (LDC). Any control used to limit or specify CUI dissemination.

(1) Only Authorized Holders can apply this additional marking and should only use to promote a Lawful Government Purpose. The principle of

(2) All LDCs must be approved by the CUI Executive Agent (EA) listed in the CUI Registry (for example, CUI marked FED ONLY further restricts sharing to Federal Employees; CUI marked NOCON prohibits sharing with Contractors). Lawful Government Purpose requires that Authorized Holders of CUI must not share CUI where sharing is prohibited, restricted, or further subject to LDCs.

General CUI Guidelines.

a. Organizations should follow the guidelines as outlined in reference (a) for handling and protecting CUI.

b. IAW reference (a), personnel will not use unofficial or personal (e.g., .net, .com, etc.) email accounts, messaging systems, or other non-DoD information systems to conduct official business involving CUI.

c. Approved or authorized government contractor systems are authorized to handle CUI.

d. Who can access CUI? The answer is based on whether the individual has a Lawful Government Purpose. While similar to Need to Know for classified information, Lawful Government Purpose has a different litmus test. See reference (a) for guidance on Lawful Government Purpose.

Training. All personnel (military, civilian, and contractor) who are authorized access to classified information systems must receive initial and annual refresher CUI education and training. The Center for Development of Security Excellence (CDSE), an element of the Defense Counterintelligence and Security Agency (DCSA), has developed and released the only authorized and approved DoD CUI training module. The training module is accessed at https://www.dodcui.mil/Home/Training/. When accessing the website, click on the CDSE Current CUI link to access the training and resource materials.

The following sites provide additional information on the DoD CUI Program:

Primary POC Capt. Lionel Vigue: lionel.vigue@navy.mil / TEL: 571-256-8422//
Secondary POC Lt. Cmdr Martha Wittosch OPNAV N2N6: martha.a.wittosch@navy.mil / TEL: 703-492-1642//

This message will remain in effect until canceled or superseded.

Released by VADM Jeffrey E. Trussler, Deputy Chief of Naval Operations for Information Warfare, OPNAV N2N6.//

You can download NAVADMIN 063/21 here

Related CHIPS Articles
Related DON CIO News
Related DON CIO Policy

CHIPS is an official U.S. Navy website sponsored by the Department of the Navy (DON) Chief Information Officer, the Department of Defense Enterprise Software Initiative (ESI) and the DON's ESI Software Product Manager Team at Space and Naval Warfare Systems Center Pacific.

Online ISSN 2154-1779; Print ISSN 1047-9988
Hyperlink Disclaimer