Compliance guide
What is information security?
Information security (in Swedish informationssäkerhet) means protecting information from being leaked, changed or lost, and making sure the right people can use it when they need it. Its three goals are confidentiality, integrity and availability. This guide explains the term, how it differs from data protection under GDPR, where Swedish guidance lives now, and how a company can start.
On this page
This is a plain-language guide, not legal advice. Where this page and a law or an authority's text differ, the original decides. Swedish quotes are translated by SimpleSecurity; the Swedish original is given where it matters.
1. In short
- Information security is protecting information and the systems that hold it from misuse, loss and damage. It is built on three goals: confidentiality, integrity and availability (the CIA triad).
- It covers all information the organisation depends on, in any form: files, databases, paper, conversations. It is not only an IT job.
- Data protection (GDPR) is narrower in subject and wider in purpose: it covers personal data only, but also covers lawfulness and people's rights. GDPR makes security a legal duty for personal data (Articles 5(1)(f) and 32).
- In Swedish the word is informationssäkerhet. Swedish guidance has moved to NCSC (ncsc.se), part of FRA, since 1 July 2026.
- A company starts with a short list of what matters, a risk look, a written policy and a few basic measures. A formal management system and certification can come later.
2. What information security means
The US standards body NIST keeps a public glossary of security terms at csrc.nist.gov. Its entry for "information security" quotes the US federal law definition:
| Term | NIST glossary wording |
|---|---|
| Information security | "protecting information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide integrity, confidentiality, and availability" (from 44 U.S.C. section 3542) |
| Confidentiality | "Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information." |
| Integrity | "Guarding against improper information modification or destruction, and includes ensuring information nonrepudiation and authenticity." |
| Availability | "Ensuring timely and reliable access to and use of information." |
In plain words:
- Confidentiality: only the right people can see it.
- Integrity: it is correct and nobody changed it without permission.
- Availability: it is there when it is needed.
Sweden's national cybersecurity centre describes the same idea in Swedish. NCSC writes that informationssäkerhet "handlar om att förhindra att information läcker ut, förvanskas och förstörs", and that the right information should be available "för rätt personer, i rätt tid". In English: it is about stopping information from leaking, being altered and being destroyed, and about the right information being available to the right people at the right time. That maps onto confidentiality, integrity and availability.
The EU's NIS2 directive uses the same three ideas in a slightly wider list. It defines the security of network and information systems as the ability to resist events that "compromise the availability, authenticity, integrity or confidentiality" of data or services (Directive (EU) 2022/2555, Article 6(2)). Authenticity (it really comes from who it says it comes from) is added to the three.
Note on ISO. The ISO/IEC 27000 family of standards is the usual reference for the vocabulary. Its text is sold by ISO and is not quoted here. NCSC's pages say the Swedish method support is based on that series (see section 5).
3. What it covers
Information security is wider than IT security. NCSC says the work covers three kinds of protection: administrative rules such as policies and guidelines, technical protection such as firewalls and encryption, and physical protection such as perimeter protection (walls, doors, locks) and fire protection (NCSC, "Om informationssäkerhet").
| Kind of protection | Example |
|---|---|
| Administrative | A policy, who may see what, a leaver checklist |
| Technical | Backups, updates, encryption, sign-in checks |
| Physical | Locked rooms, shredding paper, fire protection |
NCSC also says the protection should fit the need: "tillräckligt bra och inte för svagt eller för krångligt och dyrt" (good enough, and not too weak or too complicated and expensive). Risk decides how much.
For how information security differs from cybersecurity and IT security, see IT security vs cybersecurity.
4. Information security and data protection
They overlap but are not the same thing. Information security protects any information. Data protection is the legal area that protects people's personal data, and in the EU it is set by the GDPR (Regulation (EU) 2016/679).
| Information security | Data protection (GDPR) | |
|---|---|---|
| Protects | All information that matters to the organisation | Personal data: "any information relating to an identified or identifiable natural person" (Article 4(1)) |
| Main question | Is it kept confidential, correct and available? | Is it handled lawfully, and are people's rights respected? |
| Where security fits | It is the whole subject | One principle: personal data must be processed securely (Article 5(1)(f)) |
| Source of the duty | Your own risks, customers, contracts, sector rules | The law itself |
GDPR names the same goals. Article 5(1)(f) requires personal data to be "processed in a manner that ensures appropriate security of the personal data, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage". Article 32(1)(b) lists "the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services" among the measures. So good information security is how most of the security part of GDPR is met. It is not all of GDPR: the rights of the people the data is about are in Chapter III, which security measures do not cover.
Read more in What is GDPR? and GDPR compliance.
5. In Sweden: informationssäkerhet and where the guidance lives
Informationssäkerhet is the Swedish word for information security. It is the term used on the pages of NCSC and MCF quoted below.
Who publishes the guidance now. For years the public method support came from MSB, later the Swedish Civil Defence and Resilience Agency (MCF). MCF's page for the subject (the old msb.se address now leads there) says that the support and material that used to be there has moved to ncsc.se. It states that the government has decided that all cyber operations at MCF are to move to the National Cybersecurity Centre (NCSC) at FRA from 1 July 2026. That page was last reviewed on 22 June 2026. NCSC's page "Om informationssäkerhet" adds that the pages used to belong to the agency and that NCSC is updating and restructuring the content as part of its new website.
So the answer for a reader today is: look at ncsc.se first. If you find an older link to msb.se, expect a notice that points you on.
What NCSC offers, from its own pages:
- Method support for systematic information security work (Metodstöd för informationssäkerhetsarbete): guidance, tools, templates and tips, based on the ISO/IEC 27000 series. It has four steps: identify and analyse, design, use, follow up and improve.
- Information security management system (LIS): NCSC describes it as an organisation's processes for steering and managing its information security work, with management support and a policy.
- Terminology bank (Termbank för informationssäkerhet): a free, searchable national database of terms and definitions, produced within national (SIS/TK 318) and international (ISO/SC 27) standardisation.
- Support for small and medium-sized organisations: checklists and short guides for businesses, including safe remote work.
- The cybersecurity law (NIS2) pages: for organisations the law covers. See Cybersäkerhetslagen and Does NIS2 apply to my company?
6. How a company starts
This is a practical order of work. It follows the four steps in NCSC's method support, scaled down for a small company. It is not a legal checklist.
- Find out what matters. List the information and systems the business cannot work without: customer data, accounts, the website, email, source code. Name an owner for each.
- Look at the risks. For each item ask what could go wrong (lost, leaked, changed, unavailable) and how bad it would be. Rank the list.
- Write the rules down. A short policy that management approves, and a few rules people can follow. See IT security policy: what to include.
- Put in the basic measures. Backups you have tested, updates, strong sign-in, limited access, a plan for incidents. NCSC's 10 rekommenderade säkerhetsåtgärder (10 recommended security measures) page is a Swedish list to start from.
- Check and improve. Review on a schedule and after every incident. NCSC says it is not enough to put measures in place and then relax: their effect has to be reviewed regularly.
- When the work needs structure, turn it into a management system. See What is an ISMS? If customers ask for a certificate, see ISO 27001 certification.
A certificate is a choice, not a starting condition. Many organisations work systematically for a long time before, or without, certifying.
7. How SimpleSecurity helps
SimpleSecurity keeps records and watches the outside of your systems. It does not make anyone compliant or certified, and SimpleSecurity holds no certification.
| Step | SimpleSecurity service |
|---|---|
| List what matters | Asset database that ties the other services together |
| Look at risks | Risk Register, with vulnerabilities converted into tracked, owned risks |
| Write rules down | Policy Register with review dates |
| Availability and exposure | Uptime Monitor, SSL/TLS Monitor, Email Security, Vulnerability Scanner, Backups heartbeat |
| People | People & Awareness: timestamped training and policy read-receipts per person |
| When things go wrong | Incident Register |
See every service or see the plans.
Related guides
8. Sources
- NIST Computer Security Resource Center glossary: information security, confidentiality, integrity, availability
- Regulation (EU) 2016/679 (GDPR), Articles 4(1), 5(1)(f), 32(1)(b) and Chapter III
- Directive (EU) 2022/2555 (NIS2), Article 6(2)
- NCSC: Om informationssäkerhet
- NCSC: Metodstöd för informationssäkerhetsarbete, Ledningssystem för informationssäkerhet (LIS), Termbank, Small and medium-sized organisations
- MCF (formerly MSB): Informationssäkerhet och cybersäkerhet (notice of the move to ncsc.se, last reviewed 22 June 2026)