USA Hire PTA_032724_Final.pdf

PDF 519 KB Posted

Attached to
OPM USA HIRE SUPPORT SERVICES II
Solicitation number
47QFMA25K0009
Issued by
Not on record

About this file

This document is an OPM Privacy Threshold Analysis (PTA) for the USA Hire (USAH-PF2) system. The document details a federal hiring platform operated by the Office of Personnel Management (OPM) that utilizes the PerformanceFit2 (PF2) vendor tool to deliver assessment, online interview, and proctoring services to federal government agencies. The system collects applicant information including name, personal email address, and audio/video recordings during on-demand interviews, and serves members of the public, OPM employees, contractors, and employees of other federal agencies.

The Privacy Threshold Analysis indicates the system is operationally active since January 1, 2020, with an Authority to Operate (ATO) valid until October 20, 2026. The system has a moderate confidentiality and integrity rating and a low availability rating. All privacy controls outlined in NIST SP800-53 Rev.5 are marked as "met". The Privacy Office noted that the primary update since the last PTA is the addition of video recording for on-demand interviews, and an updated Privacy Impact Assessment is currently under review and expected to be completed by the end of the third quarter of FY24.

View the file

Other files

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

OPM 5079

Rev. 9/2022

OPM Privacy Threshold Analysis OPIM will use this form to determine whether a new or updated Privacy Impact Assessment (PIA) is required and whether a new or updated System of Records Notice (SORN) is required under the Privacy Act of 1974. OPIM will also use it to document the continuous monitoring of privacy risk and mitigation for the project, program, or system.

Please complete the form and submit it to PIAMail@opm.gov. Upon receipt of this PTA, the Chief Privacy Officer, or designee, will adjudicate the PTA and return it to you. As appropriate, you will be provided with further guidance on completing a PIA and SORN.

Summary Information

Date of Completion:

Project or Program Name:

Office:

Branch/Group:

Type of Project or Program:

Project/ Program status:

Date first developed:

Pilot launch date: Pilot end date:

PTA last updated:

ATO Status (if applicable):

ATO expiration date (if applicable):

mailto:PIAMail@opm.gov

OPM PTA for

Rev. 9/2022

Project, Program, or System Manager

Name:

Office Acronym: Title:

Phone: Email:

Information System Security Officer (ISSO) (if applicable)

Name:

Phone: Email:

Specific PTA Questions

1. Overview:

Please provide a detailed description of the project, program or system and its purpose in a way a non-technical person could understand. The description should include the purpose of the project, which individuals are involved or impacted, a general lifecycle of the data, where the data is stored, and any collection instruments (e.g., forms, mobile application) used to collect information, as well as any other information needed to describe the project. If this is an updated PTA due to changes in a project, please describe the specific changes and/or upgrades that are triggering the update. If this is a renewal PTA due to an impending expiration, please state whether there were any changes since the last PTA approval.

Rev. 9/2022

2. From whom does the Project or Program collect, maintain, use, or disseminate information?

Please check all that apply.

This project does not collect, maintain, use, or disseminate any personally identifiable information

Members of the public

OPM employees

Contractors working on behalf of OPM

Employees of other federal agencies

3. Please identify all information that is collected, generated, or retained (such as names, addresses, emails, etc.) for each category of individual or population.

Name

Date of Birth

Place of Birth

Age

Citizenship

SSN

Home Address

Alias

Nicknames

Personal Email Address

Personal Cell Number

Resume or Curriculum

Business Financial Information

Tax Identification Number

Passport Number

Bank Account

Credit Card

Other Financial Account Number

Driver’s License/State ID Number

Social Media Handle/ID

Biometric Identifiers

Retirement

CSA/ CSF Number

Unique Entity Identifier

Nationality

Sexual Orientation

Race

Ethnicity

Mother’s Maiden Name

Protected Health Information

Other. Please list:

Rev. 9/2022

3(a) Does this Project, Program, or System collect, maintain, use, or disseminate Social Security numbers (SSN) or other types of stand-alone sensitive information?

No.

Yes.

3(b) Please provide the specific legal basis for collecting the SSN:

