Incident Response process
MyDesk has a documented incident response procedure that defines roles, responsibilities and communication obligations for security incidents. The procedure is based on the NIST Cybersecurity Framework and is approved by management.
Communication obligations
In case of security incidents affecting customers, MyDesk commits to the following communication:
- Early warning: Within 24 hours of knowledge of the incident
- Status update: Within 48 hours after initial notification
- Final report: Typically within one month after the incident has ended
- Continuous updates for long-lasting incidents
- GDPR notification to supervisory authority within 72 hours of data breach
Incident classification
Incidents are classified by severity (P1-P4), which determines the response time and escalation process. P1 (critical) incidents are handled with immediate response and direct management involvement.
Post-incident analysis
At the end of an incident, a post-incident analysis (PIR/post-mortem) is conducted to identify root causes and prevent recurrence. Results are documented and shared with relevant stakeholders.
Exercises and tests
MyDesk conducts regular tabletop exercises and simulated incident scenarios to test and improve incident response capabilities.
Incident Response
- Early warning - Within 24 hours
- Status update - Within 48 hours
- Final report - Within 1 month
- GDPR notification - Within 72 hours
- P1-P4 classification
- Post-incident analysis
- Regular exercises