ISO Standards

ISO 27001 Documents Required for Certification

ISO 27001 Documents Required for Certification
In short

ISO 27001 documents required for certification include the ISMS scope, information security policy, risk assessment and treatment method and results, the Statement of Applicability, security objectives, and records such as audit results and management review minutes. Auditors also expect supporting policies and procedures for the controls you apply. Keep them short and make sure they match real practice.

In this article
  1. What are the ISO 27001 documents required for certification?
  2. Which records must you keep as evidence?
  3. What other policies and procedures do auditors expect?
  4. How do you write documents that pass an audit?
  5. Frequently asked questions

ISO 27001 documents required for certification are a common source of confusion. Some companies write hundreds of pages they do not need. Others miss a mandatory record and meet a finding at the audit. This article separates what the standard requires from what is simply good practice, so you can build a system that is complete but not bloated.

ISO/IEC 27001:2022 uses the term documented information. This covers two things: documents you create and maintain, such as policies and procedures, and records you keep as evidence, such as audit results. The standard names certain items you must have. Beyond those, the amount of documentation depends on your size, complexity and the competence of your people.

What are the ISO 27001 documents required for certification?#

The standard asks for these documents. Check the exact wording in your copy of ISO/IEC 27001:2022 before you finalise your list.

DocumentPurpose
Scope of the ISMSStates what the system covers and what it does not
Information security policySets direction and commitment from top management
Risk assessment and treatment processDescribes how you identify, analyse and treat risks
Statement of ApplicabilityLists the Annex A controls, whether each applies and why
Risk treatment planRecords how each risk will be treated and who owns it
Information security objectivesSets measurable goals and how you will check them

Notice that the list is short. The standard does not ask for a thick manual. It asks you to document the decisions and rules that matter, so that people know what to do and an auditor can see how you decided. Where your own situation needs more documents, for example because several teams share duties, add them. Where it does not, leave them out.

Which records must you keep as evidence?#

Records show that the system works. The standard asks you to keep evidence of items such as competence, monitoring and measurement results, the internal audit programme and its results, management review outputs, and the nature of nonconformities and the actions taken. Risk assessment and risk treatment results are also records.

  • Evidence of staff competence, such as training records.
  • Results of monitoring and measurement.
  • Internal audit programme and audit reports.
  • Management review minutes and decisions.
  • Nonconformities and corrective actions.
  • Risk assessment results and risk treatment results.

Auditors look for these records first, because they prove the system has been running. A well-written policy with no records behind it is a weak sign.

What other policies and procedures do auditors expect?#

The 2022 edition has an Annex A of 93 controls in four themes: organisational, people, physical and technological. You choose which apply and justify the choice in your Statement of Applicability. For each control you apply, you will usually need a policy, a procedure or a record that shows how you meet it. Common examples include:

  • Access control policy and user access reviews.
  • Acceptable use of assets and information classification.
  • Supplier security and third-party agreements.
  • Incident management procedure and incident log.
  • Backup, logging and monitoring practices.
  • Business continuity and disaster recovery arrangements.
  • Secure development and change management, if you build software.
  • HR security, including onboarding, exit and awareness training.

You do not need a separate long document for each. A small company can combine several topics into one short policy, as long as the content is clear and followed.

It helps to build a simple document register. List each document, its owner, version, approval date and next review date. The register becomes the map an auditor follows, and it lets you spot missing or outdated items before the audit does. Review it at each management review, so it stays accurate.

Keep in mind that the auditor will test whether documents are used. Expect questions to staff such as where to find the incident procedure or who approves access. If people cannot answer, the document may exist only on paper. Brief your team and run a short awareness session before the audit.

How do you write documents that pass an audit?#

  1. Start from your scope and risk assessment, not from a template list.
  2. Write short, plain documents that name owners and steps.
  3. Make sure each document describes what you really do.
  4. Control versions, approvals and review dates.
  5. Link each applied control in the Statement of Applicability to its document or record.
  6. Train people on the documents that affect their work.

Templates can save a great deal of drafting time. Our ISO 27001 toolkit offers editable template documents and a gap assessment checklist, with one year of e-mail support and a free upgrade within 6 months. Templates are a starting point only. You must adapt each one to your own scope, risks and practice, or the auditor will see that the document and the reality do not match.

A common mistake is copying a policy from another company. It may promise controls you do not have, which creates a finding. Another is leaving old versions in circulation. Keep one current version in a controlled place and archive the rest.

If you want expert help to design the document set, see our ISO 27001 consulting in India. The right amount of documentation depends on your organisation, and no one can promise an audit result.

Finally, plan for change. Your scope, suppliers and tools will change over the three-year certification cycle, and the documents must keep pace. Assign an owner for each document, review it at least once a year, and record changes. This habit keeps you ready for surveillance audits.

Frequently asked questions#

How many documents do we need?#

There is no fixed number. You need the items the standard names, plus whatever is necessary for your controls to be understood and followed. Keep it as small as works.

Can we use one policy for several topics?#

Yes, if the content is clear and covers what the standard and your risks require. Small companies often combine topics to keep the system simple.

Do records have to be on paper?#

No. Electronic records are fine if they are controlled, backed up and available when the auditor asks for them.

For a wider view, read our complete guide to ISO 27001 or contact AdWiser with your questions.

Found this useful?

Share it with your network, and follow AdWiser Enterprise Consulting on LinkedIn for more certification guides and compliance tips.

Share:

Leave a Comment

Comments are reviewed before they appear. Please keep them relevant and leave out web links.

Ready to put this into practice?

Start with the ISO 27001:2022 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp