Document
Pia_0704-0507
ICR 202107-0704-012 · OMB 0704-0507 · Object 114850400.
⚠️ Notice: This form may be outdated. More recent filings and information on OMB 0704-0507 can be found here:
Document [pdf]
Download: pdf | txt
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. 1. DOD INFORMATION SYSTEM/ELECTRONIC COLLECTION NAME: Basic Employee And Security Tracker (BEAST) 3. PIA APPROVAL DATE: 2. DOD COMPONENT NAME: 08/30/2018 White House Communications Agency SECTION 1: PII DESCRIPTION SUMMARY (FOR PUBLIC RELEASE) a. The PII is: (Check one. Note: foreign nationals are included in general public.) From members of the general public From Federal employees and/or Federal contractors From both members of the general public and Federal employees and/or Federal contractors Not Collected (if checked proceed to Section 4) b. The PII is in a: (Check one) New DoD Information System New Electronic Collection Existing DoD Information System Existing Electronic Collection Significantly Modified DoD Information System c. Describe the purpose of this DoD information system or electronic collection and describe the types of personal information about individuals collected in the system. To manage personnel and security records for the purpose of validation, analysis, and appraisal throughout the life-cycle. This system is used to track security, sensitive items such as access/accountable badges and employment data of military personnel, DoD Government employees, and DoD contractors who support the White House Communications Agency (WHCA) and/or the White House Military Office (WHMO) d. Why is the PII collected and/or what is the intended use of the PII? (e.g., verification, identification, authentication, data matching, mission-related use, administrative use) Mission Related Use (e.g., administrative use, background investigations, authentication, identification and verification). e. Do individuals have the opportunity to object to the collection of their PII? Yes No (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. The members can object at anytime to the collection of their PII; however failure to consent could lead to non-consideration for Presidential Support Duty. Employment/Duty at WHMO/WHCA is 100% voluntary. f. Do individuals have the opportunity to consent to the specific uses of their PII? Yes No (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. During the security interview, at the time of application or anytime thereafter, the member can non-consent to the use of their PII; however failure to consent could lead to non-consideration or dismissal from Presidential Support Duty. Employment/Duty at WHMO/WHCA is 100% voluntary. 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.) Privacy Act Statement Privacy Advisory Not Applicable PRIVACY ACT STATEMENT: The Authority for collecting the requested information resides in Executive Orders 10450 (Security requirements for Government employment), 11652 (Classification and declassification of national security information and material) & 9397 (Federal Agency Use of Social Security Numbers). The information is used in making security determinations, granting access to classified/ PSD protected information and for making personnel management decisions. Routine uses include determining the scope and coverage of a personnel security investigation, checking investigative leads assuring completeness of the investigation, and providing evaluators and/or adjudicators with basic personal history information relevant to security/suitability and are referenced in the SORN. Information may be DD FORM 2930, JUN 2017 PREVIOUS EDITION IS OBSOLETE. AEM Designer Page 1 of 8 disclosed to and maintained by Government agencies and administrative personnel involved in processing security actions that evolve during the course of these determinations. When populated with data, this questionnaire becomes PII and must be encrypted prior to transmittal. The personal data collection will be transferred into an approved system of record, under an Authority to Operate, granted on 10 Jul 09, under federal register chronicle 78 FR 70543, 26 Nov 13, 79 FR 34299, 16 Jun 14 and maintained for up to 75 years. The SORN allowing this collection can be found at: http://dpcld.defense.gov/Privacy/SORNsIndex/DOD-Component-Article-View/Article/570748/kwhc08/ h. With whom will the PII be shared through data exchange, both within your DoD Component and outside your Component? (Check all that apply) Within the DoD Component Specify. Human Resource Office, Security and the System Administrators (IAW non-disclosure agreements) Other DoD Components Specify. White House Military Office (WHMO) Other Federal Agencies Specify. United States Secret Service (USSS) State and Local Agencies Specify. Contractor (Name of contractor and describe the language in the contract that safeguards PII. Include whether FAR privacy clauses, i.e., 52.224-1, Privacy Act Notification, 52.224-2, Privacy Act, and FAR 39.105 are included in the contract.) Specify. Other (e.g., commercial providers, colleges). Specify. i. Source of the PII collected is: (Check all that apply and list all information systems if applicable) Individuals Databases Existing DoD Information Systems Commercial Systems Other Federal Information Systems j. How will the information be collected? (Check all that apply and list all Official Form Numbers if applicable) E-mail Official Form (Enter Form Number(s) in the box below) Face-to-Face Contact Paper Fax Telephone Interview Information Sharing - System to System Website/E-Form Other (If Other, enter the information in the box below) WHCA Form 89 (WHCA Security Questionnaire), DISA recruiting website: http://www.disa.mil/careers/whca, DD Form 1172-2 (Application for Identification Card/DEERS), J2 COR-OGA Form. Members can also opt to email the data, following encryption and data in motion requirements. 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. Yes No If "Yes," enter SORN System Identifier KWHC-08 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 If "No," explain why the SORN is not required in accordance with DoD Regulation 5400.11-R: Department of Defense Privacy Program. N/A 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? (1) NARA Job Number or General Records Schedule Authority. DD FORM 2930, JUN 2017 GRS: N1-330-08-010 (Pending) PREVIOUS EDITION IS OBSOLETE. AEM Designer Page 2 of 8 (2) If pending, provide the date the SF-115 was submitted to NARA. 5/19/2017 (3) Retention Instructions. Basic Employee and Security Tracker (BEAST). Proposed disposition for the BEAST database is Temporary - maintain for 75 years, then destroy. m. What is the authority to collect information? A Federal law or Executive Order must authorize the collection and maintenance of a system of records. For PII not collected or maintained in a system of records, the collection or maintenance of the PII must be necessary to discharge the requirements of a statue or Executive Order. (1) If this system has a Privacy Act SORN, the authorities in this PIA and the existing Privacy Act SORN should be similar. (2) If a SORN does not apply, cite the authority for this DoD information system or electronic collection to collect, use, maintain and/or disseminate PII. (If multiple authorities are cited, provide all that apply). (a) Cite the specific provisions of the statute and/or EO that authorizes the operation of the system and the collection of PII. (b) If direct statutory authority or an Executive Order does not exist, indirect statutory authority may be cited if the authority requires the operation or administration of a program, the execution of which will require the collection and maintenance of a system of records. (c) If direct or indirect authority does not exist, DoD Components can use their general statutory grants of authority (“internal housekeeping”) as the primary authority. The requirement, directive, or instruction implementing the statute within the DoD Component must be identified. 5 U.S.C. 1303 Investigations; 5 U.S.C 3301, Civil service; 44 U.S.C. 3101, Administrative Procedure Act; DoDI 5025.01, DoD Directives Program; and E.O. 9397 (SSN), as amended 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. Yes No Pending (1) If "Yes," list all applicable OMB Control Numbers, collection titles, and expiration dates. (2) If "No," explain why OMB approval is not required in accordance with DoD Manual 8910.01, Volume 2, " DoD Information Collections Manual: Procedures for DoD Public Information Collections.” (3) If "Pending," provide the date for the 60 and/or 30 day notice and the Federal Register citation. OMB Control Number - 0704-0507 DD FORM 2930, JUN 2017 PREVIOUS EDITION IS OBSOLETE. AEM Designer Page 3 of 8 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) Biometrics Birth Date Child Information Citizenship Disability Information DoD ID Number Driver's License Education Information Emergency Contact Employment Information Financial Information Gender/Gender Identification Home/Cell Phone Law Enforcement Information Legal Status Mailing/Home Address Marital Status Medical Information Military Records Mother's Middle/Maiden Name Name(s) Official Duty Address Official Duty Telephone Phone Other ID Number Passport Information Personal E-mail Address Photo Place of Birth Position/Title Race/Ethnicity Rank/Grade Protected Health Information (PHI)1 Religious Preference Records Security Information Work E-mail Address If Other, enter the information in the box below Social Security Number (SSN) (Full or in any form) Previous Work Experience 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 (dated within two (2) years) DPCLTD approved SSN Justification on Memo in place? Yes No If "Yes," provide the signatory and date approval. If “No,” explain why there is no SSN Justification Memo. 22 Nov 2017 (2) Describe the approved acceptable use in accordance with DoD Instruction 1000.30 “Reduction of Social Security Number (SSN) Use within DoD”. Acceptable Use is documented in the PITC Basic User Agreement and Acceptable Use Acknowledgment that the member signs upon being assigned to the agency. We have reduced the use of the SSN in all areas controlled by WHCA. Once the military services remove it from the evaluation processes, we will respectively end the use as well. Same consideration for credit agencies. (3) Describe the mitigation efforts to reduce the use including visibility and printing of SSN in accordance with DoD Instructoin 1000.30, “Reduction of Social Security Number (SSN) Use within DoD”. WHCA must use the SSN because our determination for suitability is based largely upon credit history and information, as this continues to be the largest insider threat; as long as credit agencies are reporting based on the SSN as a unique identifier, WHMO/WHCA must inheritably use this identifier also. (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. Yes No Credit background checks and military evaluations. These are our only two uses. As indicated, agencies outside of our purview use these identifiers, so we must also by default. b. What is the PII confidentiality impact level2? 1 Low Moderate High The definition of PHI involves evaluating conditions listed in the HIPAA. Consult with General Counsel to make this determination. 2 Guidance 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. DD FORM 2930, JUN 2017 PREVIOUS EDITION IS OBSOLETE. AEM Designer Page 4 of 8 c. How will the PII be secured? (1) Physical Controls. (Check all that apply) Cipher Locks Closed Circuit TV (CCTV) Combination Locks Identification Badges Key Cards Safes Security Guards If Other, enter the information in the box below SCIF and physical blast door (2) Administrative Controls. (Check all that apply) Backups Secured Off-site Encryption of Backups Methods to Ensure Only Authorized Personnel Access to PII Periodic Security Audits Regular Monitoring of Users' Security Practices If Other, enter the information in the box below (3) Technical Controls. (Check all that apply) Biometrics Common Access Card (CAC) DoD Public Key Infrastructure Certificates Encryption of Data at Rest Encryption of Data in Transit External Certificate Authority Certificates Firewall Intrusion Detection System (IDS) Least Privilege Access Role-Based Access Controls Used Only for Privileged (Elevated Roles) User Identification and Password Virtual Private Network (VPN) If Other, enter the information in the box below d. What additional measures/safeguards have been put in place to address privacy risks for this information system or electronic collection? SCIF and physical blast door DD FORM 2930, JUN 2017 PREVIOUS EDITION IS OBSOLETE. AEM Designer Page 5 of 8
| File Type | application/pdf |
| File Title | PIA_0704-0507.pdf |
| Author | HechtAS |
| File Modified | 2021-09-20 |
| File Created | 2021-09-20 |