About this interactive
The earlier an incident is declared, the sooner the response starts and the less impact it has. But declaring sets off a lot: people are notified, work is dropped. Declare too early or too often and you cause panic and wasted work, and become the person who cried wolf.
So before anyone hits the button, the lesson puts in some checks:
- Validate it. Is the alert a true positive, a real problem, or a false positive? An alert nobody has checked is not yet an incident.
- Check it against the threshold. One user complaining is usually not an incident; the whole site down is. Each organization sets its own line, and the right number depends on how many users it has.
- Make sure the right person calls it. Usually IT, security or customer support do the initial research and declare. The lesson's own example: a user said drop everything, and it turned out to be her own internet connection.
Not declaring is not ignoring: the investigation starts right away. Declaring is what moves it into full incident response, with triage deciding who is brought in.
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →