Most teams starting ISO/IEC 27001:2022 hit the same problem early: a blank page and a long list of required documents. A document toolkit is meant to remove that problem. Used well, it saves weeks of drafting. Used badly, it produces a thick binder that describes an organisation you are not.
This article explains what a good ISO 27001 toolkit should contain, how to check its quality before you rely on it, and how to turn templates into a working information security management system (ISMS).
What an ISO 27001 document toolkit is (and is not)#
A toolkit is a set of editable templates, checklists and examples that cover the documented information the standard expects, plus the policies and procedures that support your chosen controls. You edit it to fit your organisation.
It is not a certificate, and it is not a shortcut around the work. The standard expects you to understand your context, assess your own risks, and operate the controls you select. A toolkit gives you structure and wording. It cannot supply your risk decisions, your asset list or your evidence that processes are actually followed. Auditors will look for those.
It also cannot guarantee a certification outcome. That depends on how well your ISMS is implemented and operated, and on the certification body's assessment.
What a good toolkit should include#
ISO/IEC 27001:2022 has two parts to cover: the management system requirements in clauses 4 to 10, and the 93 Annex A controls grouped into four themes (organizational, people, physical and technological). A useful toolkit maps to both.
Management system documents#
- ISMS scope statement and a context and interested parties analysis.
- Information security policy and measurable security objectives.
- Risk assessment and treatment methodology, with a risk register and treatment plan template.
- Statement of Applicability (SoA) covering every Annex A control, with inclusion and exclusion reasons.
- Roles, responsibilities and authorities, plus competence and awareness records.
- Internal audit programme, audit checklist and report templates.
- Management review agenda and minutes template.
- Nonconformity and corrective action log.
Control-level policies and procedures#
These should reflect the Annex A themes. Typical examples include:
- Access control, acceptable use and password or authentication rules.
- Asset management and information classification.
- Supplier and third-party security.
- Incident management and business continuity arrangements.
- Secure development, change management and backup.
- Physical security, remote working and onboarding or offboarding.
- Cryptography, logging and monitoring, and vulnerability management.
Supporting material#
Checklists, forms, worked examples, awareness presentations and a gap assessment checklist make the toolkit easier to use. Worked examples matter most: they show what a completed risk register or SoA looks like, not just an empty form.
How to judge a toolkit before you rely on it#
Not all toolkits are equal. Check the following before you commit time to one.
- Is it written for the 2022 edition? Older material refers to the previous Annex A structure. The 2022 edition reorganised the controls into four themes and added new ones, so the SoA and control mapping must match.
- Are the files editable? You need Word and Excel-type formats you can change freely, not locked PDFs.
- Does it cover the full set? Look for management system documents, control documents and records, not only policies.
- Are there examples? Completed samples reduce guesswork on risk scoring, objectives and audit records.
- Is the language usable? Policies should be short and clear enough for staff to read. Dense legal-style text rarely gets followed.
- Does it help you start? A gap assessment checklist tells you what already exists and what is missing, so you do not rewrite things you already do well.
How to turn templates into a working ISMS#
The order you work in matters more than the number of documents. A sensible sequence looks like this.
- Run a gap assessment. Compare current practice with the requirements and controls. Note what exists, what is informal and what is missing.
- Define scope and context. Decide which business units, locations, systems and services the ISMS covers, and who has an interest in it.
- Assess risk. Build your asset list, identify threats and vulnerabilities, score risks using your own criteria and agree owners.
- Select controls and complete the SoA. Let the risk results drive which controls apply. Do not simply accept all or none by default.
- Adapt the policies and procedures. Replace generic wording with your tools, teams, approval routes and timelines. Delete sections that do not apply.
- Roll out and train. A policy nobody has read is not a control. Brief staff, assign owners and start keeping records.
- Operate, then audit. Run the processes for long enough to generate evidence, carry out an internal audit and hold a management review.
When you reach the certification audit, it helps to know what each stage looks at. Our guide to the ISO 27001 Stage 1 vs Stage 2 audit explains the difference.
Common mistakes when using a toolkit#
- Leaving template text unchanged. Auditors quickly notice policies that do not match how the company operates.
- Over-documenting. The standard does not require a procedure for everything. Write what you need to run and control the process.
- Copying someone else's risk assessment. Risks, assets and tolerances are specific to you.
- Treating the SoA as a formality. It should be justified, current and consistent with your risk treatment.
- Skipping records. Procedures without evidence of operation will not demonstrate that the ISMS works.
- No ownership. Every policy, risk and control needs a named owner who is expected to maintain it.
Frequently asked questions#
Can a toolkit alone get us ISO 27001 certified?#
No. A toolkit provides documentation, but certification depends on a certification body assessing that your ISMS is implemented and operating. You still need to carry out risk assessment, apply controls, train people, run an internal audit and hold a management review.
Do we need all 93 Annex A controls?#
Not necessarily. You select controls based on your risk treatment, then record in the Statement of Applicability which are included, which are excluded and why. Exclusions need a sound justification, and you should compare your selected controls against the Annex A list so that none is overlooked.
Who should adapt the documents?#
The people who run the processes should write or review them, with a coordinator, often the information security or compliance manager, keeping them consistent. Documents written in isolation by one person tend to describe an ideal process, not the real one.
If you want a structured starting point, the ISO 27001:2022 Toolkit offers 180+ editable templates, examples and a gap assessment checklist that you can tailor to your own ISMS.

Leave a Comment