A.6 People controls

A.6.3 Information security awareness, education and training

Not mandatory by default – decided in your SoA

What it means in plain language

Give staff awareness, education and training on security appropriate to their role, and repeat it regularly.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Awareness, education, and training are most effective when they are role-specific, repeatable, and measurable against the risks people actually face. A generic annual slide deck may not equip developers, service desk staff, or managers to recognise incidents, handle data correctly, or follow escalation paths, so the program needs practical scenarios, ownership, and tracked completion. This control also supports the organization’s broader competence and awareness expectations.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Training exists but is one-size-fits-all, so privileged users or developers never receive role-specific guidance on secure administration, code handling, or approval boundaries.
  • Completion records are incomplete or fragmented across HR and local spreadsheets, making it difficult to show who attended which session and when refreshers were due.
  • No practical reinforcement is used, so staff may have attended training but still miss phishing cues, reporting steps, or handling rules in day-to-day work.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Maintain a training register that maps each audience to required topics, delivery method, owner, due date, and completion status. HR or L&D can host attendance data, while ISMS owners define the risk-based syllabus for starters, annual refreshers, and targeted sessions after incidents, control changes, or new threats. Include contractors where their duties touch organizational information or systems.
  • Design modules around common failure mechanisms: weak passwords, approval bypass, phishing, misplaced records, unsafe file sharing, and improper remote-working habits. Add role-based tracks for developers, administrators, finance, and managers, with short scenario questions or tabletop exercises to test judgment rather than recall. Keep content current by referencing internal incidents, threat intelligence, and changes to tools or procedures.
  • Use illustrative cadence such as onboarding within the first month, annual refreshers for all staff, quarterly phishing simulations, and ad hoc briefings after major changes. Managers should close completion gaps for their teams and escalate repeat non-attendance. When staff move roles, trigger re-training for new access, new data types, or new processing activities before the change goes live.
  • Retain evidence that shows not just attendance but understanding: quiz scores, simulation outcomes, sign-in sheets, webinar logs, and follow-up coaching for failures. Where training is mandatory for specific roles, record exemptions, compensating guidance, and sign-off by the accountable manager. Periodically review metrics for late completion, repeat click rates, and topics needing stronger emphasis.

What an auditor will ask to see

  • Training register entries showing topic, audience, owner, delivery date, completion status, and re-training due date.
  • Role-based slide deck or microlearning outline with secure coding, admin, or remote-working scenarios.
  • Phishing simulation report with targeted cohort, campaign date, click or report results, and follow-up actions.
  • New starter induction checklist signed after awareness session and before system access activation.

Baseline documents in the kit

These free kit documents help you document or evidence A.6.3. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with 7.2 — Competence and A.6.8 — Information security event reporting. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.