No safeguard removes risk completely. What matters is knowing in advance what to do when something happens. An incident response plan is a short, practical document that defines who does what, in which order.
Components of the plan
- Roles and contact list: Incident lead, IT owner, management, legal and communications, with phone numbers (email may be down).
- Incident classification: Ransomware, account takeover, data leak, service outage and their severity levels.
- Critical asset list: Which system's outage costs most and which is restored first?
- Backup and recovery info: Where backups are and how to restore; see backup strategy.
What to do in the first 24 hours
- Detect and verify: Confirm the alert is real and note the time.
- Contain: Isolate affected devices from the network (isolating rather than powering off preserves evidence), reset passwords and end sessions on suspicious accounts.
- Preserve evidence: Keep logs, emails and screenshots.
- Assess impact: Determine which data and systems are affected.
- Communicate: Inform management and, if needed, insurer and legal adviser; name one spokesperson to avoid spreading wrong information.
- Clean and recover: Do not restore before closing the root cause; return from a clean backup.
Legal notification
For a personal data breach, notifying the authority and affected people within the statutory period may be required; see the KVKK compliance checklist. Take legal assessment to your legal adviser.
After the incident
Write a short report on what happened, why and what will change. For ransomware see the ransomware guide; for prevention see MFA, zero trust and penetration testing.
Test the plan
Run a tabletop exercise at least yearly; for the wider picture see cyber security basics.
ujans prepares incident response plans, runs exercises and provides technical help in an emergency.