7.1 Resources
The organization has to identify and supply the resources the ISMS needs to be set up, put into operation, maintained and continually improved.
Source: ISO/IEC 27001:2022, 7.1. 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.
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
- Records of staffing for ISMS roles and allocated time · Identity provider / directory
- Evidence of tools and services funded for security processes · Document repository
- Management review records addressing resource adequacy · Policy repository / GRC workspace
governing documentDocuments that govern the control
- An ISMS budget and resource plan approved by management · Policy repository / GRC workspace
First move
Common gaps auditors find
- Resource needs are never formally determined
- The ISMS depends on unfunded part-time effort
- Tooling needed for controls was never budgeted
- Resource shortfalls raised in reviews are not acted on
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