A template for each kind of incident
Five ready-made templates, from personal data breach to NIS2 incident, each with its own steps and fields: what happened and when, the cause, the consequences and the measures you implemented.
Modules
.legal AI
All AI features →Integrations
See all integrations →Platform & features
Understand the rules
See it in action
All customer stories →Plan your switch
Stay up to date
A personal data breach and a security incident go in the same register, each with its own template. Record what happened and what you did about it, attach the documentation that proves it, delegate the follow-up, and export the lot when somebody asks six months later.
Unlimited users • Free onboarding and support • No commitment
One incident log
Anders Krogh is CISO at Meridian Nordic, an energy group with entities in Denmark, Sweden and Germany, and NIS2, ISO 27001 and GDPR all live at the same time. Sofie Bruhn, the group DPO, sits with her own half of the same job. Incidents used to be handled in an email thread and written up in a Word file afterwards, if anybody got round to it. Now the two of them register in the same log: what happened, when it started, what caused it, what was done about it, and who was told. The documentation is attached to the record, and the follow-up is a task with somebody's name and a date on it.
One log, two regimes
A personal data breach and an operational security incident are registered in the same place, by the same drill, each with the template that fits it.
Evidence on the record
Attach the extract, the email receipt and the vendor's reply to the incident itself, while you create it or at any point after.
Follow-up with a name on it
Create a task straight from the incident with a responsible person, a business area and a deadline, linked back automatically.
It leaves the platform
One incident as a zip of its documents plus a PDF summary, and the list as Excel with Custom Lists, whenever somebody asks to see it.
One incident log
The incident itself is rarely the hard part six months later. The hard part is that the account of it is spread across four inboxes and one person's memory.
One incident log
Anders and Sofie do not need two systems and two habits. The incident log is one register, and every incident starts from the template that fits it: a personal data breach for Sofie, an NIS2 incident for Anders. Same log, same routine, and the right questions for each.
One incident log
The two questions that come back later are whether you told the authority and whether you told the people affected. Both sit on the record, and so does what proves it.
One incident log
Registering the incident is half the job. The other half is the work that follows it, and that is the half that quietly stalls.
One incident log
This is what the log is for. Somebody asks months later, and you want one artefact rather than a reconstruction.
One incident log
Two boundaries, said plainly, because they are the two things everybody assumes. Better read here than discovered during your first incident.
Five ready-made templates, from personal data breach to NIS2 incident, each with its own steps and fields: what happened and when, the cause, the consequences and the measures you implemented.
When the incident happened, whether and when it was reported to the data protection authority, and whether the affected individuals were notified. You keep track of the deadline yourself.
Upload files while you create the incident or afterwards, an extract from another system or an email receipt for the notification, all gathered on the record. Link the incident to the assets, vendors, processing activities and processes it affected.
Create the follow-up from the incident page with a name, a responsible person, a business area and a deadline. The task links back to the incident automatically.
A single incident downloads as a zip of its uploaded documents plus a PDF summary. The list exports to Excel for an internal review, a report or an audit, with the Custom Lists add-on.
One of the fixed widgets on the Compliance Dashboard shows how registered incidents distribute by severity, for the whole group or drilled down to one company.
One incident log
One log, and the two regimes that send people looking for it.
GDPR
Articles 33 and 34 are a documentation job: what happened, whether it had to be reported, whether the people affected were told, and what proves it. The fields on the incident log are shaped around exactly that.
NIS2
Incident handling is one of the risk-management measures behind the services you deliver. .legal holds the NIS2 framework and the controls beneath it, and the log is where you document your own handling. Reporting to an authority happens outside the platform.
Where the incident log sits alongside the record of processing, the processing activities, the assets and the annual wheel (årshjul). The templates for personal data breaches and access requests come with it.
Explore Data ProtectionWhere your security documentation and controls live, so incident registration sits next to the controls that ask for it. The templates for NIS2 incidents and security incidents come with it, as do the framework templates for NIS2 and ISO 27001 among others. Add the Frameworks module when one task should count towards several frameworks at once.
Explore Information and Cyber Securitycompanies
users
contracts
processing activities
Bech-Bruun
Mikkel Friis Rossa (Partner)
Fenerum
Rasmus Boutrup (Financial Controller)
Lægeforeningen
Michael Berner (Lawyer)
Molecule Consultancy
Nanna Rodian Christensen (HR & Operational Manager)
Plum Safety
Ulrik Dueholm Beckmann (QC, CM og ESG Lead)
Bech-Bruun
Mikkel Friis Rossa (Partner)
Fenerum
Rasmus Boutrup (Financial Controller)
Lægeforeningen
Michael Berner (Lawyer)
Molecule Consultancy
Nanna Rodian Christensen (HR & Operational Manager)
Plum Safety
Ulrik Dueholm Beckmann (QC, CM og ESG Lead)
Novicell
Julie Oxenvad (Legal Consultant)
Min By Media
Tinna Schultz (HR Manager)
DMJX
Kaspar Rochholz (GDPR Coordinator)
Axel Kaufmann ApS
Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)
NRGi
Mette Mühlendorph (Compliance Specialist)
Novicell
Julie Oxenvad (Legal Consultant)
Min By Media
Tinna Schultz (HR Manager)
DMJX
Kaspar Rochholz (GDPR Coordinator)
Axel Kaufmann ApS
Julie Lundkvist Andreasen (Lawyer and Head of Costumer Service)
NRGi
Mette Mühlendorph (Compliance Specialist)
Every use case is a real piece of compliance work, told the way it actually runs in the platform. Filter by who you are, what you work with, and which frameworks you answer to.
24 use cases
No use cases match that combination yet. Try removing a filter.
No, and we would rather say it here than let you find out during an incident. There is no countdown on an incident, no 24-hour or 72-hour timer, no one-month reminder, and nothing tells you that a clock has started running. What the log does is hold the decision and the proof: when the incident happened, whether it had to be reported, whether it was, when the report was made, and whether the affected individuals were notified. We hold the record of the reporting. You do the reporting.
No. There is no submission, no form generated for a supervisory authority and no receipt handling. You report the way you report today, and then the log records that it happened, when it happened and what proves it, an email receipt for example. The point is that afterwards the account and the evidence sit in the same place instead of in somebody's inbox.
One log with five standard templates: personal data breach, data subject access request, NIS2 incident, security incident and vendor incident. The personal data breach template is shaped around Articles 33 and 34, with the types of personal data involved and the notification of the individuals concerned, and the NIS2 incident template covers incidents affecting your network and information systems. All of them live in the same register, because the questions asked afterwards are the same ones: what happened, what did you do about it, who did you tell, and can you show it.
Getting NIS2-ready without starting from scratchNo. The platform is the record, not the detector. It does not scan anything and it never derives a status from security breaches found automatically, which is exactly what a SIEM does. Spotting the incident out there is still your job, and registering it is a person filling in a form. Colleagues without a login can report what they noticed as an observation, and an observation converts straight into an incident with the template you choose. If what you need is a SIEM, you need to buy one somewhere else, because this does not replace it.
How the management system runs day to dayTwo things. A single incident downloads as a zip of its uploaded documents together with a PDF summary of the incident itself. The incident list can be filtered and exported to Excel, for an internal review, a report or an audit. Export to Excel and saved views need the Custom Lists add-on.
Keeping your records of processing audit-readyYes, at dashboard level. Incidents by severity is one of the fixed widgets on the Compliance Dashboard, showing how registered incidents distribute by severity, for the whole group or drilled down to a single company. Read it as an operational overview of where the pressure is, not as a management report and not as a status on your compliance.
Yes. The incident flow has a Relations step where you link the incident to the assets and vendors it affected, and to processing activities and processes, so the connection is part of the record rather than a line of text.
Yes, with the Templates and Custom Fields add-on. Build your own incident templates, from scratch or based on a standard one, add and remove fields, and decide which must be filled in before the incident can be created. A field can be text, a dropdown, a date, a number, a checkbox or legal entities, for example. The standard templates work without the add-on.