Compliance guide
What is an information security management system (ISMS)?
An information security management system (ISMS, in Swedish ledningssystem för informationssäkerhet, LIS) is the set of processes an organisation uses to steer and manage its information security work. ISO/IEC 27001 is the international standard that sets the requirements for one. In Sweden, the public method support that used to come from MSB is moving to NCSC, part of FRA. This guide explains the parts, the standard and the Swedish guidance.
On this page
This is a plain-language summary, not legal advice. The text of ISO/IEC 27001 is sold, so this page states only what ISO, SIS, Swedac and NCSC say publicly. Agency names and web addresses in Sweden changed in 2026; section 5 says what was found on 20 November 2026.
1. In short
- An ISMS is an organisation's processes for steering and managing information security (NCSC: "Ett LIS är en organisations processer för styrning och ledning av informationssäkerhetsarbetet").
- ISO/IEC 27001 "defines requirements an ISMS must meet" (iso.org). You can build an ISMS on the standard without being certified.
- The usual parts are management support and a policy, a scope, a risk assessment, chosen security measures with a Statement of Applicability, internal audit and management review.
- The Swedish method support (metodstöd) for an ISMS is now NCSC's. NCSC is part of FRA. NCSC has an overview page on ncsc.se, and the full site was still on an msb.se address on 20 November 2026, with a move to ncsc.se planned for the end of 2026.
- Certification is a separate step. See ISO 27001 certification.
- NIS2 does not require an ISMS by that name. It requires risk-based security measures. An ISMS is one way to organise them.
2. What an ISMS is
"Management system" means the rules, roles and routines an organisation uses to run an area of work and keep improving it. Quality and environment have their own. An ISMS is the one for information security.
Sweden's NCSC puts it this way: an ISMS is a support for how information security work is steered. The processes "ska utvärderas löpande och anpassas till aktuella verksamhets- och omvärldskrav" (are to be evaluated continuously and adapted to current business and external requirements). A central part is management's stated support. Management should also make sure the organisation adopts a policy for the work. Further guidelines can then give direction to managers and staff.
ISO describes the aim as keeping information confidential, intact and available by applying a risk management process. It adds that an ISMS "is a tool for risk management, cyber-resilience and operational excellence". NCSC says the same idea: the security level starts from a risk analysis adapted to the business, and the work follows a clear process.
An ISMS covers information in any form. ISO says the standard helps secure information "in all forms, including paper-based, cloud-based and digital data". It is not a product you install.
3. The parts of an ISMS
The binding wording of ISO/IEC 27001 is paid text. The parts below are the ones described in public sources. The right-hand column says where each is described.
| Part | In plain words | Public source |
|---|---|---|
| Management support | Top management states its support and stays involved. | NCSC (LIS page); SIS: "Högsta ledningen ska vara involverad". |
| Policy and guidelines | A policy for the work, then guidelines. NCSC lists topics guidelines often cover: internet and email use, protection against malicious code, physical security, incident handling, continuity planning, mobile work, inventory and licences, access rights and logging. | NCSC (LIS page). |
| Scope | Which parts of the organisation the ISMS covers. | ISO scope text ("within the context of the organization"); the SC 27 Journal 2026 names "scope definition" among the work of a management system. |
| Risk assessment and treatment | Find the risks, decide which to accept, and decide measures for the rest. | ISO and SIS scope texts; NCSC method step "Identifiera och analysera". |
| Security measures | The controls chosen to treat the risks. Annex A of ISO/IEC 27001 lists 93, and the organisation compares its own list with them. | SIS; SC 27 Journal 2025. See Annex A. |
| Statement of Applicability | A document that records which Annex A controls apply, how they are implemented and why. | SC 27 Journal 2026 ("documented through the Statement of Applicability"). |
| Internal audit | Checking inside the organisation that the system works. | SC 27 Journal 2026. |
| Management review | Management looks at risks, resources and results, and decides what to change. | SC 27 Journal 2026. |
| Continual improvement | The cycle repeats and the system adapts to change. | ISO scope ("continually improving"); NCSC step "Följa upp och förbättra". |
The Journal is a publication of ISO/IEC JTC 1/SC 27, the committee behind the standard. It is not the standard itself. Treat the rows that cite it as a description of common practice. The wording of the requirements is in the standard.
The SC 27 Journal 2026 also says an ISMS is not "a one-time project that ends at certification" and not "a checklist where Annex A automatically defines compliance". It says ISO/IEC 27001 requires the organisation to justify which controls apply and how they are implemented.
4. ISO/IEC 27001 and the ISMS
ISO/IEC 27001:2022 is Edition 3, published October 2022. Its scope (as shown by SIS) is requirements "for establishing, implementing, maintaining and continually improving an information security management system", including requirements for the assessment and treatment of information security risks. It applies to all organisations "regardless of type, size or nature".
SIS describes the series this way: ISO/IEC 27001 holds the basic requirements, and ISO/IEC 27002 describes how the 93 security measures can be put in place. SIS says both are the basis for an ISMS (LIS). A third, ISO/IEC 27003, is a guidance standard. The standards are sold by SIS and ISO. More in ISO 27001 certification: what it is and how it works.
5. Swedish guidance: MSB, MCF, FRA and NCSC
Older pages and guides name MSB. This is what was found on 20 November 2026.
| What was checked | What it showed |
|---|---|
| MSB's old address msb.se/informationssakerhet | Redirects (through mcf.se) to NCSC's section "Arbeta systematiskt med informationssäkerhet och cybersäkerhet" on ncsc.se, the website of the Nationellt cybersäkerhetscenter (NCSC). That section links to "Metodstöd för informationssäkerhetsarbete". The older deep address for the method support on msb.se ends on a "Sidan finns inte" page. |
| Who NCSC is | NCSC's page says it is "en del av FRA" (part of FRA, Försvarets radioanstalt). |
| What changed in 2026 | NCSC says that from 1 July 2026 the information and cybersecurity operations of the Myndigheten för civilt försvar (MCF) were "integrerats i verksamheten vid FRA" (integrated into FRA). |
| The old address informationssakerhet.se/metodstodet | Redirects to metodstod-informationssakerhet.msb.se and returns "Vi hittar inte sidan" (page not found). The method support itself is on metodstod-informationssakerhet.msb.se, where it is called NCSC's "Metodstöd för systematiskt informationssäkerhetsarbete". A notice there says the site is planned to move to ncsc.se at the end of 2026 and that its content is current. |
So the owner of the ISMS method support is NCSC at FRA, even though the full site is still on an msb.se address. Pages and guides written before 1 July 2026 may still name MSB or MCF. The same change is described in our guide Cybersäkerhetslagen: what Sweden's NIS2 law requires.
The method support site says it is addressed, in NCSC's words, to "dig som arbetar med informationssäkerhet i en organisation, oavsett verksamhetsområde och storlek på organisation" (you who work with information security in an organisation, whatever its sector and size). NCSC also lists a related tool, Cybersäkerhetskollen, on the same pages.
6. The four steps in the Swedish method support
NCSC says its method support aims to clarify how systematic information security work can be built on the standards for ISMS (LIS). It "baseras på standardserien ISO/IEC 27000" (is based on the ISO/IEC 27000 series). It has four steps, which can be worked through in turn or used as needed:
- Identifiera och analysera (identify and analyse). NCSC's page names four introductory films: business analysis, analysis of the outside world, risk analysis and gap analysis. The results give an understanding of internal and external conditions, overall risks and the current level of information security.
- Utforma (design). Shape the work so it fits the organisation and addresses the risks it does not accept.
- Använda (use). The third step. The overview page does not describe it further.
- Följa upp och förbättra (follow up and improve). The work is followed up and improved over time. NCSC says organisations often work in several steps at once and pass all steps "om och om igen" (again and again).
NCSC adds that the work must fit the organisation's own steering, such as responsibilities, risk management and budget routines, so it is part of ordinary operations. It says it is not enough to introduce some security measures and then settle back, because the measures' effect must be reviewed regularly.
7. ISMS or certificate?
An ISMS and an ISO 27001 certificate are different things. The ISMS is the system you run. The certificate is an outside body's confirmation that it meets the standard. ISO says organisations "can decide whether they want to go through a certification process". Some "implement the standard in order to benefit from the best practice it contains", while others also want a certificate "to reassure customers and clients". Swedac says a certificate shows customers, partners and authorities that the organisation works in a structured way with information security.
How a certification body audits, and how to check that it is accredited, is in ISO 27001 certification. The first policy document most ISMS work needs is covered in IT security policy.
8. An ISMS and NIS2
Neither NIS2 nor Cybersäkerhetslagen (2025:1506) requires an ISMS or an ISO 27001 certificate by name. The authority's binding rule says an operator must "identifiera och hantera behovet av att använda relevanta standarder i cybersäkerhetsarbetet" (identify and deal with the need to use relevant standards in its cybersecurity work) (MCFFS 2026:11, 3 kap. 2 §). The general advice, which is not binding, says SS-ISO/IEC 27001:2022 and SS-EN ISO/IEC 27002:2022, or equivalent, should be used as support.
The same regulation's 3 kap. 1 § is binding and reads like the Swedish method steps. The operator must run “systematiskt och riskbaserat cybersäkerhetsarbete” (systematic, risk-based cybersecurity work). That includes identifying and analysing external requirements, internal needs and risks, designing and introducing security measures, following up and evaluating risks and measures, and improving measures when needed. The work “ska integreras med befintligt sätt att leda och styra organisationen” (is to be integrated with the way the organisation is already led and steered). For the full list of duties, see the NIS2 compliance checklist, and for what to show instead of a certificate, Is there a NIS2 certification?
9. How SimpleSecurity helps
SimpleSecurity does not make an organisation compliant or certified. It keeps records that an ISMS produces.
| ISMS part | Service |
|---|---|
| Statement of Applicability | Statement of Applicability: all 93 Annex A controls, with reasons, justification, evidence notes and a CSV export for the auditor. |
| Risk assessment | Risk Register: tracked, owned risks, with vulnerabilities converted to risks. |
| Policies | Policy Register: policy lifecycle tracking with review SLAs. |
| Control mapping | Compliance: controls mapped across 22 frameworks, including ISO 27001. |
| Awareness and training | People & Awareness: per-person, timestamped training and policy read-receipts. |
| Assets in scope | Asset Database (CMDB): one list of assets that other services link to. |
| Incidents | Incident Register: incidents with NIS2 and GDPR clocks. |
See every service or see the plans.
Related guides
10. Sources
- NCSC, Ledningssystem för informationssäkerhet (LIS)
- NCSC, Metodstöd för informationssäkerhetsarbete and the method support site metodstod-informationssakerhet.msb.se
- NCSC, Om centret: part of FRA; 1 July 2026
- ISO/IEC 27001:2022, iso.org
- SIS, ISO 27001 and SS-EN ISO/IEC 27001:2023
- Swedac, ledningssystem för informationssäkerhet
- SC 27 Journal 2026 and 2025
- MCFFS 2026:11, 3 kap. 1–2 §§, in force 1 October 2026 (text in the FRA rule book)