“Which documents are mandatory for ISO 27001?” is usually asked in the hope of getting a list. In fact, the standard doesn’t require specific document names; it requires certain information to be documented, and in addition the documents the organization considers necessary for the effectiveness of the ISMS to be created. That’s where the problem we see in the field comes from: a 40-document set downloaded from the internet describes work the organization doesn’t actually do, and each one becomes a separate nonconformity in the audit. Below you’ll find the topics on which the standard explicitly expects documented information, which documents cover them in practice and how a document becomes defensible in an audit.
The difference between policies, procedures, instructions and records
Mixing up these four types produces unnecessarily long policies and procedures with no records. The distinction is:
| Type | What does it describe? | Example |
|---|---|---|
| Policy | Management’s principles and commitment | Information Security Policy, Access Control Policy |
| Procedure | Who does what, in which order | User Account Management Procedure |
| Instruction | The steps of a single task | Instruction for preparing a new laptop |
| Record | Evidence that the activity was carried out | Approved access request, restore test record |
Auditors read the policy and ask about the procedure, but usually make their decision by looking at the record. Policies should be short; a two-page access control policy is more defensible than a twelve-page text nobody reads. Technical details (password length, lockout threshold, MFA scope) belong in a procedure or standard document. That way, when a setting changes, the policy doesn’t need to go back to management for approval.
The main topics on which the standard explicitly expects documented information
- ISMS scope
- Information security policy
- Risk assessment process and risk treatment process
- Statement of Applicability (SoA)
- Information security objectives
- Evidence of competence
- Operational information needed to have confidence that processes are carried out as planned
- Results of risk assessment and risk treatment
- Monitoring and measurement results
- Internal audit program and results
- Results of management review
- Nonconformities, actions taken and results of corrective actions
Annex A controls also require documents in most cases: for example, documented operating procedures, acceptable use rules or incident management planning. Which ones are needed depends on the control selection in the SoA.
Notice that half the list is “results”. Risk assessment results, monitoring results, internal audit results. These aren’t written; they’re records produced by a system in operation. When “document writing” is finished in the project timeline, half the work is done. The other half is records.
Note: The list is a summary of the standard’s structure; clause texts are copyrighted and aren’t reproduced verbatim. For exact requirements, refer to the standard itself.
A typical document set in practice
In a medium-sized organization, the management system and controls are usually covered by 20–30 documents: policy, risk methodology, risk treatment plan, SoA, asset management, classification, access control, user account management, passwords and MFA, privileged access, backup, business continuity and disaster recovery, incident response, logging and monitoring, change and patch management, secure configuration, supplier security, remote access, acceptable use, awareness plan, internal audit program, management review documents, corrective action forms and an audit evidence matrix. Several topics can be combined in one document; what matters is consistency and traceability.
On the IT side, the documents that cause the most problems are the backup, patching and logging procedures. The reason is simple: the person who writes them and the person who runs the system are different people. The procedure says “daily backup, monthly restore test”; the backup software has a weekly job configured and the last restore test was a year ago. Write these documents together with the system administrator, with the console open.
Five elements that make a document defensible in an audit
- Owner: The person responsible for keeping the document up to date.
- Approval and effective date: Who approved it, and when did it take effect?
- Review frequency: At least annually or when changes occur.
- Reality: Do the roles, systems and frequencies described actually exist in the organization?
- Link to records: Which form or system record does each rule produce?
A practical way to test the fifth element is an evidence matrix: every “shall” sentence in every procedure is written on a row, with the record it produces and where that record is kept. A row left without a match is either deleted or starts producing records. There’s no middle ground.
Is using a template wrong?
A template can be a good starting point for format and heading structure. The problem is putting a template into effect without adapting it to the organization: if the “Information Security Committee” it mentions doesn’t exist in the organization, or “monthly log review” isn’t done, the document produces a nonconformity in the audit. For adaptation, a short meeting with each document owner and writing down how things really work is recommended.
Traces left over from templates are easy to find: another company’s name, a product the organization doesn’t use (“all servers are protected by X antivirus”), a job title that doesn’t exist. Auditors catch these on first reading, and confidence in the rest of the documents drops. Before publishing, check the organization name, system names and roles in every document one by one.
Document control: versions, access, retention
The standard expects control over the distribution, access, retention and changes of documented information. For organizations using Microsoft 365, a SharePoint document library meets these requirements in practice with versioning, an approval flow and access permissions. For details, see the SharePoint evidence management guide.
A control failure you may run into is the same document sitting in three different places in three different versions: one in a shared folder, one as an email attachment, one on the intranet. Set a single publication point and remove the other copies or mark them as “uncontrolled copy”. A retention period must also be defined for records; records with a legal retention period (e.g. legislative requirements for logs) are assessed separately.
Document control also has a reverse side: the withdrawn version. A procedure that’s been withdrawn should be archived but shouldn’t stay in the publication area users can access. Otherwise, two versions are read side by side and which one is valid is up for debate again.
Having your documents prepared externally
If there’s no internal resource, all the documents can be prepared externally; however, each document must be handed over to an internal owner. The Information Security Policy and Procedure Package prepares the policies and procedures selected for the project scope in a single project (the sample list has 25 headings); the ISO 27001 documentation service keeps the scope flexible.
Frequently asked questions
Can documents be kept in software instead of Word?
Yes. The standard doesn’t specify a format; a document management system, SharePoint, a wiki or a GRC tool can be used. What matters is meeting the requirements for version control, approval, access and retention.
Are English documents accepted?
The audit language and the language employees can understand should be taken into account. Group company policies can be in English; for practicality, user-facing instructions are best kept in Turkish.
Is it a problem in the audit if there are only a few documents?
No. Having too many unnecessary documents is a bigger risk. Combining topics is accepted as long as the requirements are met, and the documents are consistent and applied.