Join our Newsletter — 33% off our NHI Course
Home› Guides› ISO 27001 Annex A.6 People controls: All 8…
Guide Security Policies & Awareness

ISO 27001 Annex A.6 People controls: All 8 Controls with Audit Evidence

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 13 min read
On this page

Annex A.6 holds only 8 of the 93 ISO 27001 controls, but they run through HR, legal, line management and the service desk, so the evidence is scattered and the ISMS team rarely owns it. The people theme follows an individual from screening before hire, through employment terms, training and remote working, to discipline, confidentiality and duties after they leave, and asks everyone to report security events. Auditors sample real people for these controls: recent joiners, recent leavers, remote workers and anyone disciplined. This guide takes each of the 8 controls in ISO/IEC 27001:2022 Annex A in turn, paraphrases the intent, names a realistic owner and lists the records that hold up at certification. It is for ISMS managers, HR and people teams, and internal auditors. Control intent is paraphrased, not quoted; read the normative text in ISO/IEC 27001:2022 and the guidance in ISO/IEC 27002:2022. For the full catalogue, see the ISO 27002 Controls Guide.

Key takeaways

  • HR owns most of the evidence. Screening files, contracts, disciplinary records and leaver checklists sit in HR systems, so agree access and sampling with HR before the audit.
  • Auditors sample people, not policies. Expect a request for a list of joiners and leavers in the period, then a sample traced through every relevant control.
  • There are no new people controls in 2022. 6.7 remote working renames the 2013 teleworking control, and 6.8 merges event and weakness reporting into one control.
  • Screening must be proportionate and lawful. 6.1 asks for checks in line with law and the risk of the role, so the depth differs between a privileged administrator and a general employee.
  • People controls end at the leaver step, but identities often do not. 6.5 duties after leaving only work if access removal under the A.5 and A.8 controls happens on time, including shared and machine credentials the person held.

The 8 people controls at a glance

ISO/IEC 27002:2022 (edition 3, published February 2022, 152 pages, no amendment listed by ISO) numbers the people controls 6.1 to 6.8. They group naturally into three stages of employment plus one cross-cutting control.

StageControlTypical ownerCore evidence
Before employment6.1 ScreeningHR, with security for role risk tiersScreening standard, role tiers, completed check records
Before employment6.2 Terms and conditions of employmentHR, legalContract templates with security clauses, signed contracts
During employment6.3 Information security awareness, education and trainingSecurity awareness leadTraining plan, completion records, role-based training
During employment6.4 Disciplinary processHRDisciplinary policy referencing security, anonymised case log
During employment6.7 Remote workingIT, securityRemote working policy, device and connection controls
After employment6.5 Responsibilities after termination or change of employmentHR, line managersExit reminders, contract clauses that survive termination, mover records
Cross-stage6.6 Confidentiality or non-disclosure agreementsLegalNDA templates, signed agreements, review history
Cross-stage6.8 Information security event reportingSecurity operationsReporting channels, reports received, feedback to reporters

Before employment: 6.1 and 6.2

ControlIntent in plain wordsEvidence auditors usually sample
6.1 ScreeningVerify candidates before they join and, where justified, during employment, in proportion to the role, the information they will access, the risks and the applicable lawScreening standard with role tiers; for sampled joiners, proof that each required check finished before access was granted; rescreening records for high-risk roles
6.2 Terms and conditions of employmentContracts state the security responsibilities of both the individual and the organisationCurrent contract templates with security, acceptable use and confidentiality clauses; signed contracts for sampled joiners; contractor and agency terms

Making screening proportionate

  • Tier roles by risk: map each role to a tier based on privileged access, access to sensitive data, financial authority and ability to change production. NIST SP 800-53 PS-2 position risk designation is a useful model.
  • Define checks per tier: typical components are identity verification, right to work, employment history, references, qualifications and, where the law permits for the role, criminal record checks. The UK government's Baseline Personnel Security Standard (version 7.0, June 2024) is an example of a published baseline that underpins further vetting.
  • Close the timing gap: access is often provisioned on day one while checks are still running. Either gate provisioning on screening completion or record a conditional start with limited access, approved by the hiring manager.
  • Cover non-employees: contractors, agency staff and outsourced administrators need equivalent checks, done by you or contractually required of the supplier (NIST PS-7). Remote hiring adds identity fraud risk; see the Insider Threat from Fake IT Workers Guide (North Korean IT Worker Schemes).
  • Respect data protection law: screening is personal data processing. The UK ICO, for example, publishes employment guidance covering recruitment and selection, verifying candidate information and keeping recruitment records. Retain screening results only as long as justified.

For depth on check types and legal limits, see the Personnel Security and Background Screening Guide and the Personnel Security Policy Template.

