Record an incident
Create a security incident record and flag it under Law 21.663 or Law 21.719 so SofIA Governance creates its reports with deadlines.
On this page
Record an incident as soon as you detect it. The detection date is what starts the legal deadlines, so it should be right from the start.
Before you start
You need the Administrator or Editor role. With Read only, the New incident button is disabled.
To assign an owner, the person must be in Company → Staff and active.
To indicate what the incident affected, these must be registered first: assets in Company → Assets, services in Company → Business services, processes in Company → Areas and processes, suppliers in Company → Suppliers and processing activities in Operations → Privacy (RoPA). Risks are in ISMS → Risk matrix, and controls appear when you adopt the first standard.
If your company is an Operator of Vital Importance (OIV), check that this classification is set in Company → Company details: it changes the ANCI deadlines (see Legal reporting deadlines).
Steps
Go to Operations → Incidents.
Press New incident. If there are no incidents yet, you can also use Record an incident in the center of the screen.
Fill in the general section:
Title (required): a phrase that identifies the incident.
Description: what happened, in a few lines.
Category: free text, for example ransomware, phishing or data leak.
Owner: the person handling the incident. They receive the reports when they are sent.
Severity: Low, Medium, High or Critical. It starts at Medium.
Status: it starts at Open. See Incident statuses and lifecycle.
Enter the dates:
Occurred on: when it happened, if you know.
Detected on (required): it comes with the current date and time. Correct it if you detected the incident earlier. Legal deadlines run from detection.
Check the legal boxes that apply:
Significant effect (Law 21.663): creates the reports to ANCI (early warning 3 h, update 72 h or 24 h if OIV, action plan 7 days if OIV and final report 15 days).
Personal data breach (Law 21.719): creates the notification to the Data Protection Agency and the communication to data subjects.
If personal data is involved, fill in Affected data subjects (an estimated number) and Affected data categories: type each category (for example, contact or health) and press Enter or the + button. To remove one, press the x on its tag.
Describe the rest, whatever you already know:
Impact
Containment measures
Root cause
Lessons learned
Mark what the incident affected. Next to each list's name you'll see how many you have selected, and if the list has more than six items, a Filter… field appears to search by name or code:
Affected assets (also by hostname or IP).
Affected services: they appear in the PDF of the reports to the authority.
Affected processes.
Affected processing activities (RoPA): in a personal data breach, the compromised processing activity. It appears in the PDF of the reports to the Agency and to data subjects.
Suppliers involved.
In Related risks, choose for each risk Materialized (the incident is that risk happening) or Arises from the incident (a risk you hadn't identified). Leave it as — Not related — if it doesn't apply. If you don't have risks yet, you'll see There are no risks yet. You can create one from the incident details.
In ISMS controls, filter by code or name (for example, 8.16 or backups) and mark Failed on the control that didn't work and Helped respond on the one that helped contain or recover. The same control can have both marks.
Press Save. The button is only enabled when there is a Title and Detected on.
Don't wait until you have all the information to record the incident. The early warning to ANCI is due 3 hours after detection: record the basics, check the legal box and fill in the rest as you go.
You decide the legal boxes. SofIA Governance doesn't classify the incident for you: if you're unsure whether it has a significant effect or whether personal data was compromised, check with your cybersecurity officer or your DPO before the first deadline expires.
What happens next
You'll see Incident INC-… recorded. and the incident appears in the list, with its sequential code for the year (for example, INC-2026-0004). The sequence follows the highest existing code: if you delete an incident, its code isn't reused for another one.
If you checked a legal box, the Laws column shows Law 21.663 · ANCI or Law 21.719 · Personal data, and Reports shows the progress (for example, 0/4 sent).
Pending reports appear above the list with their countdown. Open them to prepare them: see Prepare and send a report to the authority.
From the detail view you create the incident's new risk, action plan and finding: see Incident risks, controls, action plan and finding.
Edit an incident
Press the pencil (Edit) on the incident's row, or Edit incident in its detail view. The form opens as Edit incident, with what you already selected shown first in each list; change what you need and press Save. You'll see Incident updated.
When you save, SofIA Governance reviews the incident's reports:
If you checked a new legal box, it creates any missing reports.
If you changed Detected on, it recalculates the deadline of the reports not yet sent.
If you unchecked a box, in that same save it deletes the reports for that law that haven't been sent yet, whether in Draft or PDF generated. Sent ones are kept.
Reports with PDF generated that haven't been sent go back to Draft and their PDF is discarded, because the incident's data appears in the PDF. Download delivers a new one with the current data. Sent reports don't change.
Incidents that come from an integration
An event received from an integration becomes an incident when you press Escalate in its events, or automatically, if the integration has Open an incident automatically for critical events checked and an alert or incident of critical severity arrives. The incident is created like this:
with the event's title and a description that says which integration it comes from;
with the event's severity and, as Detected on, the date the event occurred (or was received);
with the event's asset as the affected asset, if the event included one;
with no legal boxes checked.
Open it, check Detected on, decide whether it has a significant effect or a data breach and flag it so its reports are created. More details in Review received events.
Related
Company for staff, assets and the regulatory classification