EvidenceSheet

7.2 Competence

The organization must decide what competence is needed by people working under its control whose work affects information security performance; make sure they are competent through education, training or experience; where applicable act to acquire the competence and check those actions worked; and keep documented evidence of competence. The note gives examples such as training, mentoring or reassigning current staff, or hiring or contracting competent people.

Source: ISO/IEC 27001:2022, 7.2. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open ISO/IEC 27001:2022 in the compliance library.

Clauses 4 to 10 are the management-system requirements: none of them can be excluded when an organisation claims conformity. The 93 Annex A controls are a reference set: one may be excluded with a justification in the Statement of Applicability. Certification bodies assess conformity; the evidence lists here are what auditors commonly ask for, not a list the standard prescribes.

4
artefacts
0
held by a system
2
at each review
hard
to go live
HR system / LMS
where the evidence lives
teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Training, qualification and experience records for people in those roles · HR system / LMS
  • Records of actions taken to close competence gaps and evaluation of their effectiveness · HR system / LMS

governing documentDocuments that govern the control

  • Competence requirements for roles affecting information security performance · Policy repository / GRC workspace
  • Coverage of contractors and others working under the organization's control · HR system / LMS

First move

No system holds this evidence for you: it is people and documents. Reminders and routing to the owner still save time. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date.

Common gaps auditors find

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

7.1 Resources · 7.3 Awareness