Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Mandatory requirement Documented information required
What it means in plain language
People whose work affects information security must be competent – through education, training or experience. Define what competence each role needs, close gaps (training, mentoring, hiring) and keep evidence.
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
Evidence of competence.
Why this requirement matters
Competence is more than training attendance; it is the demonstrated ability to perform security-relevant work correctly. Teams should define role-based skills, identify gaps, and keep evidence that people responsible for the ISMS, administration, or development can carry out their tasks with appropriate knowledge and experience. Auditors commonly probe whether competence requirements are practical and role-specific.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Role expectations are described in job titles only, but there is no matrix showing what knowledge, experience, or qualifications are needed for each security-relevant task.
Training certificates exist, yet there is no link between courses completed and the actual responsibilities performed, leaving competence gaps unreviewed.
Temporary staff or new joiners handle sensitive tasks without mentoring, sign-off, or recorded assessment of readiness for privileged or operational duties.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define competence criteria per role, such as ISMS management, system administration, secure development, incident handling, supplier oversight, or internal auditing. Keep criteria measurable: policy knowledge, tool proficiency, regulatory awareness, and experience with the actual systems or processes used by the organisation.
Maintain a competence matrix that compares required and actual capability for each named role-holder. Where a gap exists, record the chosen response: training, supervision, paired working, certification, reassignment, or recruitment. Reassess after a reasonable period and update the matrix when responsibilities change.
Use the Training & Awareness Register to record formal courses, workshops, mentoring, hands-on exercises, and post-training assessments. Include dates, provider, topic, result, and manager approval that the learning was applied to the relevant role, not just attended.
For high-impact duties, keep direct evidence of practical competence, such as sample change approvals, incident decisions, access reviews, or code review comments signed off by a supervisor. If competence depends on external expertise, record the vendor, scope, and how internal staff validate outputs.
What an auditor will ask to see
Competence matrix linking each role to required skills, experience, and current status.
Training certificates, attendance logs, mentoring notes, and assessment results.
Performance sign-off or supervisory review records for security-critical tasks.
CVs, professional memberships, or recruitment records where expertise was sourced externally.
Baseline documents in the kit
These free kit documents help you document or evidence clause 7.2. Each one is tailored to your organization when you build your kit.
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.