Home  /  Insights  /  ISO 27001 required documents and records: the complete list
Insights

ISO 27001 required documents and records: the complete list

ISO 27001 asks for less paperwork than most people think, but it is exact about what it does ask for. Here is every item the clauses require, the documents your Annex A controls usually add, and what an auditor looks for in each.

Cyber Veda

Quick answer: ISO/IEC 27001:2022 requires documented information in Clauses 4 to 10: the ISMS scope, information security policy, risk assessment and treatment processes, Statement of Applicability, risk treatment plan, security objectives and evidence of competence, operation, monitoring, internal audit, management review and corrective action. Further policies and procedures depend on which Annex A controls you select in your Statement of Applicability.

Two kinds of required documentation

Searches for a list of ISO 27001 mandatory documents return lists of wildly different lengths, from a dozen items to more than sixty. The difference comes from mixing two sources of documentation that the standard treats quite differently:

  • Documentation the clauses require. Clauses 4 to 10 set out the management system, and in specific places they say a piece of documented information must exist. These items are mandatory for every certified organisation, with no exceptions.
  • Documentation your controls lead to. Annex A lists 93 controls. You select the ones that apply through your risk assessment and record that in your Statement of Applicability. Many selected controls are easiest to evidence with a policy, register or procedure, and a few say outright that something should be documented. None of these is mandatory until you select the control.

A third category sits between them: clause 7.5.1 b) requires whatever other documented information you decide is needed for the ISMS to be effective. That gives you room to document what helps and leave out what doesn’t, as long as you can defend the choice.

Documents vs records

ISO uses one term, “documented information”, for everything. You may see a rule that “maintain” means a document and “retain” means a record, but that was the 2013 wording. ISO/IEC 27001:2022 mostly says documented information “shall be available”, and uses “retain” in only a few places, such as the risk assessment and risk treatment processes in 6.1.2 and 6.1.3. The practical way to read the requirements is by what each item does:

  • Documents say how things should be done and are kept current: the scope, the policy, the risk assessment method. They change as the business changes, under version control.
  • Records are evidence of something that happened: audit results, management review minutes, training completions. Records shouldn’t change once created. If one is wrong, you correct it visibly rather than overwrite it.

The Type column in the table below follows this practical split; it isn’t a label the standard assigns. The distinction matters at audit. A policy proves you intended to do something; a record proves you did. Organisations that buy a full set of policies but keep no records are easy to spot at Stage 1.

What the clauses require

This is the complete set of documented information named in Clauses 4 to 10 of ISO/IEC 27001:2022. For what each clause asks of the management system more broadly, see ISO 27001 clauses 4 to 10 explained.

ClauseDocumented informationTypeWhat it typically looks like
4.3Scope of the ISMSDocumentA scope statement naming the services, locations, people and systems covered, with interfaces and any exclusions explained
5.2Information security policyDocumentA short, top-management-approved policy with a commitment to meet requirements and improve, and a framework for setting objectives
6.1.2Information security risk assessment processDocumentYour risk method: how risks are identified, analysed and evaluated, and the risk acceptance criteria
6.1.3Information security risk treatment processDocumentHow treatment options are chosen, controls determined and residual risk accepted by risk owners
6.1.3 d)Statement of ApplicabilityDocumentEvery Annex A control with inclusion or exclusion, justification and implementation status
6.1.3 e)Risk treatment planDocumentActions, owners and target dates, approved by risk owners along with the residual risk
6.2Information security objectivesDocumentObjectives, measurable where practicable, with who is responsible, the resources needed, deadlines and how results will be evaluated
7.2Evidence of competenceRecordRole requirements plus training, qualifications or experience records for people doing ISMS work
7.5.1 b)Other documented information you determine is necessaryEitherThe policies, procedures and records you decide the ISMS needs, including most Annex A documentation
8.1Operational planning and controlRecordEnough evidence to show processes ran as planned, such as tickets, logs and checklists
8.2Results of risk assessmentsRecordThe risk register at each assessment, including those triggered by significant change
8.3Results of risk treatmentRecordEvidence that treatment actions were completed and what risk remains
9.1Monitoring and measurement resultsRecordMetrics and reports on control performance and progress against objectives
9.2.2Internal audit programme and resultsRecordThe audit programme, audit plans, reports and findings
9.3.3Management review resultsRecordMinutes showing the required inputs were covered and the decisions taken
10.2Nonconformities and corrective actionsRecordA log of each nonconformity, the action taken and whether it worked