3(c) If the SSN is needed to carry out the functions and/or fulfill requirements of the Project, System, or Program, please explain why it is necessary and how it will be used.

3(d) If the Project, Program, or System requires the use of SSN, what actions are being taken to abide by Public Law No. 115-59, “Social Security Number Fraud Prevention Act of 2017,” 42 U.S.C. § 405, which requires the use of privacy-enhancing SSN alternatives when there are technological, legal, or regulatory limitations to eliminating the SSN? Note: even if you are properly authorized to collect SSNs, you are required to use an alternate unique identifier. If there are technological, legal, or regulatory limitations to eliminating the SSN, privacy-enhancing alternatives should be taken, such as masking, truncating, or encrypting the SSN, or blocking the display of SSNs in hard copy or digital formats.

Rev. 9/2022

4. How does the Project, Program, or System retrieve information?

By a unique identifier. Please list all unique identifiers used:

By a non-unique identifier or other means. Please describe:

5. What is the records retention schedule(s) for the information collected for each category type (include the records schedule number)? If no schedule has been approved, please provide proposed schedule, or plans to determine it.

Note: If no records schedule is in place or are unsure of the applicable records schedule, please reach out to the OPM Records Officer.

5(a) How does the Project, Program, or System ensure that records are disposed of or deleted in accordance with the retention schedule (e.g., technical/automatic purge, manual audit)?

6. Does this Project, Program, or System connect, receive, or share PII with any other Office, projects, programs, or systems?

No.

Yes. If yes, please list:

7. Does this Project, Program, or System connect, receive, or share PII with any external (non-OPM) government or non-government partners or systems?

No.

Yes. If yes, please list:

Rev. 9/2022

8. Is this sharing pursuant to new or existing information sharing agreement (MOU, MOA, etc.)? If applicable, please provide agreement as an attachment.

Please describe applicable information sharing governance in place:

9. Does the Project, Program, or System have a mechanism to track external disclosures of an individual’s PII?

No. What steps will be taken to develop and maintain the accounting:

Yes. In what format is the accounting maintained:

10. Does this Project, Program, or System use or collect data involving or from any of the following technologies:

Social Media

Advanced analytics

Live PII data for testing

No

11. Does the planned effort include any interaction or intervention with human subjects via pilot studies, exercises, focus groups, surveys, equipment or technology, observation of public behavior, review of data sets, etc. for research purposes?

No.

Yes.

12. Does the Project, Program, or System provide role-based or additional privacy training for personnel who have access, in addition to annual privacy training required of all OPM personnel?

No.

Yes. If yes, please list:

Rev. 9/2022

13. Is there a FIPS 199 determination? No.

Yes. Please indicate the determinations for each of the following:

Confidentiality:

Low Moderate High Undefined

Integrity:

Low Moderate High Undefined

Availability:

Low Moderate High Undefined

Completed by the OPM Chief Privacy Officer or Designee

Privacy Office Reviewer:

Date Review Completed:

PTA Expiration Date:

Designation

Privacy Sensitive System: Yes No

Category of System:

If “other” is selected, please describe:

Privacy compliance and assurance (PCA):

Privacy compliance documentation in progress

PTA sufficient at this time

PIA required

SORN required

Privacy Act Statement Required

PRA clearance required

Records Schedule Required

New information sharing arrangement required

Rev. 9/2022

PIA:

SORN:

Privacy Office Comments:

Please describe rationale for privacy compliance determination above, and any further action(s) that must be taken by Office.

Rev. 9/2022

Privacy Controls Privacy controls are the administrative, technical, and physical safeguards employed within organizations to protect and ensure the proper handling of PII. The privacy control families can be implemented at the organization, office, program, or information system level, under the leadership of the Senior Agency Official for Privacy (SAOP) or Chief Privacy Officer (CPO) and in coordination with the Chief Information Security Officer (CISO), Chief Information Officer (CIO), program officials, and legal counsel. NIST SP800-53 Rev.5 provides a summary of the privacy controls. Indicate, in the context of this PTA, whether the control is met (Y), not met (N), or Not Applicable (N/A).

Control Number

Privacy Controls (NIST SP800-53 Rev.5)

