What does a coffee machine have in common with a company? Both take something in, turn it into something else, and only work if their parts play together. That’s a system. And what turns a company into a managed one is a management system.
A management system is the framework of policies, processes, roles and resources an organization uses to set objectives and achieve them. An information security management system, or ISMS, applies that framework to one topic: protecting the confidentiality, integrity and availability of information. ISO 27001 defines the requirements such a system must meet.
From a system to a management system
A system is a set of elements that work together as a whole. Every system has a purpose, elements, an organization that makes them interact, boundaries, an environment that influences it, and inputs it turns into outputs.

Take a professional coffee machine. Beans, water and power go in, a cup of coffee comes out. Inside, the grinder, the boiler, the pump and the controller work together, and the controller makes sure they do it in the right order. The housing is the boundary. The café and the staff are its environment. And its purpose: great coffee, cup after cup.
An organization is a system too. Instead of a grinder and a boiler, it has people, structures and rules, and it exists to achieve objectives. A management system is how it pursues them.
The idea behind a management system
Most organizations already manage security somehow: a capable administrator here, a policy written after an incident there. A management system replaces this dependence on individuals with structure.

It starts with direction. Top management sets a policy, and from it, objectives: results the organization wants to achieve, ideally measurable. Then the elements of the management system do the work. What comes out are results, and those are measured against the objectives. If you missed them, or something has changed, you review and improve, and adjust the objectives if needed. Then it starts again.
The six building blocks

Typically, you’ll find six building blocks. The organizational structure: who’s at the top and who reports to whom. Roles and responsibilities: who does what, and who’s accountable. The culture: the way things are really done around here, often unwritten. Policies: the direction set by top management. Objectives: what exactly you want to achieve. And processes: the activities that turn inputs into outputs. You’ll meet every one of them again in ISO 27001, from the policy in clause 5.2 to the roles in 5.3 and the objectives in 6.2.
Plan, Do, Check, Act
Most management system standards describe the improvement loop as the PDCA cycle.

Think of it as a wheel rolling up a slope: every turn takes you a little higher. That’s continual improvement. And what stops the wheel from rolling back? The management system itself: the processes, rules and records you’ve put in place. In ISO 27001, the clauses map onto the cycle like this:
Phase | Clauses | In the ISMS |
|---|---|---|
Plan | 4, 5, 6, 7 | Understand context, commit leadership, assess risks, plan treatment, provide resources |
Do | 8 | Operate the processes and implement the risk treatment |
Check | 9 | Monitor, measure, audit internally, review with management |
Act | 10 | Correct nonconformities and improve the system |
The cycle has no finish line. An ISMS that completed one loop and stopped is, by the standard’s own logic, no longer a management system.
The harmonized structure
Do you have to figure all of this out yourself? No. That’s what management system standards are for: ISO 9001 for quality, ISO 14001 for the environment, ISO 45001 for health and safety, ISO 22301 for business continuity, and ISO 27001 for information security.
All modern ISO management system standards share one skeleton, known as the harmonized structure. You’ll also hear the older names Annex SL or High-Level Structure. Clauses 4 to 10 carry the same headings in every standard: context, leadership, planning, support, operation, performance evaluation, improvement. Only the subject changes. The practical benefit is integration: an organization can run one management system that satisfies ISO 27001 and ISO 9001 together, with shared document control, shared internal audits and one management review.
A management system is not a set of documents
The most persistent misunderstanding in this field is equating the ISMS with its documentation. Documents matter, and ISO 27001 names the ones it requires, but they are evidence of the system, not the system itself. The system is the running cycle: risks being assessed, decisions being taken by named owners, measurements being reviewed, corrections being made. A complete document set describing a cycle that never runs describes nothing.
The same goes for software. A tool can support an ISMS, but it isn’t the ISMS.
At Barvello: no second management system
Barvello Coffee Systems is the fictional company of our ISO 27001 Lead Implementer course: a family-owned maker of professional coffee machines in Munich, with about 500 employees and its own cloud platform, Barvello Connect. Its quality management system has been certified to ISO 9001 since 2004, and you’ll find all six building blocks in it.

A Quality and Regulatory Affairs department reports to the CEO. Anna Schulz, the Head of Quality, runs the system. The culture is pragmatic and informal, and outside of Quality, little is written down. There’s a quality policy, and objectives like on-time delivery, which was 94 percent in 2025. The internal audits and the management review with the board every January are the “check”, and the corrective actions that follow are the “act”.
So when the ISMS project started, Anna made one thing very clear: she doesn’t want a second management system. And thanks to the harmonized structure, she doesn’t need one. Barvello can use one management review, one internal audit program and one document control for quality and for information security.
From the auditor’s chair
Certification audits are built around exactly this distinction. At stage 1 I read the documentation. At stage 2 I look for the operating system behind it: objectives that were actually measured, a management review that actually took decisions, corrective actions that were actually verified. A polished document set with no operating evidence does not pass stage 2. A modest document set describing a cycle that demonstrably runs usually does.
Frequently asked questions
Is an ISMS a software tool?
No. Software can support an ISMS, for example for risk registers or document control, but the management system is the set of processes, roles and decisions. Buying a tool does not create one.
Can ISO 27001 be integrated with ISO 9001?
Yes. The harmonized structure is designed for it. Shared elements such as document control, internal audit and management review can serve both standards in one integrated system.
How much documentation does ISO 27001 require?
Less than most projects produce. The standard names specific documented information, such as the scope, the policy and the risk assessment results. Everything beyond that is your choice and should earn its maintenance effort.
Chapter 2 in the course.
From a coffee machine to an ISMS.
8 lectures (51 min) explain management systems, ISO 27001 and the 27000 family, how to read the requirements, and the laws and frameworks around it, with Barvello as the example throughout. Then the course takes you through the 12 steps of the implementation.
Management Systems
09:28
ISO 27001: The Standard for an ISMS
07:06
The ISO 27000 Family
07:20
How to Read ISO 27001
08:13
Next up: the 12 steps to implement ISO 27001, starting with the implementation roadmap.