A few things are notably absent. ISO/IEC 27001:2022 doesn’t require a written procedure for document control, internal audit or corrective action. The 2005 edition did, which is why older templates still include them. You still need to run those processes and keep their records; you just don’t need a separate document describing each one. The 2024 amendment, which added climate change to the context in clauses 4.1 and 4.2, didn’t add a new mandatory document either, but auditors may ask how you considered it.

The risk items in this table are the heart of the system. Our risk assessment guide covers the method, register and treatment plan step by step.

Documents your Annex A controls usually add

Once the Statement of Applicability is settled, most organisations need a set of topic-specific policies, registers and procedures to support the controls they selected. Treat the list below as typical, not mandatory. Each item only becomes necessary if you select the control behind it, and several can be combined into one document.

DocumentMain controlsNotes
Topic-specific security policies5.1Approved, published and reviewed. The topics should follow your risks, not a template’s table of contents
Roles and responsibilities5.2, 5.3Who owns the ISMS, risks and controls, and how conflicting duties are separated
Inventory of information and assets5.9Assets in scope with owners. Often drawn from device management and SaaS admin tools
Acceptable use rules5.10The control wording asks for these to be documented
Access control policy5.15 to 5.18, 8.2 to 8.5How access is requested, approved, reviewed and removed, including privileged access
Supplier security5.19 to 5.23How suppliers and cloud services are assessed, contracted and monitored
Incident management5.24 to 5.28, 6.8How events are reported, assessed, escalated, learned from and evidenced
Business continuity and ICT readiness5.29, 5.30Security during disruption and plans that are tested, not just written
Legal and regulatory requirements register5.31 to 5.34Laws, regulations and contracts that apply, kept up to date; covers privacy obligations too
Documented operating procedures5.37For the activities that need them, such as backups, onboarding or deployments
Confidentiality agreements6.6Identified, documented, reviewed and signed by the people they apply to
Secure development and change8.25 to 8.32Only if you build or change software and systems in scope

Notice that most of these produce records as well: access reviews, supplier assessments, incident logs, backup tests. At Stage 2 the auditor spends more time on those records than on the policies themselves. For the full control set and how to decide which apply, see Annex A controls explained.

What auditors look for

Certification auditors don’t mark documents for style or length. They check four things, first at Stage 1 and then in depth at Stage 2 (see what to expect at each stage):

Control of documented information

Clause 7.5 expects each document to be identifiable (title, owner, version, date), reviewed and approved by the right person, available where it’s needed, and protected from unauthorised change. Old versions should be withdrawn or clearly marked. A shared drive where three copies of the access policy sit side by side is an easy finding.

Consistency

The scope, risk register, Statement of Applicability and policies should tell the same story. If the SoA says a control is implemented, the auditor will ask for the policy and the evidence. If a policy says access is reviewed quarterly, they will ask for the reviews carried out so far.

Use

Auditors interview people outside the security team. If staff can’t say where the policies live or what they say about the things they do every day, the documents exist on paper only. The same applies to procedures: what the document says and what people describe should match.

Records over time

A management system has to show it has run, not just that it was set up. Before certification, auditors expect the ISMS to have completed one full cycle of its own activities: risk assessment and treatment, internal audit, management review and corrective action, each with dated records. That doesn’t mean a year of history, but the records must be real.

Right-sizing for a small business

