Updated 18 November 2026. Thomas Ferreira is a security engineer at nophi.sh, certified CISSP, GCFA, GCIH and GCFE.
Short answer: ISO/IEC 27001:2022 does not mention phishing simulations. Annex A control A.6.3 requires awareness, education and training suited to each person’s job, with regular updates, and clause 7.2 requires you to evaluate whether that training works and to keep the evidence. Dated phishing test results per person, the training assigned after each mistake and a trend over 6 to 12 months are the evidence most auditors expect for that.
ISO/IEC 27001 sets the requirements for an information security management system (ISMS): risk assessment, choice of controls, management involvement and continual improvement. The 2022 edition lists 93 controls in Annex A. A certification body accredited by a national accreditation body (UKAS in the United Kingdom, ANAB in the United States, COFRAC in France) issues the certificate for three years, with a surveillance audit every year.
What ISO 27001:2022 requires for security awareness
The standard covers awareness in two clauses of the management system and two Annex A controls. The table sums up what each one asks and the evidence that answers it.
| Requirement | What it asks, in substance | Evidence the auditor samples |
|---|---|---|
| Clause 7.2, competence | Define the competence needed for roles that affect security, train people where needed, evaluate the effectiveness of the actions taken, keep documented evidence | Role-based training plan, training records, results that show the training works |
| Clause 7.3, awareness | Everyone working under your control knows the security policy, their contribution to the ISMS and the implications of not conforming | Policy acknowledgement, awareness course records, staff interviews |
| Control A.6.3, awareness, education and training | Personnel and relevant interested parties receive awareness, education and training suited to their job function, and regular updates on policies and procedures | Training per role, campaign history, refresher schedule |
| Control A.5.7, threat intelligence | Collect and analyse information about threats to adapt your controls | Simulations built on threats you actually receive, reported suspicious emails |
| Clause 9.3.2, management review | Inputs include monitoring and measurement results and trends | Review minutes that show the phishing and training figures and the decisions taken |
Clause 7.2: evaluate the effectiveness of training
Clause 7.2 is where phishing simulations earn their place. It asks you to evaluate the effectiveness of the actions taken to build competence. Attendance alone does not show effectiveness: a course completed by everyone says nothing about what people do with a suspicious email. A simulation measures that behaviour, person by person, and its trend over several campaigns shows whether the training changes it.
Roles also matter here. A finance assistant who approves payments and a developer who deploys code face different attacks. The auditor expects training adapted to those roles.
Clause 7.3: what everyone must know
Clause 7.3 lists three things every person working under your control must be aware of:
- the information security policy;
- their contribution to the effectiveness of the ISMS, including the benefits of better security performance;
- the implications of not conforming with the ISMS requirements.
Contractors and suppliers who access your systems are covered too, as “persons doing work under the organization’s control”.
Control A.6.3: training suited to the job, with regular updates
A.6.3 is the Annex A control most directly about awareness. It replaced A.7.2.2 of the 2013 edition. Two words carry the audit: appropriate, which means adapted to the job function, and regular, which means updates over time, not a one-off. Simulation scenarios tied to each team’s work (a fake supplier invoice for accounting, a fake HR portal, an urgent request from a director) answer the first. A schedule of campaigns and refreshers answers the second.
Control A.5.7: train on the threats you actually receive
A.5.7 was new in 2022. It asks you to gather and analyse threat information and use it to adapt your controls. For awareness, that means simulating the attacks your staff actually see (CEO fraud and business email compromise, fake document shares, credential pages) and using the suspicious emails your staff report as input.
Does ISO 27001 require phishing simulations?
The standard does not require them by name. In practice they are the simplest way to meet the effectiveness requirement of clause 7.2 and the “regular updates” of A.6.3 with evidence an auditor can check. The alternative (quizzes only, or attendance sheets) gives weaker evidence of behaviour.
For what a programme can achieve, see our phishing click rate benchmarks: KnowBe4 reports a 33.1% click rate on a first test among its customers and 4.1% after 12 months of training (KnowBe4, 2025 report). These are vendor figures without a control group, so set your own target against your own baseline.
What the auditor checks at stage 2 and surveillance audits
Stage 1 reviews your documentation. Stage 2 checks that the ISMS actually runs. Surveillance audits in years 2 and 3 check that it keeps running.
Training records per person. The auditor takes the staff list and checks that each person has a dated training record. For people hired in the last 12 months, they check that awareness happened during onboarding. A record without names and dates proves nothing.
Phishing simulation results. The figures auditors ask for:
- the click rate per campaign and its trend;
- the report rate (people who flagged the email as suspicious);
- the share of staff included in campaigns, and who was never tested;
- what happened after a mistake: training assigned, completed or overdue.
Continual improvement. ISO 27001 follows the Plan, Do, Check, Act cycle. The auditor looks for progress, not perfection. A click rate that falls from one campaign to the next shows the programme works. Results that stagnate with no corrective action, or a programme that measures nothing, invite a nonconformity.
Management review. Clause 9.3.2 lists monitoring and measurement results among the inputs of the management review. The auditor reads the minutes and checks that the awareness figures and the decisions taken appear there.
Interviews. The auditor talks to randomly chosen staff outside IT: “What do you do with a suspicious email?”, “Where is the security policy?”. Staff who cannot answer reveal weak awareness, even with complete records.
Common awareness nonconformities
- no evidence for contractors who access your systems;
- training with no measure of effectiveness (clause 7.2);
- no documented awareness for people hired in the last 6 months;
- simulation results getting worse with no documented action plan;
- management review minutes with no awareness figures.
The A.6.3 evidence pack to export before the audit
| Evidence | Contents | What it shows |
|---|---|---|
| Results per campaign | Date, scenario, people targeted, click and report rates, result per person, training assigned | Behaviour is tested in real conditions and each person is followed up (A.6.3, 7.2) |
| 12-month trend | Click and report rates across campaigns, first versus latest, per department | Continual improvement (PDCA) |
| Training record per person | Courses assigned and completed, with dates, new joiners included | Individual awareness (7.3) and onboarding coverage |
| Coverage | People included in campaigns, people never tested, over time | Awareness reaches the whole organisation, non-technical teams included |
| Management review inputs | Summary of the figures and the decisions for the next period | Results feed the management review (9.3.2) |
If your ISMS lives in a compliance platform, you can also push these records there. Our guide Send phishing simulation results to Vanta and Drata shows how, with the API fields to map.
How nophi.sh produces this evidence
nophi.sh covers the awareness part of clause 7.3 and control A.6.3. The certificate covers your whole ISMS, so the policy, the risk assessment and the review itself remain your documents.
Phishing simulations (A.6.3, 7.2). Each phishing simulation campaign records, for each person, the email received, the date and what they did (opened, clicked, entered credentials, reported). Clicks from email security scanners are set aside so they do not count as human clicks. The catalogue holds 66 English and 69 French scenarios, each with a category, a difficulty and the red flags taught on the debrief page, so you can match scenarios to each team’s job.
Training after a mistake (7.3). When someone clicks or enters credentials, nophi.sh assigns a short course and a practice exercise of 10 emails (8 out of 10 to pass). The built-in course “Phishing Awareness Fundamentals” has five short lessons and a quiz with an 80% passing score. Reminders go out before the deadline; once it passes, the person’s manager is told if you recorded a manager email. You can add your own content, such as a presentation of your security policy and the implications of not conforming, to cover the three points of clause 7.3.
Dashboard (9.3). A risk score per person and per department, click and report rate trends, repeat clickers, people never tested, overdue training and the suspicious emails your staff reported.
Audit report and exports. The PDF report holds a summary, trends, risk distribution, results per department and training follow-up. The CSV export gives the per-person detail. The REST API returns the same results per recipient, for a compliance platform or your own records.
Reported emails (A.5.7). When someone forwards a suspicious email to the nophi.sh address, or uses the Microsoft 365 Report button set up to that address, they usually get an AI verdict with its reasons within one to two minutes, and your security contacts are alerted. These reports show what your staff really receive, and you can turn them into your own simulation templates.
Pricing is 1 euro excl. VAT per person per month, minimum 10 people, billed monthly with no commitment (pricing). Run a baseline campaign during the 14-day trial (full product, no card) to start your evidence.
ISO 27001 or SOC 2?
SOC 2 is an attestation report issued by a CPA firm under the AICPA framework, over an observation period. ISO 27001 leads to a three-year certificate from an accredited body. European customers and public tenders usually ask for ISO 27001; SOC 2 is mostly requested by US customers. The phishing and training records above serve both, and they also cover part of the training duties of NIS2.
Sources (checked on 18 November 2026): ISO/IEC 27001:2022, UKAS, ANAB, COFRAC, AICPA, SOC suite of services, ENISA, awareness raising, KnowBe4 Phishing by Industry Benchmarking Report 2025. Clause and control wording is summarised from ISO/IEC 27001:2022; buy the standard from ISO or your national standards body for the full text.
Frequently asked questions
Does ISO 27001 require phishing simulations?
No clause or control of ISO/IEC 27001:2022 names phishing simulations. Control A.6.3 requires awareness, education and training suited to each job function, with regular updates, and clause 7.2 requires you to evaluate the effectiveness of the training and keep documented evidence. A phishing simulation is the most direct way to measure that effectiveness: it tests behaviour in real conditions and produces dated, per-person results an auditor can sample.
What awareness evidence does an ISO 27001 stage 2 auditor ask for?
Usually four things: dated training records per person (new joiners included), phishing simulation results per campaign (click rate, report rate, trend), evidence that results lead to action (training assigned after a mistake, corrective actions) and the management review minutes where these results were discussed (clause 9.3.2). The auditor also interviews staff outside IT to check they know the security policy and what to do with a suspicious email.
How many phishing campaigns should we run before the certification audit?
The standard sets no number. Auditors look for a programme that runs and improves, so a single campaign the week before the audit shows little. Three or four campaigns spread over 6 to 12 months, with a baseline first and the training that followed each mistake, give the auditor a trend to read.
Is ISO 27001 A.6.3 the same as A.7.2.2 in the 2013 version?
Yes, in substance. ISO/IEC 27001:2013 had the control A.7.2.2 Information security awareness, education and training. The 2022 revision renumbered the Annex A controls into four themes and the same requirement became A.6.3, in the people controls. Old procedures that still cite A.7.2.2 should be updated, as auditors now work from the 2022 numbering.
Do contractors need awareness training under ISO 27001?
Clause 7.3 covers all persons doing work under the organisation's control, and A.6.3 covers personnel and relevant interested parties. Contractors who use your systems or data are in scope. Include them in your campaigns and training, or obtain equivalent assurance through the supplier controls A.5.19 and A.5.20, and keep the evidence.
What does nophi.sh cost for an ISO 27001 awareness programme?
nophi.sh costs 1 euro excl. VAT per person per month, with a minimum of 10 people, billed monthly with no commitment. Simulations, training, the PDF audit report, CSV exports, the API and the MCP server are included. For 50 people, 12 months of evidence cost 600 euros excl. VAT. The 14-day trial needs no card.
ISO 27001 or SOC 2 for a European company?
ISO/IEC 27001 leads to a certificate valid for three years, issued by an accredited certification body, with surveillance audits each year. SOC 2 is an attestation report issued by a CPA firm under the AICPA framework. European customers and tenders usually ask for ISO 27001; SOC 2 is mostly requested by US customers. Both ask for security awareness evidence, and the same phishing and training records serve both.