Attachment 0011 - DD 2930.pdf
PDF 73 KB Posted
- Solicitation number
- Reposting_RFP_W911QY26RA007_MaterielFielding_MedicalLiaisonSupportServices
About this file
This document is a PDF viewer error message, not a federal contract opportunity file. The PDF failed to load properly and only displays a "Please wait..." notice with instructions to upgrade Adobe Reader. No contract information, solicitation details, requirements, pricing terms, response dates, or other substantive content is present in this document. The file cannot be summarized as a contract opportunity document.
View the file
Other files
Show all 23
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
Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
DRAFT
SAMPLE
PREVIOUS EDITION IS OBSOLETE.
Page of
DD FORM 2930, JUN 2017
PRIVACY IMPACT ASSESSMENT (PIA)
PRESCRIBING AUTHORITY: DoD Instruction 5400.16, "DoD Privacy Impact Assessment (PIA) Guidance". Complete this form for Department of Defense (DoD) information systems or electronic collections of information (referred to as an "electronic collection" for the purpose of this form) that collect, maintain, use, and/or disseminate personally identifiable information (PII) about members of the public, Federal employees, contractors, or foreign nationals employed at U.S. military facilities internationally. In the case where no PII is collected, the PIA will serve as a conclusive determination that privacy requirements do not apply to system.
SECTION 1: PII DESCRIPTION SUMMARY (FOR PUBLIC RELEASE)
a. The PII is: (Check one. Note: Federal contractors, military family members, and foreign nationals are included in general public.)
b. The PII is in a: (Check one.)
e. Do individuals have the opportunity to object to the collection of their PII?
(1) If "Yes," describe the method by which individuals can object to the collection of PII.
(2) If "No," state the reason why individuals cannot object to the collection of PII.
f. Do individuals have the opportunity to consent to the specific uses of their PII?
(1) If "Yes," describe the method by which individuals can give or withhold their consent.
(2) If "No," state the reason why individuals cannot give or withhold their consent.
g. When an individual is asked to provide PII, a Privacy Act Statement (PAS) and/or a Privacy Advisory must be provided. (Check as appropriate and provide the actual wording.)
h. With whom will the PII be shared through data/system exchange, both within your DoD Component and outside your Component?
(Check all that apply)
i. Source of the PII collected is: (Check all that apply and list all information systems if applicable)
j. How will the information be collected? (Check all that apply and list all Official Form Numbers if applicable)
k. Does this DoD Information system or electronic collection require a Privacy Act System of Records Notice (SORN)?
A Privacy Act SORN is required if the information system or electronic collection contains information about U.S. citizens or lawful permanent U.S. residents that is retrieved by name or other unique identifier. PIA and Privacy Act SORN information must be consistent.
SORN System Identifier SORN System Identifier If "Yes," enter SORN System Identifier SORN System Identifier SORN Identifier, not the Federal Register (FR) Citation. Consult the DoD Component Privacy Office for additional information or http://dpcld.defense.gov/ Privacy/SORNs/ or If a SORN has not yet been published in the Federal Register, enter date of submission for approval to Defense Privacy, Civil Liberties, and Transparency Division (DPCLTD). Consult the DoD Component Privacy Office for this date
l. What is the National Archives and Records Administration (NARA) approved, pending or general records schedule (GRS) disposition authority for the system or for the records maintained in the system?
SORN System Identifier
(2) If pending, provide the date the SF-115 was submitted to NARA.
SORN System Identifier
n. Does this DoD information system or electronic collection have an active and approved Office of Management and Budget (OMB) Control Number?
Contact the Component Information Management Control Officer or DoD Clearance Officer for this information. This number indicates OMB approval to collect data from 10 or more members of the public in a 12-month period regardless of form or format.
SORN System Identifier
SECTION 2: PII RISK REVIEW
a. What PII will be collected (a data element alone or in combination that can uniquely identify an individual)? (Check all that apply) If the SSN is collected, complete the following questions.
(DoD Instruction 1000.30 states that all DoD personnel shall reduce or eliminate the use of SSNs wherever possible. SSNs shall not be used in spreadsheets, hard copy lists, electronic reports, or collected in surveys unless they meet one or more of the acceptable use criteria.)
(1) Is there a current DPCLTD approved SSN Justification on Memo in place?
(4) Has a plan to eliminate the use of the SSN or mitigate its use and or visibility been identified in the approved SSN Justification request?
If "Yes," provide the unique identifier and when can it be eliminated?
If "No," explain.
(4) Has a plan to eliminate the use of the SSN or mitigate its use and or visibility been identified in the approved SSN Justification request?
SORN System Identifier
b. What is the PII confidentiality impact level2?
1The definition of PHI involves evaluating conditions listed in the HIPAA. Consult with General Counsel to make this determination.
2Guidance on determining the PII confidentiality impact level, see Section 2.5 “Categorization of PII Using NIST SP 800-122.” Use the identified PII confidentiality impact level to apply the appropriate Privacy Overlay low, moderate, or high. This activity may be conducted as part of the categorization exercise that occurs under the Risk Management Framework (RMF). Note that categorization under the RMF is typically conducted using the information types described in NIST Special Publication (SP) 800-60, which are not as granular as the PII data elements listed in the PIA table. Determining the PII confidentiality impact level is most effective when done in collaboration with the Information Owner, Information System Owner, Information System Security Manager, and representatives from the security and privacy organizations, such as the Information System Security Officer (ISSO) and Senior Component Official for Privacy (SCOP) or designees.
c. How will the PII be secured?
(1) Physical Controls. (Check all that apply)
(2) Administrative Controls. (Check all that apply)
(3) Technical Controls. (Check all that apply)
SECTION 3: RELATED COMPLIANCE INFORMATION
a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool3?
b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”.
Indicate the assessment and authorization status:
c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11?
SORN System Identifier If "Yes," Enter UII If unsure, consult the component IT Budget Point of Contact to obtain the UII.
3Guidance on Risk Management Framework (RMF) tools (i.g., eMASS, Xacta, and RSA Archer) are found on the Knowledge Service (KS) at https://rmfks.osd.mil.
SECTION 4: REVIEW AND APPROVAL SIGNATURES
Completion of the PIA requires coordination by the program manager or designee through the information system security manager and privacy representative at the local level. Mandatory coordinators are: Component CIO, Senior Component Official for Privacy, Component Senior Information Security Officer, and Component Records Officer.
Publishing: Only Section 1 of this PIA will be published. Each DoD Component will maintain a central repository of PIAs on the Component's public Web site.
DoD Components will submit an electronic copy of each approved PIA to the DoD CIO at: osd.mc-alex.dod-cio.mbx.pia@mail.mil.
If the PIA document contains information that would reveal sensitive information or raise security concerns, the DoD Component may restrict the publication of the assessment to include Section 1.
9.0.0.2.20120627.2.874785 DD Form 2930, "Privacy Impact Assessment (PIA)"
| CurrentPage: |
| PageCount: |
| 1. DOD INFORMATION SYSTEM/ELECTRONIC COLLECTION NAME:: |
| 2. DOD COMPONENT NAME: select from drop-down list.: |
| 3. PIA APPROVAL DATE: (cannot be completed until Section 4, Signature H and Date of Review are completed. Value should be the same as Section 4, Date of Review H): |
| b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”. - (2) If an assessment and authorization is not using RMF, indicate the projected transition date.: |
| SECTION 1: PII DESCRIPTION SUMMARY (FOR PUBLIC RELEASE) - a. The PII is: (Check one. Note: Federal contractors, military family members, and foreign nationals are included in general public.) - Select for "From members of the general public.": 0 |
| a. The PII is: (Check one. Note: Federal contractors, military family members, and foreign nationals are included in general public.) - Select for "From federal employees.": 0 |
| a. The PII is: (Check one. Note: Federal contractors, military family members, and foreign nationals are included in general public.) - Select for "from both members of the general public and Federal employees.": 0 |
| a. The PII is: (Check one. Note: Federal contractors, military family members, and foreign nationals are included in general public.) - Select for "Not Collected (if checked proceed to Section 4).": 0 |
| b. The PII is in a: (Check one.) - Select for "New DoD Information System.": 0 |
| b. The PII is in a: (Check one.) - Select for "New Electronic Collection.": 0 |
| b. The PII is in a: (Check one.) - Select for "Existing DoD Information System.": 0 |
| b. The PII is in a: (Check one.) - Select for "Existing Electronic Collection.": 0 |
| b. The PII is in a: (Check one.) - Select for "Significantly Modified DoD Information System.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "Yes.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - Select for "No.": 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| c. Does this DoD information system have an IT investment Unique Investment Identifier (UII), required by Office of Management and Budget (OMB) Circular A-11? - If "yes," enter UII.: 0 |
| g. When an individual is asked to provide PII, a Privacy Act Statement (PAS) and/or a Privacy Advisory must be provided. (Check as appropriate) - Select for "Privacy Act Statement.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "Telephone Interview.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "E-mail.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "E-mail.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "Official Form.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "Official Form.": 0 |
| h. Component CIO Reviewing Official Name - (3) Work Telephone: 0 |
| h. Component CIO Reviewing Official Name - (3) Work Telephone: 0 |
| j. How will the information be collected? (Check all that apply) - Select for "Paper.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "Paper.": 0 |
| j. How will the information be collected? (Check all that apply) - Select for "Information Sharing - System to System.: 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Other.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Other.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Other.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Other.": 0 |
| directed: |
| b. What is the PII confidentiality impact level? - Select for "High.": 0 |
| b. What is the PII confidentiality impact level? - Select for "High.": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Cipher Locks.": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Closed Circuit TV (CCTV).": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Combination Locks.": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Identification Badges.": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Key Cards.": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Safes.": 0 |
| c. How will the PII be secured? - (1) Physical Controls. (Check all that apply) - Select for "Security Guards.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. - If "Other," describe how the PII will be secured.: |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Backups Secured Off-site.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Encryption of Backups.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Methods to Ensure Only Authorized Personnel Access to PII.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Periodic Security Audits.": 0 |
| c. How will the PII be secured? - (2) Administrative Controls. (Check all that apply) - Select for "Regular Monitoring of Users' Security Practices.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Biometrics.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Command Access Card (CAC).": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Virtual Private Network (VPN).": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Virtual Private Network (VPN).": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Virtual Private Network (VPN).": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Virtual Private Network (VPN).": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Encryption of Data at Rest.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Encryption of Data in Transit.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Firewall.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Used Only for Privileged (Elevated Roles.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Used Only for Privileged (Elevated Roles.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Used Only for Privileged (Elevated Roles.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Role-Based Access Controls.": 0 |
| c. How will the PII be secured? - (3) Technical Controls. (Check all that apply) - Select for "Other.": 0 |
| SECTION 3: RELATED COMPLIANCE INFORMATION - a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Select for "Yes, DITPR.": 0 |
| a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Yes, DITPR - Enter DITPR System Identification Number.: |
| a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Select for "Yes, SIPRNET.": 0 |
| a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Yes, SIPRNET - Enter SIPRNET Identification Number.: |
| a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Select for "No.": 0 |
| a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Select for "No.": 0 |
| a. Is this DoD Information System registered in the DoD IT Portfolio Repository (DITPR) or the DoD Secret Internet Protocol Router Network (SIPRNET) Information Technology (IT) Registry or Risk Management Framework (RMF) tool? - Yes, RMF tool - Enter RMF tool Identification Number.: |
| b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”. - Indicate the assessment and authorization status: Select for "Interim Authorization to Test (IATT).": 0 |
| b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”. - Indicate the assessment and authorization status: Select for "Interim Authorization to Test (IATT).": 0 |
| b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”. - Indicate the assessment and authorization status: Select for "Interim Authorization to Test (IATT).": 0 |
| b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”. - Indicate the assessment and authorization status: Select for "Interim Authorization to Test (IATT).": 0 |
| b. DoD information systems require assessment and authorization under the DoD Instruction 8510.01, “Risk Management Framework for DoD Information Technology”. - Indicate the assessment and authorization status: Interim Authorization to Test (IATT) - Enter Date Granted.: |
| SECTION 4: REVIEW AND APPROVAL SIGNATURES - a. Program Manager or Designee Name : |
| h. Component CIO Reviewing Official Name - (1) Title: |
| h. Component CIO Reviewing Official Name - (2) Organization: |
| h. Component CIO Reviewing Official Name - (4) DSN: |
| h. Component CIO Reviewing Official Name - (5) E-mail address: |
| a. Program Manager or Designee - (6) Signature: |
| g. Senior Component Official for Privacy (SCOP) or Designee Name - (7) Date of Review: |
| b. Other Official (to be used at Component discretion): |
| b. Other Official (to be used at Component discretion) - (6) Signature: |
| c. Other Official (to be used at Component discretion): |
| c. Other Official (to be used at Component discretion) - (6) Signature: |
| d. Component Privacy Officer (CPO): |
| d. Component Privacy Officer (CPO) - (6) Signature: |
| e. Component Records Officer: |
| e. Component Records Officer - (6) Signature: |
| f. Component Senior Information Security Officer or Designee Name: |
| f. Component Senior Information Security Officer or Designee Name - (6) Signature: |
| h. Component CIO Reviewing Official Name: |
| h. Component CIO Reviewing Official Name - (6) Signature: |
| h. Component CIO Reviewing Official Name - (7) Date of Review: |
File details come from the government source that posted it. Updated .