A standard incident form
Fixed fields, the same for everybody: what happened and when it started, the cause, the nature of it, the potential consequences and the measures you implemented.
One incident log for GDPR and NIS2
A personal data breach and a security incident go in the same register, on the same form. 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
.jpeg?width=131&height=26&name=right_people_logo%20(1).jpeg){kind=small}
.jpg?width=58&height=26&name=Praktiserende%20L%C3%A6gers%20Organisation%20(1).jpg){kind=small}
.jpg?width=108&height=26&name=finans%20danmark%20(1).jpg){kind=small}
.jpg?width=89&height=26&name=klasselotteri%20(1).jpg){kind=small}
-1.png?width=68&height=52&name=bws_shipping_rgb%20-%20Kopi%20(2)-1.png)
.jpeg?width=135&height=26&name=AH%20industries%20(1).jpeg){kind=small}
.jpg?width=493&height=57&name=KAUFMANN%20(1).jpg)
One incident log Meridian's incidents stopped living in a mailbox
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 register for both jobs, so a personal data breach and an operational security incident go the same way.
-
Cause, nature, potential consequences and the measures implemented, captured while people still remember them.
-
Whether it was reported, when the report was made, and whether the affected individuals were notified.
-
One incident exports as a zip with a PDF summary, and the whole log exports as Excel.
One incident log Incidents that live in a mailbox
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.
-
Everybody who handled it wrote it down somewhere different, and nothing says which version is the account of record.
-
The evidence, the extract, the receipt, the supplier's reply, sits wherever it happened to land.
-
When somebody asks what you actually did about it, the answer is a search rather than a document.
One incident log One drill, two regimes
Anders and Sofie do not need two systems and two habits. The incident log is one standard form with fixed fields, and both of them fill in the same one.
-
What happened and when it started, the cause, the nature of it, and the potential consequences for individuals, for the company and for the services.
-
Which types of personal data were involved, when it is that kind of incident.
-
The measures you implemented to deal with it and to limit the damage.
One incident log Reported, notified, and the proof attached
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.
-
Whether the incident was reported to the data protection authority, and when the report was made.
-
Whether the affected individuals were notified.
-
The documentation attached to the incident itself, an extract from another system or an email receipt for the notification. Files can go on while you create the incident or at any point after.
One incident log What happens next gets a name and a date
Registering the incident is half the job. The other half is the work that follows it, and that is the half that quietly stalls.
-
Create a task straight from the incident page with a name, a responsible person, a business area and a deadline.
-
The task links back to the incident automatically, so the follow-up and the account of what happened stay together.
-
Mention a colleague in a task comment or in the incident's own cause field, and the discussion stays with the record instead of in a chat thread.
One incident log When somebody asks to see it
This is what the log is for. Somebody asks months later, and you want one artefact rather than a reconstruction.
-
A single incident downloads as a zip of its uploaded documents plus a PDF summary of the incident.
-
The full log exports as Excel, for an internal review, a report or an audit.
-
Incidents by severity is one of the fixed widgets on the Compliance Dashboard, for the group as a whole or drilled down to one company.
One incident log We hold the record of the reporting. You do the reporting.
Two boundaries, said plainly, because they are the two things everybody assumes. Better read here than discovered during your first incident.
-
There is no countdown. The platform does not track the statutory deadlines, not the ones under NIS2 and not the 72-hour one under GDPR, and nothing on an incident counts down.
-
Nothing is filed for you. There is no submission to a supervisory authority and no receipt handling. You report where you have always reported, and the log holds the record that you did.
-
The platform is the record, not the detector. It does not scan and it never derives a status from breaches found automatically, so it is not a SIEM, and spotting the incident is still your job.
One incident log Frameworks this covers
One log, and the two regimes that send people looking for it.
-
GDPR
Read about GDPRArticles 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
Read about NIS2Incident 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.
Our Customers
+400
companies
+10.000
users
+79.000
contracts
+14.000
processing activities
.legal's team has consistently demonstrated a commitment to innovation while being responsive to the needs of our mutual clients.
With .legal, we've gained a simpler and more manageable solution that better suits our needs
.legal has been the right choice for us. .legal are professional and welcoming with skilled employees.
Firstly, it means that not all the work is in one place (me), and secondly, that the understanding of GDPR is implemented throughout the organisation.
From .legal, we experience an incredibly high degree of flexibility and willingness to adapt features to our local needs.
.legal's team has consistently demonstrated a commitment to innovation while being responsive to the needs of our mutual clients.
With .legal, we've gained a simpler and more manageable solution that better suits our needs
.legal has been the right choice for us. .legal are professional and welcoming with skilled employees.
Firstly, it means that not all the work is in one place (me), and secondly, that the understanding of GDPR is implemented throughout the organisation.
From .legal, we experience an incredibly high degree of flexibility and willingness to adapt features to our local needs.
We are satisfied with the switch to .legal – it has strengthened our compliance work, made processes easier to manage and more transparent, and improved cross-team collaboration
It just works! It is so easy and user-friendly, and the overview of processing activities is brilliant.
.legal has really understood what it means to create a user-friendly and efficient solution. Privacy is an attractive product compared to price and functionality.
.legal continuously update the platform to ensure their customers always remain compliant. In our view, any other choice would be a downgrade.
The implementation of .legal has made a difference in the way we handle compliance. The system has created structure and overview, which has had concrete benefits.
We are satisfied with the switch to .legal – it has strengthened our compliance work, made processes easier to manage and more transparent, and improved cross-team collaboration
It just works! It is so easy and user-friendly, and the overview of processing activities is brilliant.
.legal has really understood what it means to create a user-friendly and efficient solution. Privacy is an attractive product compared to price and functionality.
.legal continuously update the platform to ensure their customers always remain compliant. In our view, any other choice would be a downgrade.
The implementation of .legal has made a difference in the way we handle compliance. The system has created structure and overview, which has had concrete benefits.
Use cases
Book demo
Find the job you need done
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.
Compliance & GRC leadCISO & IT securityDPOLegal counselExecutive & board
Energy & utilitiesFinancial servicesManufacturingPublic sectorHealthcareProfessional servicesRetail & e-commerceTechnology
SMVMid-marketEnterprise & group
GDPRNIS2ISO 27001CIS18DORAePrivacyAI ActD-mærketData Act
Compliance & GRC lead
Run awareness training that reaches every colleague
Send out training and policies, chase the stragglers automatically, and prove every colleague completed it. You bring the material, we run the rails.
See awareness training
Compliance & GRC lead
Manage compliance across a group of companies
Run every company in the group from one platform, document once at group level, and still report entity by entity. Delivered by the Group Companies add-on.
See group compliance
Legal counsel
Run due diligence on your vendors
Classify a vendor on your own criteria, get the answers and documents you need with no login for them, and move the approved ones straight into contracts.
See vendor due diligence
Compliance & GRC lead
Multi-framework compliance: do the work once
Do a control once and it counts across every framework it maps to, with a simulated score on the ones you haven't started yet.
See multi-framework compliance
CISO & IT security
Get NIS2-ready without starting from scratch
Build on the ISO 27001 work you've already done, switch NIS2 on, and let a simulated score show how far ahead you already are.
See NIS2 readiness
DPO
From twelve spreadsheets to one record of processing
Your GDPR documentation already exists, it just lives in spreadsheets. Export what you have and we structure it in .legal for you, typically inside two weeks.
See the move off spreadsheets
Compliance & GRC lead
Build one risk register for the whole organisation
One register across GDPR, NIS2, AI and information security, where each risk area keeps its own matrix, scale and appetite. Delivered by the Enterprise Risk Management add-on.
See the risk register
Executive & board
Give the board a risk picture it can act on
One management report across every risk area: entities assessed, risks above appetite, exposure now and once the open plans are done. Export it with your own comment on it.
See board risk reporting
CISO & IT security
Run your ISMS in one platform
The frameworks you answer to, the controls beneath them and the documentation that proves the work happened, all three in one module, with status updating itself from completed tasks.
See how the ISMS runs
DPO
Keep your records of processing always audit-ready
The Article 30 record is a report drawn from your processing activities, not a document you rebuild before an inspection. Correct an activity and the record says so immediately.
See the record stay current
Compliance & GRC lead
Get ready for the D-seal
D-Seal's own criteria sit in the platform under a formal agreement with D-Seal, mapped 1:1 with the level 3 criteria. Work the controls, collect the documentation, export it per task.
See the D-seal route
Legal counsel
Contract management with obligations and renewals
Register what each contract obliges you to do, delegate it as tasks with deadlines, and see in one overview that it gets done on time. Renewals notify ahead of the date.
See obligations and renewals
No use cases match that combination yet. Try removing a filter.
