How we run our ISO 27001 documentation in Elium, and what our 2026 audit said
Our ISMS documentation lives in our own knowledge platform: how we organise it, what our 2026 ISO 27001 surveillance audit said, and what we would change.

We keep all our ISMS documentation in Elium, the knowledge platform we build: every policy, procedure and record of our information security management system, certified to ISO/IEC 27001 since May 2022. Each document has an owner, a review date and an approval, and our April 2026 surveillance audit found no major nonconformity.
That audit, run by our certification body Certi-Trust, was the first of the new three-year cycle. A major nonconformity is a serious gap against the standard; the auditor found none and recommended that we keep the certification.
This post shows how we organise that documentation, the habits that keep it current, what the auditor wrote about it, and what we would set up differently if we started today.

Why we keep an ISMS in a knowledge platform
ISO 27001 asks for a lot of writing. A scope, a security policy, a risk method, a Statement of Applicability (the list of security controls you apply, and why), objectives, procedures, and records that prove the system runs: audits, reviews, incidents, corrective actions. Clause 7.5 of the standard then asks you to control all of it. Each document needs an identity, a review and an approval. It must also be available to the people who need it, protected, under version control, and retained.
Those are the problems a knowledge platform solves every day for other teams. A policy is knowledge with an owner. It must be found, read, trusted and kept up to date. So when our security project started, we did not buy a separate tool for it. We wrote the system where the rest of the company already reads and writes.
Two things followed. Security documents use the same editor, search and notifications as everything else, so people actually open them. And our auditors see the same screens our customers use.
It also suits two kinds of writers. Our engineers write in Markdown, through import or their AI assistant; colleagues in sales, customer success and operations use the editor. Both end up as the same governed article, with the same owner, review date and approval.
How our Security space is organised
Everything sits in one space called Security, open to the whole company for reading. It holds about 250 live articles today:
| What | Examples |
|---|---|
| The management system, clause by clause | Scope, context, roles, risk method, objectives, planning of changes |
| Annex A policies and procedures | Access control, change management, secure development, backup, business continuity |
| Suppliers and services | One description per supplier: what it does, which data it touches, where it is hosted, its certifications |
| Management reviews | Minutes of every Security Committee, on a meeting template |
| Evidence | Internal audits, penetration tests, recovery tests, incident reports, change reports |
| Awareness and law | Security reminders for staff, and the data protection and cybersecurity laws of the countries where we work |
The entry point is one article, "Getting started with our information security management system". It follows the standard from clause 4 to clause 10. Under each clause, a short paragraph explains how we meet it and embeds the article that governs it. Newcomers start there, and auditors use it as the map for the audit.
Six habits that keep it current
1. Every document has an owner and a review date
Each article names one owner. Policies carry a review date, usually 12 months ahead. When the date gets close, the owner gets a task and a reminder. After the date, the article stays readable but its green "verified" badge turns red, so nobody mistakes an expired policy for a current one.

2. Policies are approved before they go live
Policies and the documents for each clause go through an approval step before readers see them. The approver is recorded on the version, so an auditor can see who approved each policy, and when.

3. Changes start as drafts
Editing a live policy creates a draft. Readers keep seeing the approved version until the new one is published. The full history is kept: who changed what, when, and the version before.
4. We check that people read the rules
A policy nobody reads protects nothing. New colleagues are invited to read the internal policies in their first days, and each policy's analytics show who has opened it. For a rule everyone must follow, Elium can go further: the article is sent with a "mark as read" request, and you see who has confirmed and who has not.

5. The management review is written where the system lives
Our Security Committee meets several times a year. The minutes follow one template, built on what the standard expects a management review to cover: actions from last time, changes, performance, audit results, objectives, risks and improvements. Action owners are named in the minutes, and a year of minutes is a year of evidence, in one place.
6. Our AI assistant reads, flags and drafts; owners decide
We connected our AI assistant to the Security space, with the same access rights as the person using it. We use it in three ways.
- To ask. "Which policies mention our backup provider?" It answers from the approved documents, with links, and only shows what the person asking may open.
- To flag. Before a review, it compares a policy with the procedures and records around it. Where something disagrees or looks out of date, it leaves an annotation on that passage. The owner finds it at the next review and decides what to change.
- To draft. When a change is clear, it prepares a draft. It never publishes: the owner checks it and the approver signs, as for any other change.
The annotations also leave a trail: they show an auditor why a document changed, not only that it did.

What our 2026 ISO 27001 surveillance audit said
An auditor samples documents and asks for evidence. Over two days in April 2026, the evidence for scope, roles, the risk method, the committee minutes and the performance indicators all came from the Security space.
On documented information (the standard's term for documents and records), Certi-Trust's report says:
The Elium platform includes several features supporting ISMS management and governance, such as document view tracking, approval workflows, and detailed change logs/history. These capabilities enhance traceability, accountability, and control over documented information within the ISMS.
The same section notes three more points. Every page can carry a review period, with at least a yearly check in place. Drafts are clearly separated from approved versions. And access, version control and approval protect the integrity of each document. Its conclusion on clause 7.5: our way of managing documented information meets the requirement.
What we would set up differently today
The system works and passes its audits. It also grew over ten years, and you can see that in its structure. If we started again, we would change three things.
- More than one space. One space for everything mixes the rules everyone reads with records only a few people need. We would separate the management system, the evidence and the suppliers, each with its own access and its own review rule.
- One review rule, set once. Our review periods drifted between one and two years, article by article. A default per space, set on day one, is simpler to run and easier to explain to an auditor.
- Structure before volume. Sections in clause order, a template for each kind of document, and tags for the Annex A controls from the first article. Adding structure to a few hundred articles later is real work.
We describe that setup step by step, so you can start where we would start now: a ready setup for ISO 27001 document control, with the spaces, sections, tags, templates and workflows. If you are not sure yet what to write in the first place, our guide to ISO 27001 documentation lists every document the standard asks for and how auditors check them.
Where to start
Start with your information security policy. Give it one owner, a review date 12 months ahead and an approver. Then send it to everyone with a request to confirm they have read it. That one article already shows an auditor the whole cycle: written, approved, communicated, kept current.
The help centre shows each step in Elium: review dates, approval and article analytics.
Common questions
You can run ISO 27001 documentation in a knowledge platform, as long as it gives each document an owner, a review date, approval before publication, a version history, access rights and a record of who read it. We have run our own ISMS in Elium since our first certification in May 2022, and our certification body concluded in 2026 that this way of managing documented information meets clause 7.5. The difference from shared folders is upkeep: reminders and expiry badges keep documents current without anyone chasing them.
At a surveillance audit, the auditor samples part of the system and asks for evidence: the scope, roles, the risk method, the latest internal audit and management review, and records showing that controls run as described. For documented information, expect questions on who approved each document, when it was last reviewed, how drafts are kept apart from approved versions, and who can read or change it. In our 2026 surveillance audit, every piece of evidence the auditor asked for came from our Security space.
Set up the structure before moving any documents: separate areas for the rules everyone reads, the records few people need and the supplier descriptions, one default review period per area, sections in clause order, a template for each kind of document, and tags for the Annex A controls. Adding structure to a few hundred documents later is real work. Our ISO 27001 document control setup gives that structure step by step.


