What this policy is
Defines what pre-employment screening is performed, on which roles, by whom, and under which legal frameworks (e.g. country-specific employment law).
Why every organization needs one
Background checks are an obvious mitigation for insider risk on sensitive roles — and a contractual requirement under most customer security questionnaires.
What a competent Background Verification Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Roles subject to screening
- Screening scope (criminal, credit, education, employment)
- Re-screening cadence for sensitive roles
- Vendor-managed screening provider relationship
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_background_verification_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.6.1 | Screening | People controls |
| ISO/IEC 27701:2025 | A.1.4.7 | Temporary files disposal | Privacy by design / default |
| ISO/IEC 27701:2025 | A.2.5.9 | Change of subcontractor | PII sharing, transfer & disclosure (processors) |
3 controls across 2 frameworks reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.