Bundle the evidence for each obligation
26 obligations, 21 fully evidenced, as of 14 May
Energy
The answer arrives a week after the question.Open agent
Enlarge demo
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
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.
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.
26 obligations, 21 fully evidenced, as of 14 May
Registration of 8 November last year, 2 contact details out of date
nachweismappe_termin_mai.pdf, 26 obligations, 5 open points
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 records which report went out when and what is still outstanding. Executive management submits the report itself.
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
Data processing
Responsible teams
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?
All agents
60%
less research time
Regulatory management, legal, network operations
50%
less reporting effort
Sustainability, management
70%
less reporting effort
Network management, controlling
60%
less preparation time
Executive board, management
45%
less evidence effort
Metering point operations, regulation
40%
fewer delivery delays
Purchasing, dispatch, production