Control Status

PT Authority and Purpose

PT-2 Authority to Process Personally Identifiable Information

PT-3 Personally Identifiable Information Processing

PM-3 Information Security and Privacy Resources

PM-18 Privacy Program Plan

PM-19 Privacy Program Leadership Role

TR-3 Dissemination of Privacy Program Information

RA-3 Risk Assessment

RA-8 Privacy Impact Assessment

SA-1 Policies and Procedures

SA-4 Acquisition Process

SA-9 External System Services

CA-2 Control Assessments

AT-1 Policies and Procedures

AT-2 Literacy Training and Awareness

AT-3 Role-based Training

Rev. 9/2022

Control Number

Privacy Controls (NIST SP800-53 Rev.5)

Control Status

AT-3(5) Role-based Training / Processing Personally Identifiable Information

PL-4 Rules of Behavior

PM-27 Privacy Reporting

AR-7 Privacy-Enhanced System Design and Development

PM-20 Dissemination of Privacy Program Information

PM-21 Accounting of Disclosures

PM-22 Personally Identifiable Information Quality Management

PM-24 Data Integrity Board

SI-1 Policies and Procedures

SA-8(33) Security and Privacy Engineering Principles / Minimization

SI-12(1) Information Management and Retention / Limit PII Elements

MP-6 Media Sanitization

SI-12 Information Management and Retention

SI-12(3) Information Management and Retention / Information Disposal

SI-12(2) Information Management and Retention / Minimize PII in Testing, Training and Research

PT-4 Consent

AC-1 Policies and Procedures

AC-3(14) Access Enforcement / Individual Access

SI-18 Personally Identifiable Information Quality Operations

Rev. 9/2022

Control Number

Privacy Controls (NIST SP800-53 Rev.5)

Control Status

SI-18(4) Personally Identifiable Information Quality Operations / Individual Requests

SI-18(5) Personally Identifiable Information Quality Operations / Notice of Correction or Deletion

PM-25 Minimization of PII used in Testing, Training, and Research

PM-26 Complaint Management

PM-5(1) System Inventory / Inventory of Personally Identifiable Information

IR-8 Incident Response Plan

IR-8(1) Incident Response Plan / Breaches

PT-5 Privacy Notice

PT-5(1) Privacy Notice / Just-In-Time Notice

PT-5(2) Privacy Notice / Privacy Act Statements

PT-6 System of Records Notice

AC-21 Information Sharing

AU-2 Event Logging

OPM Privacy Threshold Analysis
Summary Information
Project, Program, or System Manager
Information System Security Officer (ISSO) (if applicable)
Specific PTA Questions
1.Overview:
2.From whom does the Project or Programcollect, maintain, use, or disseminateinformation?
3.Please identify all information that is collected, generated, or retained (such as names,addresses, emails, etc.) for each category of individual or population.
3(a) Does this Project, Program, or System collect, maintain, use, or disseminate Social Security numbers (SSN) or other types of stand-alone sensitive information?
3(b) Please provide the specific legal basis for collecting the SSN:
3(c) If the SSN is needed to carry out the functions and/or fulfill requirements of the Project, System, or Program, please explain why it is necessary and how it will be used.
3(d) If the Project, Program, or System requires the use of SSN, what actions are being taken to abide by Public Law No. 115-59, “Social Security Number Fraud Prevention Act of 2017,” 42 U.S.C. § 405, which requires the use of privacy-enhancing SSN alternatives when there are technological, legal, or regulatory limitations to eliminating the SSN?
4.How does the Project, Program, orSystem retrieve information?
5.What is the records retentionschedule(s) for the information collectedfor each category type (include the recordsschedule number)? If no schedule has beenapproved, please provide proposedschedule, or plans to determine it.
5(a) How does the Project, Program, or System ensure that records are disposed of or deleted in accordance with the retention schedule (e.g., technical/automatic purge, manual audit)?
6.Does this Project, Program, or Systemconnect, receive, or share PII with anyother Office, projects, programs, orsystems?
7.Does this Project, Program, or Systemconnect, receive, or share PII with anyexternal (non-OPM) government or non-government partners or systems?
8.Is this sharing pursuant to new orexisting information sharing agreement(MOU, MOA, etc.)? If applicable, pleaseprovide agreement as an attachment.
9.Does the Project, Program, or Systemhave a mechanism to track externaldisclosures of an individual’s PII?
10.Does this Project, Program, or Systemuse or collect data involving or from any ofthe following technologies:
11. Does the planned effort include any interaction or intervention with human subjects via pilot studies, exercises, focus groups, surveys, equipment or technology, observation of public behavior, review of data sets, etc. for research purposes?
12.Does the Project, Program, orprovide role-based or additional privacytraining for personnel who have access, inaddition to annual privacy training requiredof all OPM personnel?
13. Is there a FIPS 199 determination?
Completed by the OPM Chief Privacy Officer or Designee
Designation
Privacy Office Comments:

Privacy Controls

Date of Completion: 03/27/2024
Office: [HRS]
BranchGroup: [HRS]
ProjectType: [System]
ProjectStatus: [Operational]
Date first developed: 01/01/2020
Pilot launch date:
Pilot end date:
PTA last updated: 12/06/2022
ATOstatus: [Complete]
ATO expiration date if applicable: 10/20/2026
Project or Program Name: USA Hire (USAH-PF2)
ManagerName: Patrick Sharpe
Acronym: [FSC/USAH Program Office]
Title: USA Hire Program Manager
ManagerPhone: (202)373-8185
ManagerEmail: Patrick.Sharpe@opm.gov
ISSOname: Thomas Koomson
ISSOphone: 202-213-5568
ISSOemail: Thomas.Koomson@opm.gov
Overview: OPM created the USA Hire program to meet the hiring needs of Federal government agencies, utilizing the vendor tool PerformanceFit2 (PF2) to deliver assessment and online interview services. OPM provides assessment, online interview, and proctoring services to other agencies on a reimbursable basis, through inter-agency agreements under the provisions of the Revolving Fund, 5 U.S.C. §1304 (e)(1). USA Hire is an assessment option that combines multiple choice and simulation-based test types that can be delivered in an online or in-person proctored setting, as well as a live and on-demand online interview option. Live interviews are conducted during scheduled times and on-demand interviews are completed by applicants in a defined time period. USA Hire collects applicant email, first name, & last name from USAJOBS and USA Staffing to email invitations to applicants that meet minimum qualifications. USA Hire also collects applicant audio and video recordings during on-demand interviews. One of USA Hire's vendors, PearsonVue, collects applicant email, first name, last name, and digital signature for verification against identification at in-person test sessions.
CollectNo: Off
CollectPublic: Yes
CollectOPM: Yes
CollectContractors: Yes
CollectOtherAgencies: Yes
CollectedName: Yes
CollectedDOB: Off
CollectedPlaceBirth: Off
CollectedAge: Off
CollectedCitizenship: Off
CollectedSSN: Off
CollectedHomeAddress: Off
CollectedAlias: Off
CollectedNickname: Off
CollectedPersonalEmail: Yes
CollectedPersonalCell: Off
CollectedResume: Off
CollectedBusinessFinancial: Off
CollectedTIN: Off
CollectedPassport: Off
CollectedBank: Off
CollectedCredit: Off
CollectedOtherFinancial: Off
CollectedLicense: Off
CollectedSocial: Off
CollectedBiometric: Off
CollectedRetirement: Off
CollectedCSA: Off
CollectedEntity: Off
CollectedNationality: Off
CollectedSexualOrientation: Off
CollectedRace: Off
CollectedEthnicity: Off
CollectedMotherMaiden: Off
CollectedHealth: Off
CollectedOther: Yes
CollectedOtherText: Applicant Signature (only for in-person test sessions proctored by PearsonVue).

Audio and video recording (only for on-demand online interviews)

