The night before the audit, someone is still taking screenshots.

Screenshots go stale the moment they are taken, and an auditor knows it. Assembling that evidence by hand usually falls to whoever is least busy that week, not whoever understands the requirement. Module evidence builds the report from what module assets actually monitored and what module remediation actually fixed, so the document reflects a running record instead of a scramble the night before the audit.

compliance reporting

NIS2 evidence built from what we actually watched.

Every report is generated from the surface we monitored and the fixes we confirmed, mapped to the NIS2 measures, so your audit rests on a continuous record, not screenshots gathered the night before.

continuous monitoringconfirmed fixesyour NIS2 report

capabilities

Built from real data

Generated from the surface we monitored and the fixes we confirmed, not screenshots gathered the night before.

Mapped to NIS2

Every finding is tied to the technical measures in the NIS2 implementing regulation, so an auditor can follow it.

Your entity details

The registration details a NIS2 authority asks for, filled in from your account.

White-label ready

Providers can put their own logo and colours on the report and hand it to a client as their own.

PDF and CSV export

A clean PDF for the auditor and a CSV of the findings for your own tracking.

A continuous record

Each report rests on the running history of what we watched, so an auditor sees a timeline, not one afternoon.

What NIS2 requires

How module evidence works

  1. 01

    Built from a running record, not a fire drill

    Module assets keeps watching your exposed assets and module remediation keeps tracking the fixes that landed. Module evidence reads from that record continuously, so the report is never a one-time snapshot someone had to go build. It reflects what happened this month, not a single night.

  2. 02

    Every finding traces to a requirement

    Each finding is mapped to the specific technical measure in the NIS2 implementing regulation it satisfies. An auditor can follow a line from requirement to evidence, instead of taking your word for it.

  3. 03

    Export it, brand it, and hand it over

    The entity registration details a NIS2 authority asks for are filled in from your account. Export a clean PDF for the auditor and a CSV for your own tracking, whenever you need it, not just once a year. A managed provider can put its own logo and colours on the report and hand it to a client as their own work.

Common questions about module evidence

Is module evidence an official NIS2 certification?

No. NIS2 does not define a single certificate an authority stamps and signs, so no vendor can sell you one honestly. What module evidence gives you is the evidence and posture document an authority and an auditor actually expect to see: findings mapped to the technical measures in the implementing regulation, backed by a running monitoring record. That document is what you walk into the audit with. The legal judgment of compliance stays with the authority.

What does module evidence pull its data from?

Module assets runs the continuous monitoring and finds the exposures. Module remediation tracks and confirms the fixes. Module evidence turns that record into the document: it reads what module assets monitored and what module remediation closed, maps each item to the relevant technical measure, and writes the report. Without module assets and module remediation running, module evidence has nothing current to report on.

Can our managed provider put its own branding on the report?

Yes. The report is white-label ready: a managed provider can apply its own logo and colours before handing it to a client as their own work. The underlying evidence and mappings do not change, only the presentation.

See where you’re exposed, and prove you handled it.

Match your first assets free. Browse the whole graph free. EU-hosted.

Match your first assets free. No packet to your network, nothing installed, EU-hosted.