Home / NIS2 and DORA

NIS2 and DORA: evidence from the browsers your people use.

Both rules ask you to know your ICT suppliers, manage the risks they bring and report serious incidents quickly. Much of that happens in the browser: the SaaS your people sign in to, the supplier portals they upload files to, the attacks they meet. ByteMantle turns it into records you can hand to an auditor.

PlainlyByteMantle helps you meet parts of NIS2 and DORA; it does not make you compliant on its own. Compliance also depends on your own processes, contracts and decisions. The texts: NIS2 (Directive (EU) 2022/2555) and DORA (Regulation (EU) 2022/2554).

Your ICT third parties, from real use

NIS2 asks for security in the supply chain (Article 21(2)(d)); DORA asks financial entities to keep a register of their ICT third-party providers. The hardest part is knowing who they really are. The browsers already know:

  • A register kept up to date by use: every supplier and SaaS site your people use, how many of them used it and how (sign-in, payments, file uploads), declared suppliers or every site the browsers saw.
  • Critical suppliers ranked by real use, not by a spreadsheet filled in once a year.
  • Export when the auditor asks: CSV or JSON, as input for your NIS2 documentation and your DORA register of information.

Supplier exposure, without scanning anyone

The sites your suppliers run tell the browsers which software they use. The console matches those versions with public advisories (NVD, OSV, CISA's catalogue of exploited vulnerabilities, EPSS, end-of-support dates), gives each group of sites an exposure score and its trend, and lets you hand a supplier a clean PDF of what to check. It says "possible vulnerabilities", never "vulnerable": the supplier is the one who can confirm. How it works: supplier exposure without scanning.

Incident evidence, ready for the report

NIS2 sets short deadlines for reporting significant incidents, starting with an early warning within 24 hours. When an attack reaches a browser, the console already has the story:

  • One incident per attack, in order: where the user came from, the site and its age, which script loaded which, the lure, the exact command or sign-in page, and how it ended.
  • Exports for your report and your partners: PDF, JSON, a ZIP with checksums, and STIX 2.1 bundles with TLP marking for MISP and OpenCTI.
  • Which other people met the same attack, and on which sites, so you can tell how far it went.

Controls you can show

Where the data lives

In the European Union when we host the console, or on your own server if you run it yourself. Detection runs in the browser and only short records of detections are sent; what is collected, and what is not, is on Trust & Privacy and in the Data Processing Agreement.

Which plan

The ICT third-party register and supplier exposure are part of the Enterprise plan; incidents, exports and SIEM forwarding start with Pro. ByteMantle Enterprise · Compare plans

Stop these attacks before anything runs.

Free browser protection for everyone, in Chrome and Edge. One console for your whole company when you need it.

Get the extension — free