SFS 2025:1506 Is Now Swedish Law
The law entered into force on 15 January 2026. NIS2 is now Swedish statute and board members of every covered entity carry personal liability for compliance.
Your SOC is in Sweden. Your analyst has a name and a direct number. Threats are contained in milliseconds by AI, confirmed by a human in a 3-minute median and not one log leaves the country.
Run a Free Domain Breach ScanIncluding a strategic, multi-year engagement to strengthen cybersecurity resilience across Sweden's critical public sector.
Trusted by 40+ Swedish Kommuner, Regions and
EU-Regulated Enterprises Since 2003








Three regulatory deadlines, one supply-chain catastrophe and a staffing shortage that puts in-house 24/7 coverage out of reach for most organisations.
The law entered into force on 15 January 2026. NIS2 is now Swedish statute and board members of every covered entity carry personal liability for compliance.
The Miljödata supply-chain attack compromised roughly 200 of Sweden's 290 municipalities. A single shared platform became a national-scale incident within hours. This is not a theoretical risk.
The Tietoevry incident showed how a Nordic IT supplier becomes critical infrastructure overnight. Detection latency, not perimeter strength, determined the outcome for every affected organisation.
NIS2 Article 20 places personal liability on directors for inadequate cybersecurity risk management. Sign-off is no longer something the CISO handles alone.
Fines are not theoretical. Supervisory authorities across the EU have begun issuing them. For serious failings the ceiling is €10 million or 2% of global annual turnover, whichever is higher.
MCF (formerly MSB) requires a 24-hour early warning, a 72-hour formal notification and a final report within one month of a confirmed incident. Without 24/7 detection, that clock starts in the wrong place.
Supply-chain security is no longer best-effort. Every third-party vendor relationship has to be assessed, documented and kept current. Under NIS2 they are now part of your audit perimeter.
Sweden's security-skills shortage and Stockholm rates put an in-house 24/7 SOC out of reach for most organisations. MDR converts that capital build into a flat monthly operating line.
The obligations across Cybersäkerhetslagen (NIS2), GDPR and DORA that MDR satisfies directly, mapped to the specific controls auditors check.
Active detection of anomalies, 24 hours a day, 7 days a week, across endpoints, identity, cloud and network. The requirement is not a policy. It is an operational capability that has to produce documented evidence.
MDR satisfies: eBuilder Security SOC delivers auditable, always-on monitoring with named analysts, producing timestamped logs ready for supervisory review.
24-hour early warning, 72-hour formal notification and a complete report within one month. The clock starts at first detection, not when your IT team discovers it on Monday morning.
MDR satisfies: Every confirmed incident is timestamped from T+0. MCF-cascade-ready documentation is generated automatically for each confirmed event.
72-hour window to notify the Swedish data protection authority (IMY) where personal data is involved. Assembling that evidence under deadline pressure is where most organisations fail.
MDR satisfies: eBuilder Security produces IMY-formatted incident documentation automatically for every confirmed personal-data event, delivered to your DPO before the window closes.
For Swedish financial services entities subject to the Digital Operational Resilience Act, ICT incident classification, reporting to Finansinspektionen and operational-resilience documentation are all mandatory.
MDR satisfies: MDR incident records align with DORA classification thresholds and Finansinspektionen's reporting expectations out of the box.
Sweden's Cybersäkerhetslagen brought NIS2 into national law on 15 January 2026. If your organisation operates in energy, transport, health, digital infrastructure or public administration, you are in scope and your board carries personal liability.
Our NIS2 gap checklist maps your current state against every Article 21 control. It is written in plain English, built for the Swedish regulatory context and takes around 20 minutes to complete.
Delivered to your inbox instantly. No spam. EU data residency. Unsubscribe any time.
No spam. EU data residency. Unsubscribe any time.
Most Swedish IT teams already run an EDR. EDR is the tool. MDR is the team and the outcome. Here is what each option actually delivers when Cybersäkerhetslagen audits arrive.
| EDR | MSSP | In-House SOC | MDR - eBuilder Security | |
|---|---|---|---|---|
| What you get | Endpoint detection tool only | Alert forwarding service | Your own analysts & tooling | Tool + 24/7 named team + outcomes |
| Who responds | You | You (after their ticket) | Your team | Named eBuilder Security analyst |
| 24/7 coverage | Tool only, no analyst | Variable by contract | Only if fully staffed | Yes, contractual SLA |
| Time to value | Weeks of tuning | 4–8 weeks | 6–18 months to build | 3 days to go live |
| NIS2 reporting help | Partial (data only) | Partial | Yes, if process is mature | MCF-cascade ready |
| Data stays in Sweden | Tool-dependent | Often offshore | Yes, if self-hosted | Guaranteed by contract |
From what's included to the 3-day deployment and the 3-minute response that makes the difference.
One monthly fee. No incident response surcharges. No hidden add-ons.
Swedish analysts watching your environment continuously. Named people, not a ticket queue.
NIS2 Art. 21.2aHypothesis-driven weekly hunts mapped to MITRE ATT&CK and current Nordic TTPs.
ATT&CK aligned3-minute median response. Containment is included in every plan, covering isolation, credential rotation and firewall pushes.
SLA-backedContinuous watch over accounts, sessions and privileged access. Compromised credentials are rotated and risky logins blocked before they spread.
Entra ID & ADAll telemetry is correlated through CrowdStrike's Next-Gen SIEM into a single incident timeline. Prefer your own? Bring your SIEM, with Sentinel, Splunk, QRadar and 350+ CrowdStrike integrations supported.
Correlated, BYO SIEM supportedMCF-cascade-ready records; IMY-formatted breach notifications produced automatically for every confirmed incident.
Auditor-readyBoard-level reporting on coverage, incidents, posture and compliance status, monthly and on demand.
Monthly + on demand14 to 10,000+ endpoints on one model, one named team and one flat per-endpoint rate. No renegotiation as you grow.
Flat per-endpointCrowdStrike Falcon agents push to your fleet through the device management you already run. Identity and cloud connectors are authenticated. There is no new hardware and no rip-and-replace, with everything documented before any monitoring begins.
The platform learns the rhythm of your environment, SIEM integration completes and false positives are suppressed. Detection rules are tuned to your specific identity, network and cloud footprint so the SOC starts quiet on day three.
The Sweden-based SOC takes 24/7 ownership. Your named analyst is introduced with a direct number. Automated containment is armed, runbooks are agreed and the MCF incident-reporting cascade is wired and tested end to end.
Weekly MITRE ATT&CK-aligned threat hunts and current Nordic TTP tracking catch hands-on-keyboard intrusions that automated rules miss. Findings flow into board-ready reporting and recommendations feed your security roadmap.
Automated containment isolates the affected endpoint and blocks lateral movement in milliseconds. Within three minutes a named analyst validates the incident and executes the pre-agreed runbook: credential rotation, firewall pushes, host isolation and identity revocation.
Every confirmed incident generates the full MCF-cascade record, covering the 24h early warning, the 72h formal notification and the 1-month final report, plus a GDPR Article 33 packet for IMY where personal data is involved. A live debrief closes the loop.
Once an attacker establishes initial access, the clock starts. Industry telemetry puts the median time to lateral movement at 64 minutes. If your detection-to-response window is longer than that, a single-host breach becomes an environment-wide incident. The point of MDR is to compress that window below the attacker's playbook speed.
Illustrative sequence based on a production incident at a Swedish municipality.
Automated containment isolates the affected host; lateral pathways revoked at the endpoint in milliseconds.
Swedish SOC analyst validates the alert and rules out benign automation. Confirmed genuine threat.
Lateral movement attempt blocked; identity tokens for the affected user account revoked.
CTO notified by name and direct number. Incident state: CONTAINED.
NIS2 incident record created and timestamped from first detection. MCF cascade initiated.
Full forensic report and MCF-cascade-ready documentation delivered. GDPR Article 33 packet prepared for IMY.
One incident, one cascade. The 3-minute median is the analyst's first response. The later targets cover the full incident.
Every alert is handled by a frontline analyst, then escalated to a senior analyst when the incident needs deeper work. Your named contact sits across both tiers.
2m 47s
Mean Time to Contain
A Swedish municipality of 1,200 staff was targeted after hours. Automated containment isolated the infected host in under a second; the analyst confirmed and closed the incident within 3 minutes. No data was lost.
72hrs
NIS2 Compliant from Zero
A 400-employee Swedish manufacturer reached NIS2 Article 21 alignment 68 hours after deployment, ahead of the auditor's site visit, with documented MCF-cascade procedures in place.
4yrs
Zero Breaches Under Coverage
Four consecutive years of continuous MDR across a 14-site logistics network. Several attempted intrusions; zero confirmed breaches, zero customer-facing outages.
94%
Reduction in Alert Noise
A regional Swedish energy utility cut analyst workload by 94% in the first 30 days. Automated tuning plus eBuilder Security triage filtered the volume so the in-house team focused on what mattered.
5days
DORA-Ready Posture
A Stockholm-based fintech with 220 staff completed scope mapping, classification thresholds and reporting workflow inside one working week, DORA-aligned before quarter-end.
Through their range of security services and our decision to choose their MDR solution, eBuilder Security has significantly elevated our security posture. During the implementation phase, they were quick to assist and propose solutions to any challenges we encountered. The transition from project to production has been smooth, and their backend team quickly grasped our business needs. eBuilder Security is a valued partner for our future security efforts.
Gerth Ericsson
IT Manager, Vandewiele, Sweden
eBuilder Security helps us meet our IT and information security needs. We are very satisfied by their deep knowledge, comprehensive services, and dedication to strengthening our cybersecurity posture. From End Point Protection and advisory and auditing to penetration testing, eBuilder Security has been a reliable partner in safeguarding our organization.
Christian Sørensen
Internal Operations Director, Médecins Sans Frontières, Norway
The product increases knowledge and security awareness. It helps organizations develop a good information security culture. I am particularly pleased that it is an end-to-end solution where eBuilder Security takes care of the entire process from kick-off to reporting, while allowing for customization to suit the conditions unique to our business.
Per Eriksson
Information Security Strategist, Varbergs Kommun, Sweden
An interactive, browser-based guide that walks Swedish CISOs, finance leads and procurement teams through every decision in an MDR purchase. There is no download and no email-gated PDF. Work through it online and share a link with the buying committee.
~ 2-min walkthrough · No email required
An interactive playbook for CISOs, CFOs and procurement leads
MDR is priced flat per endpoint, per month. No per-GB log charge, no SIEM ingest meter, no incident-response surcharge when something actually happens. The number you sign in month one is the number you pay in month thirty-six.
For context, a comparable in-house Swedish SOC with twelve analysts on shift, plus tooling, infrastructure and training, typically runs north of €2,000,000 per year before you have responded to a single incident. MDR converts that capital build into a known monthly operating line.
Request a Tailored MDR QuoteProposal delivered within 48 hours of a 30-minute briefing.
Pre-empting the procurement back-and-forth. These are the questions that come up in every evaluation call, answered plainly.
eBuilder Security's MDR includes 24/7 SOC monitoring from Sweden, autonomous threat containment, MITRE ATT&CK threat hunting, active incident response (endpoint isolation, credential rotation, lateral-movement blocking), SIEM and SOAR integration, NIS2 and GDPR incident documentation and board-ready reporting. Incident response is part of the service, not a surcharge.
EDR is software that detects threats on endpoints. An MSSP forwards alerts but leaves the response to you. An in-house SOC gives full control but takes 12–18 months to build. MDR is a managed service that detects, investigates and contains threats for you, with a named analyst and contractual 24/7 coverage.
eBuilder Security's MDR covers detection, response and the compliance documentation around incidents. It does not include penetration testing, security awareness training or CISO advisory. Those are separate eBuilder Security services that complement MDR and, together, cover the full scope of NIS2 Article 21.
eBuilder Security differs on four points: a verified 3-minute response with a real Swedish municipal case behind it; a Sweden-operated SOC with a named analyst who knows your environment; automated containment that acts before human escalation; and NIS2 and GDPR documentation included in the base service. eBuilder Security also starts at 14 endpoints.
eBuilder Security's MDR scales from 14 endpoints to more than 10,000, with the same 3-minute response regardless of size. There is no renegotiation as you grow and no minimum commitment for the initial free security review or briefing, which makes enterprise-grade MDR accessible to Swedish mid-market organisations and kommuner.
It means that from the moment a threat is confirmed genuine, not merely detected, a named eBuilder Security analyst has taken active containment action within three minutes. Automated containment isolates endpoints in milliseconds first; the analyst then validates, escalates and runs your organisation-specific runbook. eBuilder Security's median across incidents is under three minutes.
Nothing waits until morning. eBuilder Security's Sweden-based SOC runs 24/7, 365 days a year. Automated containment stops clear-cut threats in milliseconds. A named analyst confirms the incident and executes containment, then notifies your CTO with a full summary, often before anyone on your team is awake.
eBuilder Security's SOC executes pre-agreed runbook actions: isolating affected endpoints, blocking lateral movement across hosts, rotating compromised credentials and pushing firewall rules, all without waiting for your team. Every action is forensically logged and the incident generates timestamped documentation ready for NIS2 early-warning and GDPR notification.
eBuilder Security's MDR is built on CrowdStrike Falcon as the primary platform, with Cybereason available for multi-platform environments, deployed through the device management you already run. CrowdStrike threat intelligence tracks more than 230 named adversary groups globally and eBuilder Security's SOC layers Swedish and Nordic threat trends on top, so detection reflects the threats actually targeting Swedish organisations.
Yes. An existing CrowdStrike or Microsoft Defender deployment speeds onboarding because eBuilder Security connects to your existing telemetry instead of deploying new sensors. Integration with Microsoft Defender for Endpoint, Sentinel and Entra ID is standard and go-live is typically under 24 hours rather than the usual three days.
eBuilder Security's MDR uses an automated detection-and-response layer that contains fast-moving threats in milliseconds, blocking lateral movement and credential stuffing before they escalate. A human analyst then validates and runs the response. Automation handles machine-speed attacks while the named analyst handles judgement, so nothing waits on a queue.
eBuilder Security's MDR directly satisfies the core NIS2 Article 21 obligations: continuous monitoring, incident detection and handling, plus the documentation tied to MCF reporting. It does not by itself cover supply-chain security, business continuity or awareness training. eBuilder Security's advisory and Complorer training services complete the remaining Article 21 scope.
All telemetry, logs and incident records are stored and processed inside Sweden. eBuilder Security operates under Swedish jurisdiction with an ISO 27001-certified SOC, handles data in line with GDPR and Schrems II and transfers nothing to non-adequate third countries. Access is limited to your named analyst team and senior SOC management.
Every confirmed incident is timestamped from first detection, so eBuilder Security can produce the NIS2 reporting chain on time: a 24-hour early warning, a 72-hour formal notification and a one-month final report to MCF and your sector authority. The documentation is generated automatically, formatted for submission.
Yes. For Swedish financial entities in scope of DORA, eBuilder Security's MDR incident records align with the ICT incident-management and classification requirements of DORA Article 17 and Finansinspektionen's expectations. MDR covers the detection and reporting elements, while eBuilder Security advisory maps the wider DORA operational-resilience obligations.
eBuilder Security's MDR reaches full 24/7 coverage in three days: CrowdStrike Falcon agents deploy on day one; SIEM integration and environment baselining on day two; continuous monitoring goes live on day three. If you already run Falcon, go-live is typically under 24 hours because eBuilder Security connects to your existing telemetry.
No. eBuilder Security's MDR requires no new hardware and no rip-and-replace. Agents deploy through the device management you already use and the service integrates with your existing SIEM, firewall, identity and email tools, more than 350 integrations in all, so your current stack is enhanced rather than torn out.
Yes. A kommun can procure eBuilder Security's MDR through an existing framework agreement (ramavtal) where eBuilder Security is listed, through a direct procurement advertised in TED above the EU threshold, or through a direktupphandling under the threshold. eBuilder Security has supported kommun procurements and can advise on the right route for your situation.
Pricing is a flat monthly fee per protected endpoint, scoped to your environment, with no per-gigabyte log charge and no surprise incident-response invoice. eBuilder Security delivers a scoped proposal within 48 hours of a 30-minute briefing. Contracts typically run 12 or 24 months and the initial assessment carries no commitment.
Book a 30-minute walkthrough with a Sweden-based analyst. We'll review your current posture, map gaps to NIS2 and show you live SOC in action. No pitch deck. No commitment.
Book a 30-Minute MDR BriefingMDR is your detection and response backbone. These complementary services close the gaps before, beside and above it.
Safe AI adoption for businesses
Monitor prompts, agents, models and sensitive data in real time to reduce AI-driven risk, prevent data exposure and block threats in real time.
Offensive Security
Find what MDR needs to defend. Expert-led testing across web, cloud, API, network and Active Directory with actionable remediation guidance.
& Phishing Simulation
MDR catches threats while Awareness Training reduces them. Nano lessons and realistic phishing simulations that strengthen your human layer of defence.
Strategic Advisory
MDR gives you visibility while vCISO gives you strategy. Board-level governance, compliance leadership and vendor risk management without a full-time hire.