During employment: 6.3, 6.4 and 6.7

ControlIntent in plain wordsEvidence auditors usually sample
6.3 Information security awareness, education and trainingStaff and relevant interested parties receive awareness, education and training suited to their role, with regular updates on policy and proceduresAnnual training plan, completion rates by population, role-based modules for administrators and developers, induction records for sampled joiners
6.4 Disciplinary processA formal, communicated disciplinary process exists for policy violationsDisciplinary policy that names security breaches, evidence it is communicated (handbook, intranet), anonymised record of cases handled
6.7 Remote workingSecurity measures protect information accessed, processed or stored outside the organisation's premisesRemote working policy, managed device and encryption status, remote access controls, guidance for working in public places

6.3 beyond completion rates

Auditors increasingly ask how training content was chosen and whether it changed behaviour. Base the plan on your risk assessment and incident data, give privileged users and developers role-based training (NIST AT-3), and keep evidence that content changed after a relevant incident. Phishing simulations are optional under the standard but provide useful effectiveness data. See the Security Awareness and Human Risk Management Guide, the Security Awareness Metrics guide and the Security Awareness and Training Policy Template.

6.4 handled fairly

The control expects a process that is formal and known in advance, and that treats people consistently. Link it to a just culture: honest mistakes reported promptly should be handled differently from deliberate or repeated violations, otherwise people stop reporting under 6.8. HR keeps the case records; the ISMS needs only proof that the process exists, is communicated and has been used where appropriate.

6.7 remote working in practice

  • Scope: home, travel, co-working and third-party sites, and personal devices if you allow them. See the BYOD Security Programme.
  • Technical evidence: device management enrolment, full-disk encryption, patch status, MFA on remote access (NIST AC-17) and remote wipe for lost devices; these technical measures are evidenced under A.8 but referenced by the 6.7 policy.
  • Behavioural evidence: rules for printing, screen privacy, family use of devices and reporting loss. See the Remote Working Security for Staff Guide and the Remote Work Security Checklist.

After and across employment: 6.5, 6.6 and 6.8

ControlIntent in plain wordsEvidence auditors usually sample
6.5 Responsibilities after termination or change of employmentSecurity duties that continue after someone leaves or changes role are defined, communicated and enforcedContract clauses that survive termination, exit interview or letter reminding of duties, mover records showing access adjusted
6.6 Confidentiality or non-disclosure agreementsConfidentiality agreements reflect the organisation's needs, are signed by staff and relevant parties, and are reviewed regularlyNDA templates with review date, signed agreements for staff, contractors and visitors with access, register of third-party NDAs
6.8 Information security event reportingPersonnel can report observed or suspected security events quickly through appropriate channelsPublished reporting channels, reports received over the period, triage records, feedback given to reporters

6.5 and the leaver hand-off

6.5 covers the duties that outlive employment, but auditors test it alongside asset return (5.11) and access rights (5.18). Trace sampled leavers from the HR termination date to the last access removal, including SaaS accounts, shared mailboxes, API tokens and any service account passwords the person knew, which must be rotated. Movers are the weaker case: access from the old role is often kept. See the Employee Offboarding Security Guide, the Employee Offboarding Security Checklist and the Joiner-Mover-Leaver Guide.

6.6 kept current

The control asks for agreements that are identified, documented and reviewed, not a one-off signature. Keep a register of NDA templates with an owner and review date, and check that contractors and visitors with access signed before access began.

6.8 that people actually use

  • Channels: a phishing report button, a service desk category and a named mailbox or phone line for out-of-hours, all published in induction.
  • What to report: suspected phishing, lost devices, misdirected emails, unusual system behaviour and observed weaknesses. The 2022 control covers both events and weaknesses.
  • Feedback loop: acknowledge every report and tell reporters the outcome where you can; volume rises when people see action.

See the Security Incident Report Form Template. Reports that become incidents move into the A.5 incident controls 5.24 to 5.28; see the ISO 27001 Annex A.5 Organisational controls guide.

Where identity fits

Every people control has an identity counterpart. Screening decides who gets an account; terms and NDAs set the rules for its use; training covers credential hygiene and MFA prompts; 6.5 depends on timely deprovisioning. Two gaps recur. First, credentials a person knew but did not own, such as shared administrator passwords, break-glass accounts and service account keys, are not rotated when they leave. Second, the people a machine identity answers to change: when the named owner of a service account or AI agent leaves, ownership must transfer under the mover and leaver process. See the Insider Threat and Identity Guide and the Service Account Security Guide.