The clause list in the table above is the same for a ten-person startup and a multinational. Everything else scales. A small business can often:

  • combine topic-specific policies into a handful of documents organised around how the team actually works
  • keep the scope, policy, objectives and roles together in one short ISMS manual, if that’s easier to maintain
  • let tools generate records automatically: identity provider logs for access reviews, device management for the asset inventory, ticketing for change and incidents
  • rely on cloud providers’ certifications for the controls they operate, documenting how you checked them under supplier security
  • write procedures only where a task is risky, infrequent or done by different people

The test for each document is simple: would the business miss it if it disappeared, and could someone new follow it? If neither, it probably doesn’t need to exist. Our guide to ISO 27001 for small businesses covers scope and roles for small teams in more detail.

Common mistakes

  • Buying a 60-policy pack. Generic packs commit you to processes you don’t run, using roles you don’t have. Every promise in a policy is something an auditor can test, so each unnecessary page is a potential nonconformity. You also end up maintaining documents nobody reads.
  • Documents nobody follows. A policy that says one thing while the team does another is worse than no policy. Write down what you do, or change what you do, but close the gap before the auditor finds it.
  • Missing records. The policies are polished, but there are no minutes from management review, no internal audit report, no evidence the risk treatment plan was worked through. Records are where most first-time findings come from.
  • Treating the SoA as a checklist. Writing a policy for every included control, whether or not it adds anything. One well-written document can support many controls.
  • No version control. Unapproved drafts circulating, no review dates, no record of what changed. This is basic, and auditors notice.
  • Letting it go stale. Documents written for certification and never reviewed again. Surveillance audits each year will check that reviews happened.

Deciding which documents a particular business actually needs, and writing them to match how it works, is the part of an implementation we take on for clients. The step-by-step implementation guide shows where documentation fits in the overall sequence.

Next step

If you are building your own ISMS, the internal audit is the best test of whether your documents and records will hold up. ISO 27001 requires internal auditors to be objective and impartial, so nobody audits their own work. The auditor can be a trained staff member auditing areas they don’t run, or someone external. In a small team where everyone built part of the ISMS, that often means bringing in an outside auditor. Our independent internal audit is run by a Lead Auditor against the whole standard. If you would rather have the system built with you, see our ISO 27001 service or book a free 30-minute consultation.

FAQ

Common questions

How many mandatory documents does ISO 27001 require?

There is no fixed number. Clauses 4 to 10 call for roughly 16 to 20 items of documented information, depending on how you group them. On top of that come the documents that follow from the Annex A controls you select in your Statement of Applicability, which differ for every organisation.

Which policies are mandatory for ISO 27001?

The clauses require only one: the information security policy (clause 5.2). Topic-specific policies, such as access control or supplier security, come from Annex A control 5.1 and the other controls you select. Most organisations end up with somewhere between a handful and a dozen, sized to their risks.

Does ISO 27001 require written procedures?

Far fewer than people expect. No clause in ISO/IEC 27001:2022 requires a written procedure for document control, internal audit or corrective action, although you must still run those processes and keep the records. Annex A control 5.37 calls for documented operating procedures where you select it, and you add any others you decide are necessary under clause 7.5.1 b).

What is the difference between a document and a record?

A document says how things should be done and is kept up to date, such as a policy or the risk assessment method. A record is evidence of what was done and is kept unchanged, such as internal audit results or a training log. ISO calls both “documented information”.

Can our ISMS documentation live in a wiki or compliance platform?

Yes. The standard doesn’t care about format or tool. It cares that documents are identified, reviewed and approved, available to the people who need them, protected from unauthorised change, and that you can show which version applied at a given time.

How long should we keep ISO 27001 records?

The standard leaves retention to you. Set periods that meet your legal and contractual obligations, and keep ISMS records long enough for auditors to see a history across the three-year certification cycle.

Talk to someone who has taken companies like yours to audit.

Book a free 30-minute consultation. Tell us what is driving the need, and leave with a realistic timeline and the first three things to do.