00% SCROLL
FOR CRITICAL INFRASTRUCTURE

Resilience you can
document and defend.

NIS2 risk assessments and incident reports produced inside your own perimeter — air-gappable, with a complete audit record.

How sovereignty works
ON-PREM OR SOVEREIGN EU CLOUDZERO DATA EGRESSNEVER TRAINED ON YOUR DATA

Every report, contained.

NIS2 and incident reports — drafted, in review, filed.

NIS2 Compliance
Docs
16
In review
4
Approved
10+10%
Incident Report
Docs
9
In review
2
Approved
7+6%
Continuity Plan
Docs
12
In review
1
Approved
11+40%

An agent inside the perimeter.

It drafts the incident report from your SIEM timeline — air-gappable, nothing crosses the boundary.

AIR-GAPPABLEON TIME
ResearcherWorking
On it — opening the SIEM timeline.
Anomaly contained at 02:14
No data crossed the perimeter
Drafting the NIS2 report…
Reading the OT segment…
Delegate to…
ResearcherAgent
Legal AnalystAgent
Data AnalystAgent
WriterAgent
S Steven
M Meg

Air-gappable by design.

Deploy on-prem — even fully air-gapped. Operational data never crosses a boundary you don’t own, and agents run with no external call in normal use.

ON-PREMAIR-GAPPABLEZERO EGRESSEU ONLY

Made for NIS2.

NIS2

Risk assessments and incident reports, evidenced and on time.

Audit trail

Every action logged for the regulator.

Sovereignty

Nothing leaves the network — by architecture, not policy.

Precise, fast, contained.

Audit-ready citations

Reports trace every claim to its source.

Reporting as a Skill

Recurring NIS2 and incident reports become one click.

Contained by design

Runs where you put it; nothing leaves the network in normal use.

An incident report, filed on time.

Diana drafts the significant-incident report from your SIEM timeline — inside the perimeter, ready for the 24-hour deadline.

Document
nis2-incident-report.docx Editable Download
NIS2 REPORT
NIS2 Significant Incident Report
Security Operations · within 24h · contained
Incident

An anomaly on the OT segment was contained within 22 minutes.

SIEM · 02:14
Impact

No safety function was affected; no data crossed the perimeter.

Log · seg-OT
Response

The playbook was executed and the regulator notified on time.

Playbook §2
Ask Diana about this document — select a line to cite or redline…

The work you hand to Diana.

Produce the NIS2 compliance reportPDF
Draft an incident report from the timelineDOCX
Compile a risk assessment from the registersXLSX
Write the continuity planDOCX

What operators ask.

Can it run fully air-gapped?
Yes — deploy on-prem with no external connection at all.
Will it meet the NIS2 deadlines?
Recurring reports become a one-click Skill, evidenced and on time.
Does operational data leave the network?
No — containment is by architecture, not policy.
How does Diana get our documents?
You attach files or point it at a project folder — nothing is uploaded to a third party. It reads them in place, inside your environment.
How do we get started?
Request a deployment and we install Diana on your own infrastructure or a sovereign EU cloud, with your templates and sources connected.

What you’ll produce.

Inside the perimeter.

DRAFTS
NIS2_Compliance.pdfPDF
Incident_Report.docxDOCX
Risk_Assessment.xlsxXLSX
Continuity_Plan.docxDOCX
Runs on your infrastructure. Zero data egress. Never used to train a model.

Sovereign AI,
on your terms.

Give Critical Infrastructure a workspace that turns your own sources into finished work — entirely inside your walls.

See the architecture