Incident Response: Process, Roles and Reporting Deadlines in the Event of an Emergency

Incident Response: Process, Roles and Reporting Deadlines in the Event of an Emergency

On 10 November 2026, it emerged that unknown individuals had accessed around 3,900 records relating to staff at the University of Tübingen, including names, dates of birth, work email addresses and usernames. According to the university, the security breach arose because several settings recommended by the software manufacturer, when combined, created a vulnerability (Golem.de).

Such a vulnerability can never be completely ruled out. What matters is how quickly an organisation detects, assesses and reports an incident.

Seven phases provide a structured approach to dealing with an incident

Incident response is the structured handling of security incidents: from detection through to a return to normal operations. The aim is to limit damage, secure evidence and comply with legal obligations. The process can be adapted to the organisation’s size and sector:

  1. Preparation: Guidelines, contact lists, roles and tools are defined in advance.

  2. Detection: Anomalies are identified via monitoring, SIEM or alerts.

  3. Analysis: The scope, affected systems and severity are assessed.

  4. Containment: Affected systems are isolated. It is better to disconnect them from the network than to switch them off, as switching them off results in the loss of volatile data required for forensic analysis.

  5. Remediation: The root cause is addressed and vulnerabilities are patched.

  6. Recovery: Systems are returned to normal operation in a controlled manner.

  7. Follow-up: Lessons learnt are fed back into the process.

Every measure must be recorded in the log, including the timestamp, the person responsible and the justification. This forms the basis for forensic analysis, reports to the authorities, insurers and any potential criminal charges. Under Article 33(5) of the GDPR, data breaches must in any case be documented in full.

Two reporting deadlines run in parallel

GDPR: The controller must report a data breach to the competent supervisory authority without undue delay and, where possible, within 72 hours of becoming aware of it. Exceptions are cases where the breach is unlikely to result in a risk to data subjects (Article 33 of the GDPR). In the event of a high risk, the data subjects must also be informed (Art. 34 GDPR).

NIS2: The Directive has been transposed into the BSI Act since 6 December 2025. Affected organisations must report significant security incidents to the BSI in three stages: an early warning within 24 hours, a follow-up report within 72 hours, and a final report no later than one month after the initial report (usd AG).

Both time limits commence upon becoming aware of the incident, not upon completion of the analysis, and one report does not replace the other. If a criminal offence has been committed, such as unauthorised access to data, the possibility of filing a criminal complaint must also be considered. Whether and how a report is required is determined on a case-by-case basis by the data protection officer or the legal department.

Andreas Papadaniil, Managing Director, suresecure
In an emergency, a plan that nobody knows about is of no use. Roles, reporting channels and decision-making powers must be clearly defined and practised before the first reporting deadline begins.
Andreas Papadaniil, Managing Director, suresecure

It must be established in advance who makes decisions in an emergency

What counts as a reportable incident? Who is authorised to shut down systems? Who communicates with the authorities, customers and the press? These questions must be clarified before an incident occurs, not whilst it is happening. The Information Security Officer (ISO) coordinates processes, drills and escalations and acts as the interface between IT, senior management and the authorities.

The Data Protection Officer should be involved at an early stage, as the GDPR reporting period begins as soon as the incident comes to light. Where necessary, the legal department and external consultants are also brought in.

A SOC reduces the time taken to become aware of an incident

Reporting deadlines begin once an incident is known. A SOC with round-the-clock monitoring detects incidents even at night and at weekends. This reduces the time taken to decide whether a report is necessary. Two operating models are common:

  • Fully managed: An external service provider handles monitoring, detection and incident response continuously and comprehensively.

  • Co-Managed: The in-house security team and an external partner share the tasks, with clearly defined responsibilities.

suresecure’s Managed SOC evolved from incident response and is available as Full-Managed and Co-Managed options.

Conclusion: You’re only prepared if you’ve practised for an emergency

A security breach like the one in Tübingen cannot always be prevented. But how a company responds afterwards certainly can. An incident response plan that has been run through under realistic conditions reveals gaps in roles and reporting channels before a real incident exposes them.

For those who’d like to test this in a live setting, we recommend the Incident Drill. It simulates real-world attack scenarios based on the MITRE ATT&CK framework in a controlled environment and tests how detection, escalation and communication interact under time pressure.

FAQ

How long does an incident response investigation take?

That depends on the complexity and scope of the incident. Initial containment can take place within hours, whilst a full forensic investigation often takes several weeks.

What tools are needed for incident response?

Typical components include SIEM for detection, EDR/MDR for endpoint analysis and SOAR for automating response steps. The choice depends on the size of the organisation and its IT environment.

How is a security incident properly documented?

Each action is recorded with a timestamp, the person responsible and the reason. The documentation is used for reporting to the authorities, insurance claims and follow-up.

What should an incident response plan include?

Roles, contact channels, escalation levels, initial technical measures and reporting obligations. The plan is tested regularly and adapted to the current threat landscape.

What happens after a security incident has been reported?

This is usually followed by an in-depth analysis, consultation with supervisory authorities, a criminal complaint where appropriate, and measures designed to prevent future incidents.