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 §Swedish cyber incident check
Initial Notice Within 24 Hours And Incident Notification Within 72 Hours — Available indicators of compromise provided through… · Include available indicators of…
The calculated result is “Preliminary Threshold Not Met On Entered Figures · Initial Notice Within 24 Hours And Incident Notification Within 72 Hours”. Make the confirmed scope basis and incident-notification deadline category consistent.
Decision pathE5194FC30ASchema 2026.01.15
Staff headcount used in the size assessment30
Annual turnover used in the size assessment (€)€8
Annual balance-sheet total used in the size assessment (€)€14
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 categoryStandard Operator
Size-independent or special scope basisTrust Service Provider
Initial incident notice submittedYes
Fuller incident notification submittedYes
Indicators of compromise are availableYes
Available indicators of compromise provided through the reporting channelNo
Action required
Calculated result Preliminary Threshold Not Met On Entered Figures · Initial Notice Within 24 Hours And Incident Notification Within 72 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
Complete “Initial-notice submission date, time, and zone”
Complete “Initial-notice submission date, time, and zone”.
Cybersäkerhetslag (2025:1506) 2 kap. 5 §; NIS2 Art. 23(4)(a)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)Required
Provide the available indicators of compromise with the incident notification
Provide the available indicators of compromise with the incident notification.
NIS2 Art. 23(4)(b)Change the facts
A nearby path produces a different result.
Staff headcount used in the size assessment30 → 15
Annual balance-sheet total used in the size assessment (€)€14 → €499
Incident-notification deadline categoryStandard Operator → Trust Service Provider
Result becomesPreliminary Threshold Not Met On Entered Figures · 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.