Ask people what information security is, and most will say something like firewalls, antivirus and strong passwords. That’s part of it. But it’s a bit like saying that securing your home is just about having a good lock.
Information security is the preservation of the confidentiality, integrity and availability of information. These three properties are known as the CIA triad, and every requirement in ISO 27001 ultimately exists to protect one or more of them. This article covers the fundamentals that every ISMS is built on: information as an asset, the CIA triad, and the risks and controls that connect them.
Information is an asset
Information has value. Decisions, strategies and new products all depend on it, and anything that has value to an organization is an asset that needs protection.

It comes in three forms, and how you protect it depends on the form. Digital information, on laptops, servers, phones and in the cloud, is fast to access and easy to share, which is exactly why it needs access rights, encryption and backups. Material information, on paper, can’t be hacked, but it can be lost, taken or left lying on a desk, so locked cabinets and a clear desk matter. And unrepresented information only exists in people’s heads: knowledge, experience, know-how. When someone who has built your products for thirty years retires, that knowledge walks out the door unless it’s documented and handed over.
One detail is easy to overlook: it doesn’t matter whether the information belongs to you or was entrusted to you, for example by a customer. If it leaks, your customers will hold you responsible. So don’t stop at your own information. Include everything others have entrusted to you. ISO 27001 therefore speaks of information and other associated assets: the systems, devices, facilities and people that store, process or transmit it.
What information security is
Back to your home. You lock the door, and maybe you have an alarm. That’s technology. But a good lock doesn’t help much if you hand out keys to everyone, so you decide who gets one and get it back when someone moves out. That’s a process. And the best lock is useless if someone hides the key under the doormat. That’s people.

Protecting information takes the same three: technology, like encryption and multi-factor authentication; processes, like deciding who gets access and until when; and people, who don’t type their password into a phishing page. So information security isn’t something you can hand over to the IT department. It concerns the whole organization.
One more distinction, especially if English isn’t your first language: security isn’t safety. In German, there’s one word for both. Safety protects people from harm, like a burn from a coffee machine’s steam wand. Security protects against threats, like someone pushing manipulated firmware onto that machine. ISO 27001 is about security.
The CIA triad
The three properties give every security discussion a common language. A useful habit is to ask, for any incident or control, which of the three it concerns.
CIA | Property and meaning |
|---|---|
C | Confidentiality |
I | Integrity |
A | Availability |
Integrity isn’t only lost through attacks. A failed data import, a bug or a simple typo can make information just as inaccurate. And availability can be lost without anything being disclosed or changed: the information still exists, it just isn’t there when you need it.
Not every piece of information needs all three to the same degree, and the three can pull against each other. Encrypting everything strengthens confidentiality but can threaten availability if key management fails. Balancing them for each asset is a risk decision, not a technical default. ISO 27001 builds directly on this: the risk assessment identifies the risks of losing confidentiality, integrity and availability for the information in your scope.
Watch the full lecture above. It’s “The CIA Triad” from the course, with Alice, Bob and three real incidents at Barvello.
Authenticity and non-repudiation
Two more properties come up often. Authenticity means that something, or someone, is what it claims to be: an email really comes from your supplier, a firmware update really comes from the manufacturer. Non-repudiation means you can prove that something happened and who did it, so nobody can credibly deny it later. Digital signatures give you both, as long as the private key really stays private.
Information security, cybersecurity and data protection
The three terms overlap, but they aren’t interchangeable.

Information security covers information in every form: digital, on paper and in people’s heads. Cybersecurity is the digital part of it. So a printed contract in a locked cabinet isn’t a cybersecurity topic, but it’s still an information security topic. Data protection protects people when their personal data is processed, in Europe under the GDPR, and it reaches beyond security: whether you may process the data at all, for what purpose and for how long.
An ISMS supports all three. But ISO 27001 certification isn’t by itself proof of GDPR compliance. Lawfulness, consent and the rights of data subjects aren’t part of it. For privacy, there’s ISO 27701, a separate standard you can integrate with your ISMS.
Risks and controls
Ask an organization about its incidents, and you’ll usually get a list: the outage last spring, the phishing email that worked. Ask about its risks, the things that haven’t happened yet, and it often gets quiet. But an ISMS is built on risks, not just on incidents.
ISO defines risk as the effect of uncertainty on objectives. Whenever you work toward an objective, something can happen that you didn’t plan for. In information security, you look at the risks that come from a loss of confidentiality, integrity or availability. And a risk is basically a chain: a threat exploits a vulnerability, affects an asset, and has a consequence for the organization.

