The two terms are used as synonyms, but they cover different ground. This explainer separates them, places IT security and data protection next to them, and shows what a security management system (ISMS) actually consists of.
In short
Information security protects information in every form, on paper, in people's heads and in systems, so that it stays confidential, correct and available. Cybersecurity is the part that protects networks, systems and digital data against cyber threats. An ISMS is the management system that steers both: policies, roles, risk analysis, controls and regular review.
Ask five people in a company what "security" means and you get five scopes. The IT team thinks of firewalls, the lawyer thinks of GDPR, and the board thinks of the last ransomware headline. This explainer is written by Devies, a Gothenburg-based product and engineering consultancy, for IT leaders, CISOs, compliance owners and managers who need a shared vocabulary before they plan the work. It defines information security (informationssäkerhet) and cybersecurity, compares them with the terms they are confused with, and explains what an information security management system (ledningssystem för informationssäkerhet) is.
What is information security, and how is it different from cybersecurity?
Information security is the protection of all information an organisation depends on, whatever form it takes, while cybersecurity covers the digital part of that job: networks, systems and the data they hold.
Two definitions make the boundary concrete:
- Information security is keeping information confidential (only the right people see it), correct (nobody alters it without authority) and available (it is there when needed). The information can be a contract in a drawer, a price list in an email, a conversation on a train or a customer table in a database.
- Cybersecurity is, in the EU's own words, "the activities necessary to protect network and information systems, the users of such systems, and other persons affected by cyber threats". That definition comes from Regulation (EU) 2019/881, Article 2(1), and the NIS2 Directive reuses it.
So cybersecurity sits inside information security. A phishing attack on your mail server is both. A printed board pack forgotten on a train is a security incident in the wider sense, but nobody would call it a cyber attack. The difference matters in practice, because a programme run only by the IT department tends to miss the paper, the people and the suppliers, which is exactly where many incidents start.
The two still overlap heavily. In most modern companies almost all valuable information lives in digital systems, so the bulk of the effort, and of the budget, ends up in cybersecurity measures.
Information security compared with the terms it is confused with
Information security is the umbrella, and cybersecurity, IT security and data protection are narrower views with their own owners and laws.
Term
What it protects
Typical owner
Main reference
Information security
What it protects
All information, in any form
Typical owner
Management, with a security lead
Main reference
ISO/IEC 27001
Cybersecurity
What it protects
Networks, systems, digital data and their users
Typical owner
CISO, IT and product teams
Main reference
NIS2, Swedish Cybersecurity Act
IT security
What it protects
The technical IT environment: devices, servers, accounts
Typical owner
IT operations
Main reference
Vendor and internal baselines
Data protection
What it protects
Personal data and the rights of the people it describes
Typical owner
Data protection officer, legal
Main reference
GDPR
ISMS
What it protects
Not an asset: the way the organisation manages all of the above
Typical owner
Management
Main reference
ISO/IEC 27001 clauses 4 to 10
ISO 27001 certificate
What it protects
Not an asset: third-party evidence that the ISMS meets the standard
Typical owner
Management, certification body
Main reference
Accredited certification
Two confusions cause the most rework. First, data protection is not simply a subset of security: GDPR also covers lawful basis, purpose and individual rights, which no firewall solves. The two meet in security of processing. Second, an ISMS is not a certificate. You can run a good management system without ever being audited, and a certificate only shows that an auditor checked the system at a point in time.
What is an ISMS?
An ISMS, or information security management system, is the set of policies, roles, processes and records an organisation uses to find its information risks, decide what to do about them and check that the decisions work.
The best-known requirements for an ISMS are in ISO/IEC 27001, published by ISO and IEC. The standard describes a management system, not a technical product, and its logic is a loop: plan, do, check and improve. In everyday terms an ISMS has six parts:
- Scope and context. Which parts of the business, which locations and which systems are included, and which laws and customer demands apply.
- Leadership and policy. Management sets the direction, accepts residual risk and gives the work time and money.
- Risk analysis and treatment. You identify what could go wrong with the information that matters, rate it and choose measures. Our step-by-step guide to security risk analysis shows the method.
- Controls. The chosen measures, technical and organisational: access control, backups, supplier terms, training, incident handling.
- Measurement and review. Internal audits, metrics and a management review that looks at what actually happened.
- Improvement. Findings and incidents lead to changes, and the loop starts again.
What makes it a system is the link between the parts. A control exists because a risk justified it, someone owns it, and the review shows whether it works. A folder of policies with no risk analysis behind it is documentation, not an ISMS. For the clauses, the Annex A controls and how certification audits run, read ISO 27001 explained, which goes deeper into the standard itself.
Do you need an ISMS, and does it have to be ISO 27001?
Most mid-sized companies need some form of ISMS, either because the law asks for risk-based security management or because customers do, but the law does not prescribe ISO 27001.
As of November 2026, Article 21(2) of the NIS2 Directive (EU) 2022/2555 requires essential and important entities to have, among other measures, "policies on risk analysis and information system security", incident handling, business continuity, supply chain security and policies to assess whether the measures work. That is an ISMS in all but name. In Sweden the duties apply through the Cybersecurity Act (cybersäkerhetslagen, SFS 2025:1506), and since 1 July 2026 the National Defence Radio Establishment (FRA) is the single point of contact under NIS2, under the amended Cybersecurity Ordinance (SFS 2026:623). See what NIS2 and the Swedish Cybersecurity Act mean in practice for scope and reporting.
Outside the law, the pressure usually comes from customers. Procurement questionnaires ask for a security policy, a risk process and an incident procedure, and larger buyers ask for a certificate. ISO 27001 is then the common language, but the order of work is the same either way: build the management system first, decide on certification later.
How do you start an ISMS in a mid-sized company?
Start small and real: one scope, one risk analysis, a handful of controls with owners, and a review date in the calendar.
- Name an owner in management and a security lead who has time for the work.
- Set the scope to the part of the business customers and laws care about most, for example the product platform and its support.
- List the information that matters, where it lives and who owns it, including paper and supplier systems.
- Run a first risk analysis with the people who do the work, not only IT.
- Choose and assign controls for the top risks, with a deadline and a way to see that each one works.
- Write short policies that describe what you actually do, then train people on the parts that affect them.
- Review after three to six months, adjust, and widen the scope once the loop runs.
The common failure is to start with documents. Templates are easy to fill in and hard to live by. Starting with the risk analysis keeps the work tied to what could actually hurt the business.
Devies
Want a second opinion?
Devies, a Gothenburg-based product and engineering consultancy, works on questions like this with Nordic product and IT teams. Tell us where you are and we will suggest a sensible first step.
Frequently asked questions
Is cybersecurity the same as information security?
No. Information security covers all information an organisation depends on, in any form: digital files, paper documents and what people know and say. Cybersecurity is the part that protects networks, systems, digital data and their users against cyber threats. In practice they overlap heavily, because most valuable information is digital, but a programme that only covers cybersecurity tends to miss paper, people and supplier routines.
What does ISMS stand for?
ISMS stands for information security management system, in Swedish ledningssystem för informationssäkerhet. It is the way an organisation manages information security: scope, policy, roles, risk analysis, chosen controls, measurement and improvement, repeated in a cycle. ISO/IEC 27001 sets out the requirements for an ISMS, but the term describes the management system itself, not the certificate a company may or may not hold.
Do we need ISO 27001 certification to have an ISMS?
No. An ISMS is a way of working, and a certificate is third-party evidence that the way of working meets ISO/IEC 27001. Many companies run an ISMS based on the standard without being certified, and decide later whether customers or procurement make certification worth the audit effort. As of November 2026, neither NIS2 nor the Swedish Cybersecurity Act requires ISO 27001 certification.
Who should own information security in a company?
Management owns it, because information security decisions are business decisions about which risks to accept and what to spend. Day-to-day work is usually led by a CISO or security lead, while each system or information set has a named owner in the business. IT runs many of the technical controls, but making IT the sole owner usually leaves paper, people and supplier risks without anyone responsible.
Sources
- Regulation (EU) 2019/881 (EU Cybersecurity Act), Article 2(1), definition of cybersecurity
- Directive (EU) 2022/2555 (NIS2), Articles 6 and 21
- Cybersäkerhetslag (2025:1506), Sveriges riksdag
- SFS 2026:623, Förordning om ändring i cybersäkerhetsförordningen (2025:1507), in force 1 July 2026
- ISO/IEC 27001:2022, Information security management systems, ISO