SSNlegal: N/A
SSNjustification: N/A
FraudPrevention: N/A
3aCollectSSN: No
RetrieveInfoUnique: Yes
UniqueIdentifiers: First name, last name, email address, USAJOBS Globally Unique Identifier (GUID)
RetrieveInfoNonUnique: Off
NonUniqueIdentifiers:
RecordsSchedule: GRS 2.1, item 050 (DAA-GRS-2014-0002-0006), GRS 2.1, item 051 (DAA-GRS-2014-0002-0007) and GRS 2.1, item 070 (DAA-GRS-2014- 00020012) are the current approved NARA schedules.
RecordsDisposal: Manual purge upon decommissioning in accordance within NIST standards.
PIIinternal: Yes
ShareWithOPM: USA Hire receives the first name, last name, and email address of job seekers from USAJOBS and USA Staffing.
PIIexternal: Yes
ShareExternal: The information in USA Hire is available outside of OPM only to those Federal agencies who are customers of USA Hire.
SharingAgreement: [Updated]
InfoSharingGovernance: All Federal Agencies customers have information sharing agreements with OPM, and all customer employees must agree to rules of behavior. Existing agreements and rules of behavior will be updated for customer agencies using USA Hire.
TrackExternalDisclosureMaintainAccounting:
TrackExternalDisclosure: Yes
Accounting format: The underlying USA Hire platform maintains a complete audit trail of all user access to candidate records and can generate reports.
CollectDataSM: Off
CollectDataAdvancedAnalytics: Off
CollectDataLivePII: Off
CollectDataNo: Yes
HumanSubjects: Yes
RoleBasedTraining: Yes
RoleBasedTrainingList: The Federal agencies who use USA Hire services provide their HR Staff and Hiring Managers with system access appropriate to role-based training and need-to-know basis.
FIPS199: Yes. Please indicate the determination for confidentiality, integrity, and availability below
Confidentiality: Moderate
Integrity: Moderate
Availability: Low
Reviewer: [Josh Oswalt]
Date Review Completed: 03/27/2024
PTA Expiration Date: 03/26/2025
PrivacySensitiveSystem: Yes
Category: [System]
CategoryOther:
DocumentationInProgress: Off
PTAsufficient: Off
PIArequired: Yes
SORNrequired: Yes
PASrequired: Off
PRArequired: Off
ScheduleRequired: Off
ArrangementRequired: Off
PIAstatus: [Covered]
PIA: USA Hire (July 2020)
SORNstatus: [Covered]
SORN: OPM/GOVT-5 Recruiting, Examining, and Placement Records

OPM/GOVT-6 Personnel Research and Test Validation Records PrivacyOfficeComments: As the system contains and maintains PII, a PIA is required and was last updated in July 2020. The system also pulls information by a personal identifier, and is covered by two existing OPM SORNs.

The updated PIA is currently under review by the Privacy Office and will be completed no later than the end of 3rd quarter FY24.

The only change since the previous PTA is that USA Hire now collects video recording for on-demand interviews (previously it was only audio recording).

PT: [Yes]
PT-2: [Yes]
PT-3: [Yes]
PM-3: [Yes]
PM-18: [Yes]
PM-19: [Yes]
TR-3: [Yes]
RA-3: [Yes]
RA-8: [Yes]
SA-1: [Yes]
SA-4: [Yes]
SA-9: [Yes]
CA-2: [Yes]
AT-1: [Yes]
AT-2: [Yes]
AT-3: [Yes]
AT-3(5): [Yes]
PL-4: [Yes]
PM-27: [Yes]
AR-7: [Yes]
PM-20: [Yes]
PM-21: [Yes]
PM-22: [Yes]
PM-24: [Yes]
SI-1: [Yes]
SA-8(33): [Yes]
SI-12(1): [Yes]
MP-6: [Yes]
SI-12: [Yes]
SI-12(3): [Yes]
SI-12(2): [Yes]
PT-4: [Yes]
AC-1: [Yes]
AC-3(14): [Yes]
SI-18: [Yes]
SI-18(5): [Yes]
SI-18(4): [Yes]
PM-25: [Yes]
PM-26: [Yes]
PM-5(1): [Yes]
IR-8: [Yes]
IR-8(1): [Yes]
PT-5: [Yes]
PT-5(1): [Yes]
PT-5(2): [Yes]
PT-6: [Yes]
AC-21: [Yes]
AU-2: [Yes]

File details come from the government source that posted it. Updated .