Rolling out and evidencing A.6

  1. Agree ownership with HR and legal: record the owner and evidence source for each of the 8 controls in the ISO 27001 Statement of Applicability Template, and agree how auditors will see HR records without exposing personal data (redacted extracts or viewing in place).
  2. Set the screening tiers: define role tiers and checks per tier, then confirm the hiring workflow cannot grant privileged access before checks complete.
  3. Update templates: add security, acceptable use, confidentiality and post-termination clauses to employee, contractor and agency templates; date and version them.
  4. Build the training plan: induction, annual refresher and role-based modules, with completion tracked by population and follow-up for non-completion.
  5. Publish reporting channels: test the phishing button and mailbox, and measure time to acknowledge.
  6. Trace a sample before stage 2: take five joiners, five movers and five leavers from the period and trace each through 6.1, 6.2, 6.3, 6.5 and 6.6; fix gaps and raise your own nonconformities. See the ISMS Internal Audit and Management Review guide.
  7. Keep a fallback: if an HR system migration loses historic screening or contract records, keep the dated export as evidence and log the gap as a corrective action rather than re-signing documents with new dates.

Decision guidance: scaling A.6

SituationPractical approachWatch out for
Start-up or small teamOne screening tier plus an enhanced tier for administrators; security clauses in a single contract template; short annual trainingFounders and early staff never screened or never signed current terms
Large or multinationalCountry-specific screening matrices approved by local counsel; HR system as the evidence sourceChecks lawful in one country applied in another where they are restricted
Heavy contractor useSupplier contracts require equivalent screening and training, with right to auditContractors outside the training platform and leaver process
Fully remote workforceIdentity verification at hire, managed devices only, 6.7 policy as a core documentHiring fraud and unmanaged home devices

Detection and measurement

  • Screening before access: percentage of joiners whose required checks completed before privileged or sensitive access was granted (6.1).
  • Training completion: induction completed within [30 days] of start and annual training completion by population, including contractors (6.3).
  • Leaver access removal: percentage of leavers with all access, including SaaS and shared credentials, removed within the agreed time (6.5).
  • Mover access clean-up: percentage of movers whose previous role access was removed within the agreed time (6.5).
  • Reporting health: number of staff reports per month and median time to acknowledge (6.8).
  • NDA coverage: share of contractors and third parties with access who have a signed, current agreement (6.6).

Common failure patterns

  • Access before screening: accounts provisioned on day one while checks are pending, with no record of the conditional start.
  • Contractors outside the system: agency staff and outsourced administrators missing from screening, training and leaver evidence.
  • Training as a tick box: completion near 100% but content unchanged for years and no role-based module for administrators.
  • Movers keep everything: access accumulates across role changes because only leavers trigger removal.
  • Shared secrets survive departures: administrator and service account passwords known to a leaver are never rotated.
  • Punitive culture suppresses reporting: people who report their own mistakes are disciplined, so 6.8 reports dry up.

Framework mapping

These mappings are for orientation and are not an official crosswalk; NIST notes that mappings between control sets are not always one to one.

A.6 controlNIST SP 800-53 Rev. 5NIST CSF 2.0
6.1 ScreeningPS-2, PS-3, PS-7GV.RR-04
6.2 Terms and conditions of employmentPS-6, PS-9, PL-4GV.RR-04
6.3 Awareness, education and trainingAT-2, AT-3PR.AT-01, PR.AT-02
6.4 Disciplinary processPS-8GV.RR-04
6.5 After termination or changePS-4, PS-5GV.RR-04
6.6 Confidentiality or NDAsPS-6GV.RR-04
6.7 Remote workingAC-17PR.AA-03, PR.IR-01
6.8 Event reportingIR-6DE.AE-02

CIS Controls v8.1 Control 14 (security awareness and skills training) aligns with 6.3 and the reporting element of 6.8. See the CIS Control 14 Security Awareness and Skills Training Guide.

Practitioner checklist

  • Name an owner and evidence source for each of the 8 A.6 controls, with HR and legal agreeing their part.
  • Define screening tiers by role risk and block privileged access until checks complete.
  • Apply equivalent screening, training and leaver steps to contractors and agency staff.
  • Version contract and NDA templates with security and post-termination clauses, and review them annually.
  • Run induction, annual and role-based training, and change content after relevant incidents.
  • Remove previous-role access for movers, not only leavers.
  • Rotate shared and service account credentials known to leavers, and transfer machine identity ownership.
  • Publish simple reporting channels and give feedback to reporters.
  • Trace a sample of joiners, movers and leavers through A.6 before each audit.

Standards and references

Related NHI Mgmt Group resources: ISO 27001 Certification Guide · ISO 27001 Annex A.5 Organisational controls · ISO 27001 Annex A.8 Technological controls · Insider Threat Programme Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.