<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr" -->

---
title: DORA, NIS2, and the End of ‘We’re Not in Scope’ | daily.dev
description: DORA and NIS2 regulatory obligations reach far beyond directly named EU entities, pulling in any vendor that sells to or supplies EU-regulated banks,...
canonical: https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: DORA, NIS2, and the End of ‘We’re Not in Scope’ | daily.dev
og:description: DORA and NIS2 regulatory obligations reach far beyond directly named EU entities, pulling in any vendor that sells to or supplies EU-regulated banks,...
og:url: https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr
og:image: https://api.daily.dev/og/posts/5rh4p6xBR.png
og:image:alt: DORA, NIS2, and the End of ‘We’re Not in Scope’
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# DORA, NIS2, and the End of ‘We’re Not in Scope’

**[Security Boulevard](https://daily.dev/sources/securityboulevard)** · 6 min read · 0 upvotes · 0 comments

## Summary

DORA and NIS2 regulatory obligations reach far beyond directly named EU entities, pulling in any vendor that sells to or supplies EU-regulated banks, hospitals, or energy providers through contractual flow-down. Passeca CEO Sergiy Lapin describes common gaps organizations face: overloaded compliance leads juggling multiple frameworks, incident response runbooks not built for regulatory notification deadlines (24-hour early warning, 72-hour formal notice, 1-month root-cause analysis under NIS2), and boards that can no longer delegate cybersecurity accountability to a CISO. Practical steps recommended include building an asset inventory (what, where, who), seeding a Register of Information from existing contracts rather than starting from scratch (claimed to reach 80% coverage in 2 weeks versus 2 quarters), and shifting board reporting from compliance percentages to resilience scenarios. The piece closes by promoting Hyperproof's platform, used by Passeca, for automating third-party risk management and multi-framework compliance.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://securityboulevard.com/2026/09/dora-nis2-and-the-end-of-were-not-in-scope>

## Questions this post answers

### What are the NIS2 incident reporting deadlines after a cybersecurity incident?

NIS2 requires an early warning notification within 24 hours of an incident, a formal notification within 72 hours, and a final root-cause analysis report within 1 month. Many organizations discover their existing incident response runbooks were built for internal escalation only, not for meeting these regulatory-facing deadlines, exposing gaps once the compliance clock starts.

_Teams rebuilding incident runbooks for regulatory deadlines can track compliance guidance like this on daily.dev._

### Does DORA or NIS2 apply to vendors that are not headquartered in the EU?

Yes, vendors outside the EU can still fall under DORA and NIS2 obligations through contractual flow-down if they sell services within the EU or supply EU-regulated entities such as banks, hospitals, or energy providers. These clauses increasingly appear in supplier contracts even in countries where regulatory transposition is not yet finalized, making customer exposure the deciding factor rather than headquarters location.

_Vendors assessing their regulatory exposure can follow evolving compliance obligations on daily.dev._

### How can an organization quickly build a DORA Register of Information for third-party vendors?

Start from the existing contract repository rather than a blank spreadsheet, pulling all active contracts involving data processing or system access to create a seed list, then layering in criticality by identifying which vendors would disrupt customer service if they failed for four hours. Organizations using this contract-first approach reportedly reach 80% coverage in two weeks compared to two quarters with empty templates.

_GRC teams building vendor risk registers can track practical compliance approaches on daily.dev._

## Similar posts on daily.dev

- [DORA is live, and every pillar assumes you can see your infrastructure](https://daily.dev/posts/dora-is-live-and-every-pillar-assumes-you-can-see-your-infrastructure-cflgdq3fn) · NetBox Labs · 0 upvotes · 0 comments
- [Who owns NIS2 and DORA on a Kubernetes platform team](https://daily.dev/posts/who-owns-nis2-and-dora-on-a-kubernetes-platform-team-gfga533ws) · CNCF · 4 upvotes · 0 comments
- [When DORA Goes From Afterthought to Commercial Imperative](https://daily.dev/posts/when-dora-goes-from-afterthought-to-commercial-imperative-ukjrnq0ec) · IT Security Guru · 0 upvotes · 0 comments
- [How EU Regulations Are Reshaping SOC Operations](https://daily.dev/posts/how-eu-regulations-are-reshaping-soc-operations-fgovegosz) · Security Boulevard · 0 upvotes · 0 comments
- [NIS2: what actually changes for companies and tech teams](https://daily.dev/posts/nis2-what-actually-changes-for-companies-and-tech-teams-lnloscayr) · Codemotion · 1 upvotes · 0 comments

---

Tags: [#compliance](https://daily.dev/tags/compliance), [#dora](https://daily.dev/tags/dora)

[View this post on daily.dev](https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"DORA, NIS2, and the End of ‘We’re Not in Scope’","url":"https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr"},"datePublished":"2026-09-25T15:54:12.136Z","dateModified":"2026-09-25T15:54:38.281Z","description":"DORA and NIS2 regulatory obligations reach far beyond directly named EU entities, pulling in any vendor that sells to or supplies EU-regulated banks,...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8fe9eeb967de205fd6743e2535f16178?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/8fe9eeb967de205fd6743e2535f16178?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Security Boulevard","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Security Boulevard","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/3613c832180040de8d85bb29f74395be","url":"https://daily.dev/sources/securityboulevard"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"compliance,dora","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Security Boulevard","item":"https://daily.dev/sources/securityboulevard"},{"@type":"ListItem","position":3,"name":"DORA, NIS2, and the End of ‘We’re Not in Scope’"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/dora-nis2-and-the-end-of-we-re-not-in-scope--5rh4p6xbr#faq","mainEntity":[{"@type":"Question","name":"What are the NIS2 incident reporting deadlines after a cybersecurity incident?","acceptedAnswer":{"@type":"Answer","text":"NIS2 requires an early warning notification within 24 hours of an incident, a formal notification within 72 hours, and a final root-cause analysis report within 1 month. Many organizations discover their existing incident response runbooks were built for internal escalation only, not for meeting these regulatory-facing deadlines, exposing gaps once the compliance clock starts. Teams rebuilding incident runbooks for regulatory deadlines can track compliance guidance like this on daily.dev."}},{"@type":"Question","name":"Does DORA or NIS2 apply to vendors that are not headquartered in the EU?","acceptedAnswer":{"@type":"Answer","text":"Yes, vendors outside the EU can still fall under DORA and NIS2 obligations through contractual flow-down if they sell services within the EU or supply EU-regulated entities such as banks, hospitals, or energy providers. These clauses increasingly appear in supplier contracts even in countries where regulatory transposition is not yet finalized, making customer exposure the deciding factor rather than headquarters location. Vendors assessing their regulatory exposure can follow evolving compliance obligations on daily.dev."}},{"@type":"Question","name":"How can an organization quickly build a DORA Register of Information for third-party vendors?","acceptedAnswer":{"@type":"Answer","text":"Start from the existing contract repository rather than a blank spreadsheet, pulling all active contracts involving data processing or system access to create a seed list, then layering in criticality by identifying which vendors would disrupt customer service if they failed for four hours. Organizations using this contract-first approach reportedly reach 80% coverage in two weeks compared to two quarters with empty templates. GRC teams building vendor risk registers can track practical compliance approaches on daily.dev."}}]}
```

