Required
The ordinary scope route is not established by the entered size figures
The ordinary scope route is not established by the entered size figures.
Cybersäkerhetslag (2025:1506) 1 kap. 2 § 13 and 4 § 3; Recommendation 2003/361/EC Arts. 2–6Swedish cyber incident check
Initial Notice And Incident Notification Within 24 Hours — Annual Balance Sheet Total Eur: €60 · The entered figures do not meet the ordinary route's…
The calculated result is “Preliminary Threshold Not Met On Entered Figures · Initial Notice And Incident Notification Within 24 Hours”. The ordinary scope route is not established by the entered size figures.
Decision path24036F6A7ASchema 2026.01.15
Staff headcount used in the size assessment0
Annual turnover used in the size assessment (€)€50
Annual balance-sheet total used in the size assessment (€)€60
The entity's applicability under the Swedish Cybersecurity Act is confirmedYes
DORA or equivalent sector rules displace these incident-reporting dutiesNo
Significant incident? (severe operational disruption, financial loss, or harm to others)Yes
Incident-notification deadline categoryTrust Service Provider
Size-independent or special scope basisNone
Initial incident notice submittedNo
Fuller incident notification submittedYes
Incident notification submitted within its 24- or 72-hour deadlineNo
One month has passed since the incident notificationNo
Action required
Calculated result Preliminary Threshold Not Met On Entered Figures · Initial Notice And Incident Notification Within 24 Hours
Apply the published Swedish Cybersecurity Act interpretation to scope, size, covered activity, sector-specific displacement, significance, entity category, deadlines, and reporting status. This scenario is distinct because it produces this exact combination of calculated result, active obligations, deadlines, and required evidence.
Published by ProseIDVersion 2026.01.15
Required
Make the confirmed scope basis and incident-notification deadline category…
Make the confirmed scope basis and incident-notification deadline category consistent.
Cybersäkerhetslag (2025:1506) 1 kap. 5 § 4 and 2 kap. 6 §Required
Submit the initial incident notice to the CSIRT unit within 24 hours of awareness
Submit the initial incident notice to the CSIRT unit within 24 hours of awareness.
Cybersäkerhetslag (2025:1506) 2 kap. 5 §Required
Complete “Incident-notification submission date, time, and zone”
Complete “Incident-notification submission date, time, and zone”.
Cybersäkerhetslag (2025:1506) 2 kap. 6 §; NIS2 Art. 23(4)(b)Review
The fuller incident notification may be late
The fuller incident notification may be late.
Cybersäkerhetslag (2025:1506) 2 kap. 6 §Required
Submit a status report at the one-month point for the ongoing incident
Submit a status report at the one-month point for the ongoing incident.
Cybersäkerhetslag (2025:1506) 2 kap. 8 §Required
Complete “One-month status update”
Complete “One-month status update”.
Cybersäkerhetslag (2025:1506) 2 kap. 8 §Change the facts
A nearby path produces a different result.
Staff headcount used in the size assessment0 → 72
Annual turnover used in the size assessment (€)€50 → €2
Size-independent or special scope basisNone → Covered Public Entity
Result becomesPreliminary Medium Or Larger Threshold Met · Initial Notice And Incident Notification Within 24 Hours
Inspect the changed path →Published legal basis
Sources carried by this schema release.
The calculated path is bound to the cited version and sources. It is general information, not a substitute for advice on facts or law outside the schema.
Use your facts
Run the actual workflow.
This page shows one calculated path. Open the maintained workflow to answer with your own facts and, when needed, create a version-bound audit record.