#088Tutorial1 min

Respond to a new security alert

The first minutes after an alert: confirm, contain, fix, verify.

Hackaiz team · updated 18/11/2026

Illustration: an engineer watches charts on several screens.
Illustration: an engineer watches charts on several screens. Illustrative photo, not a screenshot.

01First, read the alert

An alert reports a new finding or an important change on a monitored asset. Open it from the notification or the dashboard: it links to the finding, its level and its evidence.

02The four steps of a response

For a Danger alert, follow this order.

  1. 1Confirm: read the evidence and check that the cited item exists in the live version.
  2. 2Contain: if a secret is exposed, rotate it immediately at its provider; if a table is open, restrict its access rule.
  3. 3Fix: prepare a fix or apply it manually, then deploy.
  4. 4Verify: re-run the analysis and keep the report as a record.

03Tell the right people

Notify the project owner and, if personal data may have been exposed, assess your notification obligations with them. Hackaiz provides technical facts, not legal advice.

04Prevent it from coming back

Add a pre-deployment check, such as the Hackaiz GitHub Action, to block a regression on a proven risk.

Tip: Write down the alert time, your actions and their times: this log will be valuable if questions come later.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles