Clause 7 – Support

Clause 7.3 Awareness

Mandatory requirement

What it means in plain language

Everyone working for you must know the security policy, how they contribute to security and what happens if they do not follow the rules.

Is it mandatory? Yes. Clauses 4–10 are the management-system requirements; all of them must be met to be certified, and none can be excluded.

Documented information

  • Not explicitly required; records are strongly recommended.

Why this requirement matters

Awareness is about informed behaviour, not just issuing a policy. Teams should evidence that workers understand the security policy, their personal contribution to protection, and the consequences of ignoring rules. The strongest records usually combine onboarding, periodic refreshers, and targeted messages after relevant incidents or near misses.

Common auditor findings to check for

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

  • Staff have signed the policy acknowledgement, but interviews show they cannot explain how to report an incident or why the rule matters in their daily work.
  • Awareness messages are generic and infrequent, so high-risk behaviours such as phishing, weak authentication, or uncontrolled data sharing are not reinforced.
  • Managers assume team members know the consequences of nonconformance, yet disciplinary expectations and escalation paths are not clearly communicated.

How you can implement it

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

  • Run structured onboarding for every new starter and contractor whose work touches information security. Cover the policy, acceptable use, data handling, reporting channels, and role-specific risks, then collect acknowledgement and a quick knowledge check to show the message was received and understood.
  • Deliver periodic reinforcement using brief, risk-based topics tied to current threats or incidents, such as phishing, remote working, password hygiene, supplier data sharing, or lost devices. Use short sessions, posters, intranet notices, or scenario-based quizzes, and record who received each message.
  • Tailor awareness to role and context. For example, finance teams need fraud and payment redirection cues, developers need secure coding reminders, and managers need escalation and approval responsibilities. Retain evidence that messages were targeted rather than a single broadcast used for everyone.
  • After incidents, near misses, or control breaches, issue a concise lessons-learned notice describing the event type, the behaviour expected next time, and any process change. Keep the record in the awareness register so it links the lesson to a specific audience and date.

What an auditor will ask to see

  • Onboarding checklist, policy acknowledgement form, and any induction quiz results.
  • Awareness campaign calendar, attendance records, quiz scores, or intranet posts.
  • Targeted incident-learning bulletins or follow-up communications sent to affected teams.
  • Phishing simulation records, including user outcomes and follow-up coaching where needed.

Baseline documents in the kit

These free kit documents help you document or evidence clause 7.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.