Capture, assess and document security incidents and data breaches in a structured way – including graphical risk mapping. Statutory reporting obligations and deadlines under NIS-2 and the GDPR are recorded, with reporting deadlines monitored automatically; nine ready-to-use report templates – for BSI reports under NIS-2 and Section 32 BSIG, for KRITIS under Section 25 BSIG and for data protection notifications – keep deadlines, measures and reports in view at all times.
INCIDENT CAPTURE
Traceable incident documentation is the basis for a fast response and for evidence towards supervisory authorities. Capture security incidents and data breaches centrally via a structured form with all relevant details – including dates, deadlines, involved parties and the assessment of statutory reporting obligations.
MEASURES & REPORTS
Manage the handling of an incident from notification to follow-up. A hierarchical measures structure, custom report templates and intake forms bring all steps together in one place.
FAQ
The structured form captures times, deadlines, the people involved, the report and a description of the incident. It also covers category, severity and the assessment of whether a reporting obligation applies, as well as the responsible information security officer. You insert files directly into the document, and a graphical risk map places the incident in context.
Nine ready-to-use reporting templates are included: early warning, report and final report to the BSI under NIS-2 (Section 32 BSIG), the KRITIS incident report under Section 25 BSIG, and the data protection reports. You can also create your own reporting templates, including ones based on the supplied templates. You check every report in a preview before saving it.
For each report, preeco derives a clear status from the deadline and the time of reporting: deadline running, reported on time, reported late, deadline missed or no deadline. If a deadline is missed, you document the reason directly on the incident. Follow-ups send reminders by email and on the dashboard for upcoming steps. Which deadlines apply to your organization is a matter for legal assessment, which the software does not replace.
Yes. In the incidents area, you document both security incidents and personal data breaches, and the reporting templates cover BSI reports as well as data protection reports. preeco | information security and preeco | data protection share one platform: if you license both products, information security officers and data protection officers work in the same application and switch between the views.
You create forms through which possible incidents can be reported on your website or intranet; they are embedded using HTML code. You assess incoming reports and create an incident where needed. For reports under the German Whistleblower Protection Act (HinSchG), preeco | whistleblower is available as a separate platform that gives whistleblower anonymity special protection.
You set up the measures for an incident in a hierarchical structure, for example immediate actions with individual steps beneath them. You assign tasks to the responsible people, who are notified by email. The insights gained from the incident are recorded as lessons learned in the same document. On release, an immutable revision of the incident document is created automatically.
Optionally, yes. AI adds to and revises individual sections of the incident document. You review the result and decide what to adopt; the assessment of the incident and of the reporting obligation stays with your team. All AI activities are logged with function, user, model and status, so it remains clear where AI was involved.
In a personal conversation we show you how preeco | information security simplifies your security management.