Understanding the topic
Screening vendors can handle names, dates of birth, Social Security numbers, addresses, driver’s-license information, criminal records, employment and education details, credit information, medical or testing status, and candidate communications. Security review should reflect the sensitivity and actual data flow.
A checklist should produce evidence and decisions, not only yes-or-no answers. The employer should understand the product scope, hosting, integrations, subprocessors, support access, incident process, retention, and responsibilities shared with the employer.
Security domains to evaluate
The review should connect technical controls to how the proposed screening program will be configured.
- Data inventory, collection minimization, transmission, hosting locations, encryption, key management, and backups.
- Authentication, multifactor support, password controls, single sign-on, role-based access, user provisioning, and session management.
- Audit logs, report exports, integration tokens, API scopes, webhook security, support access, and administrative actions.
- Vulnerability management, secure development, independent testing, change control, monitoring, and business continuity.
- Incident response, notification, subprocessors, retention, deletion, contract terms, and customer responsibilities.
How to conduct the vendor review
Security review should begin before contract signature and continue through implementation and renewal.
- 1
Map the proposed data flow
Identify candidate, employer, provider, court, verifier, laboratory, clinic, ATS, HRIS, and subprocessor data exchanges.
- 2
Request scoped evidence
Obtain current policies, test summaries, certifications where applicable, architecture, subprocessor lists, and incident procedures.
- 3
Test the configured workflow
Review user roles, candidate links, exports, integrations, logs, offboarding, and data retention in the actual tenant.
- 4
Resolve contract and implementation gaps
Assign responsibility for controls, notification, deletion, support access, and configuration.
- 5
Monitor throughout the relationship
Review incidents, changes, attestations, access, integrations, users, and retention at defined intervals.
Security review mistakes
A logo, certificate, or questionnaire score does not prove that the employer’s configuration is secure.
- Reviewing corporate controls but ignoring shared credentials and broad employer permissions.
- Assuming encryption eliminates the risk of email attachments, exports, screenshots, or excessive access.
- Accepting a certification without checking scope, date, exceptions, and product coverage.
- Connecting an ATS integration with more data and permissions than the workflow requires.
- Failing to remove former users, rotate tokens, or delete test candidate data.
Employer-side controls still matter
The vendor cannot secure devices, accounts, exports, or decisions that remain under employer control.
- Use unique accounts, multifactor authentication, least privilege, and timely offboarding.
- Do not transmit sensitive identifiers or reports through ordinary email or chat.
- Limit exports and downloads and store necessary copies in approved systems.
- Review integrations, API keys, webhooks, service accounts, and administrator access.
- Maintain an incident contact, escalation path, retention schedule, and vendor-governance owner.
Putting the information into a screening program
The FTC advises businesses to know what personal information they hold, keep only what they need, protect it, dispose of it securely, and plan for incidents. These principles apply to both the vendor and employer.
Do not claim a certification or security feature that has not been verified for the proposed product and scope. Security questions should be answered with current evidence and a clear division of responsibilities.
PRIMARY SOURCES
Sources and further reading
- Protecting Personal Information: A Guide for BusinessFederal Trade Commission
RELATED SERVICES