Threats come from two kinds of sources. Adversarial ones want to cause harm, like an attacker or an employee taking data to a competitor. Non-adversarial ones don’t mean any harm: heavy rain, a technical failure or a simple mistake. Both can be equally damaging. Vulnerabilities typically sit in six areas: hardware, software, networks, the organization, sites and people.
A risk isn’t an incident. An incident has happened, and you deal with it through incident management. A risk is a potential event that might never happen, and you manage it before it does. The two are connected: an incident is basically a risk that materialized, and every incident tells you something about your risks.

So what do you do about risks? You implement controls: measures that maintain or modify risk. A control can be technical, but also a process, a policy or a practice.

Preventive controls stop an incident from happening, like moving the servers out of the basement. Detective controls act when it occurs, like a water sensor that raises the alarm. Corrective controls act after it, like offline backups with a restore you’ve actually tested. In practice, you combine all three.
And that’s the logic behind every ISMS. You identify and assess your risks, and you treat them with controls. In ISO 27001, that’s the risk assessment and the risk treatment in clause 6, and Annex A gives you a list of 93 controls to compare your selection against. The Annex A section of this guide covers all four themes.
At Barvello: real incidents behind every term
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. About 21,700 machines send their data to Connect, so Barvello holds its customers’ recipes, prices and consumption figures. Most of that information belongs to the customers. But if it leaks, it’s Barvello’s problem.

And Barvello has an example for every term in this article. Confidentiality: in June 2026, a security researcher found that customers could see other customers’ reports in the Connect portal, simply by changing a number in the URL. Integrity: the cup counters in Connect are the basis for every pay-per-cup invoice, so a wrong counter means a wrong invoice. Availability: in September 2025, an expired certificate cut off all machines from Connect for 19 hours, and Barvello paid a €38,000 service credit. There was no attacker. Just a certificate that nobody kept an eye on.
Authenticity: in January 2026, attackers took over a sales assistant’s mailbox, which had no multi-factor authentication, and sent distributors new bank details. One of them paid €46,800. And a risk that hasn’t happened yet: in July 2021, heavy rain flooded parts of the basement in Munich and stopped three metres short of the server room. That was a warning, and the risk is still there.
How ISO 27001 builds on these fundamentals
ISO 27001 takes these concepts and makes them operational. Assets and their value inform the asset inventory, threats and vulnerabilities feed the risk assessment, and the CIA triad defines what “secure” means for each asset. The next article explains the vehicle that holds this together: the management system.
From the auditor’s chair
Incidents are easy to talk about. Most organizations can tell you about the outage last spring. Risks are harder: what could happen next, and why. That’s usually where you see whether an ISMS is driven by risks or only reacts to incidents.
Frequently asked questions
Is cybersecurity the same as information security?
No. Cybersecurity concerns digital systems and networks. Information security is broader and includes paper records, physical access and human factors. ISO 27001 addresses the broader discipline.
What is the CIA triad?
The three properties of information that information security preserves: confidentiality, integrity and availability. Every security control serves at least one of them.
What’s the difference between a risk and an incident?
An incident has happened. A risk might happen. You handle incidents through incident management, and you manage risks before they occur, with a risk assessment and controls. Every incident tells you something about your risks.
Why do paper documents matter in ISO 27001?
Because the standard protects information in every form. A contract in an unlocked cabinet is as much an information security concern as an unpatched server.
Chapter 1 in the course.
Every term, a real incident.
8 lectures (35 min) cover information as an asset, the CIA triad, authenticity and non-repudiation, cybersecurity and data protection, and risks and controls, each with real incidents from Barvello. Then the course builds the ISMS step by step.
The CIA Triad
05:43
Authenticity and Non-Repudiation
04:55
Cybersecurity and Data Protection
03:56
Risks and Controls
06:46
Next up: what a management system is, and why ISO 27001 is one.


