Incident response je proces rukovanja sigurnosnim incidentima (kršenja, napadi) — detektovanje, sadržavanje, iskorenjivanje, oporavak i učenje. Pošto se kršenja mogu dogoditi unatoč odbrambenim merama, imati plan za efikasan odgovor je važno za minimiziranje štete.
Zašto je incident response bitan
Despite defenses, security incidents WILL happen (no system is perfectly secure):
→ being PREPARED to respond limits damage, downtime, and data loss
→ a poor/slow/panicked response makes breaches far worse
→ have a PLAN before you need it (you can't improvise a good response mid-crisis).
Životni ciklus incident response-a
1. PREPARATION → plan, tools, roles, runbooks, monitoring/logging in place beforehand
2. DETECTION & ANALYSIS → identify the incident (monitoring, alerts); assess scope/severity
3. CONTAINMENT → stop the spread/limit damage (isolate affected systems, revoke access)
4. ERADICATION → remove the threat (close the vulnerability, remove malware/access)
5. RECOVERY → restore systems safely; verify they're clean; resume operations
6. POST-INCIDENT (lessons learned) → analyze what happened, improve defenses & the process
(BLAMELESS — focus on fixing, not blaming)
