Energy

NIS2 and KRITIS Evidence Agent

The status of a single obligation sits in three different places. The answer arrives a week after the question.

Answers auditors' questions on the status of security obligations with evidence, not assertions.

Answers auditors' questions on the status of security obligations with evidence, not assertions.

Open agent

Enlarge demo

Public administration

Four processes that take up the most time today

Developed in Germany · Hosted in the EU

Developed in Germany · Hosted in the EU or on-premises

Delivered together with

Sovereign hosting in Germany, single-tenant from the first user.

Sovereign hosting in Germany, single-tenant from the first user.

Legal, tax and compliance expertise for legally sound deployment.

Legal, tax and compliance expertise for legally sound deployment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

Advisory and implementation for the public sector, starting with the AI readiness assessment.

One auditor's question, three strands of evidence and a folder last kept up to date by someone else.

The evidence for an obligation is rarely in one place. The designated officer keeps the registration, the technical measure sits in the operations team's ticketing system, and the approval is in the minutes of executive management. For every audit question, someone pulls these three strands together by hand, and then does it all again at the next audit.

3

evidence strands

Registration, technical measure and the management resolution are kept separately.

26

obligations

For each one, there has to be evidence of who implements it and since when.

2 days

per audit

Gathering everything, reconciling the status of each item, putting the evidence into one pack.

5

questions without evidence

For these, the minutes record a follow-up submission at the end of the audit.

The two days of preparation per audit shrink to one, the five questions without evidence are known before the audit instead of turning up in the minutes afterwards, and the evidence effort falls by 50%.

The 50% reduction in evidence effort is this agent's headline figure. The number of obligations and the two days of preparation per audit reflect a typical process at an operator; they were not measured.

Three steps through the process.

For every obligation, the agent documents its status with the registration, measure and resolution, and names the gaps; the information security officer judges whether an obligation is met.

1.

1.

Bundle the evidence for each obligation

For every obligation, the agent brings the three strands together: registration, technical measure and the management resolution. It records the date and source of every piece of evidence.

For every obligation, the agent brings the three strands together: registration, technical measure and the management resolution. It records the date and source of every piece of evidence.

26 obligations, 21 fully evidenced, as of 14 May

2.

2.

Track the registration status in the reporting portal

The agent compares the entity's data with what was last reported. It lists every change to contacts, assets or services individually.

The agent compares the entity's data with what was last reported. It lists every change to contacts, assets or services individually.

Registration of 8 November last year, 2 contact details out of date

3.

3.

Provide the evidence pack for the audit

The agent bundles evidence, status and open points into one evidence pack per audit topic. The information security officer takes it into the audit.

The agent bundles evidence, status and open points into one evidence pack per audit topic. The information security officer takes it into the audit.

nachweismappe_termin_mai.pdf, 26 obligations, 5 open points

What the agent does not do.

It does not determine that an obligation is met.

It does not determine that an obligation is met.

It shows which evidence exists for it and which is missing. The information security officer makes the assessment, and responsibility stays with executive management.

It does not report security incidents.

It does not report security incidents.

It records which report went out when and what is still outstanding. Executive management submits the report itself.

It does not check whether a technical measure actually works.

It does not check whether a technical measure actually works.

It sees in the ticketing system that network segmentation was reported as completed on 3 March. Only the operations team's test shows whether it holds in the control system.

Connected systems

ISMS tool

IT ticketing system

operator reporting portal

Operations

Deployment model

EU cloud or private cloud

EU cloud or private cloud

Data processing

GDPR-compliant, no model training on your data

GDPR-compliant, no model training on your data

Responsible teams

Information security, executive management, legal

Information security, executive management, legal

The questions that come up before the first meeting.

How quickly is the NIS2 and KRITIS Evidence Agent ready to use?

Where is the data processed?

Where does the figure “50% less evidence effort” come from?

Related agents.

All agents

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English

Platform

Industries

Services

Resources

Company

Pricing

From AI strategy to a running platform: we show you the way.

Talk to us

Log in

DE

EN

English
neuland.ai

The AI management and orchestration platform from Cologne.

Developed in Cologne. Operated in the EU or in your data center.

Certifications and compliance: ISO 27001, ISO 9001, GDPR, EU AI Act, DORA, StBerG, and BRAO
WirtschaftsWoche Best of Technology 2026 seal, 2nd place in the Process Management category for neuland.ai

© 2026 neuland AI AG