Skip to content

Incident Response

faktoora operates a structured incident management process aligned with the requirements of DORA (Digital Operational Resilience Act). This page describes how we detect, classify, respond to and communicate security incidents.

Detection

We use several layers of monitoring and automated alerting to detect incidents early in our application, infrastructure and supply chain.

Classification

Assessment begins within 30 minutes of becoming aware of an incident; it is classified according to the following criteria:

FactorAssessment
Number of customers affectedSingle customer, a subset or all customers
Duration of the impactTemporary, sustained or ongoing
Data sensitivityPublic, internal, confidential or restricted
Service criticalityCore platform, supporting service or non-critical
Economic impactRevenue, contractual or regulatory implications

Severity Levels

Business hours are Monday to Friday, 09:00–17:00 (CET/CEST), excluding public holidays in Bavaria. For customers on the Custom ("Individuell", Enterprise) plan, the deadlines in section 10 of the Service Level Agreement apply.

SeverityDefinitionResponse time
CriticalCore service unavailable or confirmed data breachAutomatic detection around the clock; assessment begins within 30 minutes of becoming aware
HighSignificant user-facing impact or potential data exposureWithout undue delay during business hours
MediumLimited impact, no data at riskWithin 1 business day
LowMinor issue, no user impactWithin 5 business days

Customer Communication

SeverityNotification periodChannel
CriticalWithin 1 hour of classification, updates every 2 hoursEmail to affected customers
HighWithin 4 hours where users are affectedEmail to affected customers
MediumAvailable on requestVia support channels
LowAvailable on requestVia support channels

Supporting Your Regulatory Reporting

Many of our customers have their own reporting obligations – for example financial entities under DORA or controllers under the GDPR. Our incident process is designed to provide you promptly with the information for your own notifications:

InformationTimingContent
Initial notificationWithin 4 hours of classification as a major incident (no later than 24 hours after detection)Incident type, affected services, time of detection, preliminary impact assessment
Intermediate updateWithin 72 hours of the initial notificationUpdated impact assessment, cause (if known), containment measures, affected data
Final reportWithin 1 month of the intermediate updateRoot cause analysis, overall impact, remedial measures, lessons learned

We notify our customers of personal data breaches without undue delay, as set out in our Data Processing Agreement. Where faktoora itself is the controller, we notify the competent supervisory authority in accordance with Art. 33 GDPR.

Containment and Recovery

Our incident response process follows these phases:

  1. Containment - Isolate affected systems to prevent further impact
  2. Evidence preservation - Secure audit logs, application logs and access logs
  3. Root cause analysis - Identify the underlying cause
  4. Remediation - Implement fixes and verify the remediation
  5. Recovery - Restore normal operations and confirm stability

Post-Incident Review

Every incident of severity High or Critical is reviewed within 5 business days:

  • Complete timeline of detection, response and recovery
  • Root cause analysis
  • Impact assessment (customers, data, services)
  • Evaluation of the effectiveness of the response
  • Preventive measures to avoid recurrence

Lessons learned are documented and integrated into our security controls and procedures.

Retention of Incident Records

All incident records are retained for at least 5 years, based on DORA.

Reporting an Incident

If you suspect a security incident affecting faktoora or your data:

To report a vulnerability, please visit our Vulnerability Disclosure page.