Attachment_4_DODM_5200.01-V4_Excerpts_FOUO_Protection_Requirements.pdf
DoD Manual PDF 276 KB Posted
- Attached to
- TECHNICAL REP FOR MRG BEARING
- Solicitation number
- N3225319Q0069
About this file
Attachment 4
View the file
Other versions and copies of DoDM 5200.01, Vol. 4
Who attaches DoDM 5200.01, Vol. 4
Other files
| File | Type | Posted |
|---|---|---|
| Attachments_1-3.pdf | ||
| Solicitation_Final.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DoDM 5200.01-V4, February 24, 2012
Change 1, 05/09/2018
(Excerpt from Enclosure 3, page 10, paragraph 1.f.)
f. ALL DoD unclassified information MUST BE REVIEWED AND APPROVED FOR
RELEASE through standard DoD Component processes before it is provided to the public
(including via posting to publicly accessible websites) in accordance with DoDD 5230.09
(Reference (j)), Deputy Secretary of Defense Memorandum (Reference (k)), and other applicable regulations. Unclassified information previously approved for release to the public may be shared with any foreign government or organization.
(Excerpt from Enclosure 3, page 17, paragraph 2.e.)
e. Protection of FOUO Information
(1) During working hours, reasonable steps shall be taken to minimize the risk of access by unauthorized personnel (e.g., not reading, discussing, or leaving FOUO information unattended where unauthorized personnel are present). After working hours, FOUO information may be stored in unlocked containers, desks, or cabinets if Government or Government-contract building security is provided. If such building security is not provided or is deemed inadequate, the information shall be stored in locked desks, file cabinets, bookcases, locked rooms, etc.
(2) FOUO information and material may be transmitted via first class mail, parcel post, or, for bulk shipments, via fourth class mail. Whenever practical, electronic transmission of FOUO information (e.g., data, website, or e-mail) shall be by approved secure communications systems or systems utilizing other protective measures such as Public Key Infrastructure (PKI) or transport layer security (e.g., https). Use of wireless telephones should be avoided when other options are available. Transmission of FOUO by facsimile machine (fax) is permitted; the sender is responsible for determining that appropriate protection will be available at the receiving location prior to transmission (e.g., machine attended by a person authorized to receive FOUO;
fax located in a controlled government environment).
(3) FOUO information may only be posted to DoD websites consistent with security and access requirements specified in Reference (k).
(4) Additional guidance regarding FOUO information that may also require protection pursuant to the Privacy Act of 1974, as amended, may be found in Reference (r).
(5) Record copies of FOUO documents shall be disposed of according to provisions of chapter 33 of title 44, U.S.C. (Reference (v)) and the DoD Component records management directives. Non-record FOUO documents may be destroyed by any of the means approved for the destruction of classified information or by any other means that would make it difficult to recognize or reconstruct the information.
(6) The originator or other competent authority (e.g., initial FOIA denial and appellate authorities) shall terminate the FOUO status of specific information when circumstances indicate
DoDM 5200.01-V4, February 24, 2012
Change 1, 05/09/2018 that the information no longer requires protection from public disclosure. When the FOUO status of information is terminated in this manner, all known holders shall be notified, to the extent practical. Upon notification, holders shall efface or remove the FOUO markings, but records in file or storage need not be retrieved solely for that purpose. Information whose FOUO status has been terminated shall not be released to the public without the review and approval required by paragraph 1.f of this enclosure.
File details come from the government source that posted it.