ISO/IEC 27001:2022 A.6.1 — Screening

What this control requires

Background verification checks on all candidates to become personnel shall be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations and ethics and be proportional to the business requirements, the classification of the information to be accessed and the perceived risks.

In plain English

Background verification checks on all candidates to become personnel shall be carried out prior to joining the organization and on an ongoing basis taking into consideration applicable laws, regulations and ethics and be proportional to the business requirements, the classification of the information to be accessed and the perceived risks. In practice, this means you can prove you information information-level controls on a defined cadence.

Why it matters

ISO 27001 certification depends on showing each Annex A control is either implemented or explicitly justified for exclusion in the Statement of Applicability (SoA). Certification bodies sample controls during surveillance audits, and a missing SoA entry — or implementation that doesn't match the SoA wording — is a finding.

What an auditor looks for

An ISO 27001 lead auditor looks for: (1) an SoA entry covering the control with justification, (2) a documented procedure or policy implementing it, (3) records that prove the procedure runs (logs, tickets, training records) and (4) management-review evidence that effectiveness is monitored.

Within People controls, the assessor will trace your implementation back to the catalogue reference (Annex A A.6.1) and look for objective evidence on the latest two assessment cycles.

How to implement

1. Write a short policy stating intent, scope and named owner.
2. Encode it as a platform guardrail — SCP, Azure Policy initiative, Organisation Policy, or repository policy.
3. Wire a monitoring signal that catches drift (CSPM rule, SIEM rule, scheduled query, Workspace alert) and ticket it.
4. Review on a documented cadence and capture the review in the risk register or compliance tracker.

Operational checklist

• Information. Document the trigger, the owner and the cadence.
• Management. Document the trigger, the owner and the cadence.
• Classification. Document the trigger, the owner and the cadence.
• Identity. Document the trigger, the owner and the cadence.
• Access. Document the trigger, the owner and the cadence.
• Scope: information, management, people.

Evidence to collect

• Identity Scan. IAM / IdP exports — Entra ID, Okta, IAM Identity Center, Workspace directory — showing accounts, roles, MFA state and last sign-in.

Identity analytics (Okta, SailPoint, Access Analyzer) demonstrates least-privilege. Focus: Screening.

How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

• SOC 2 (2017 TSC) CC1.5 — Accountability for Internal Control Responsibilities
• NIST SP 800-171 Rev. 3 3.13.4 — Information in Shared System Resources
• CIS Controls v8 9.2 — Use DNS Filtering Services
• GDPR Article 12 — Transparent information, communication and modalities for the exercise of the rights of the data subject
• NIST SP 800-53 Rev. 5 AU-10(2) — Validate Binding Of Information Producer Identity

Related controls in ISO/IEC 27001:2022

• Annex A A.5.2 — Information security roles and responsibilities
• Annex A A.8.23 — Web filtering
• Annex A A.5.16 — Identity management
• Annex A A.5.33 — Protection of records
• Annex A A.5.15 — Access control
• Annex A A.5.18 — Access rights

References

• ISO/IEC JTC 1/SC 27 — ISO/IEC 27001:2022
• Catalogue identifier: Annex A A.6.1

Topics: identity accessidentity managementaccess reviewprivileged access