Skip to content
EclipticLink

Incident Response

Incident Response: First 24 Hours of a Breach

The first hours after discovering a breach shape everything that follows. A clear, practical sequence for containing the damage without destroying the evidence you'll need.

EclipticLink Security TeamUpdated 6 min read

Discovering a security incident is stressful, and stress leads to well-meaning mistakes like wiping a laptop, rebooting servers, or emailing the whole company from a compromised account. A simple, rehearsed sequence makes the difference.

Hour 0–1: Confirm and mobilize

  • Confirm what you are seeing and record when and how it was discovered.
  • Activate your incident response plan and name an incident lead.
  • Move coordination to an out-of-band channel, such as phones or a separate messaging workspace, in case email or chat is compromised.
  • Contact your incident response provider, legal counsel, and cyber insurer early. Many policies require prompt notification.

Hour 1–4: Contain without destroying evidence

  • Isolate, don't power off. Disconnect affected machines from the network; shutting down destroys memory evidence.
  • Disable or reset compromised accounts and revoke active sessions and tokens.
  • Block known malicious IPs, domains, and email senders.
  • Preserve logs before they rotate: identity, endpoint, firewall, cloud audit, and email.

Hour 4–12: Scope the incident

Work out the initial access vector, which systems and accounts are affected, and whether data was accessed or exfiltrated. AI-assisted forensics can turn large volumes of logs into a timeline quickly, but every conclusion should be verified by a responder before decisions are based on it.

Hour 12–24: Eradicate and communicate

  • Remove persistence such as malicious accounts, scheduled tasks, OAuth grants, and backdoors.
  • Plan recovery from known-clean backups.
  • Brief leadership with facts, not speculation.
  • With legal counsel, assess regulatory and contractual notification obligations, some of which have tight deadlines.

The best time to choose an incident response partner is before you need one. Retainers mean pre-agreed terms and faster mobilization.

After the incident

Run a blameless post-incident review, fix the root cause, and update your plan. Then test it with a tabletop exercise so the next response is faster.

If you are dealing with an incident now, contact EclipticLink's incident response team immediately.

Frequently asked questions

What should you do first after a data breach?

Confirm the incident, start a timestamped log, bring in your incident lead, and contain affected systems. Isolate them from the network rather than powering them off, because shutting down can destroy evidence held in memory.

Should you turn off a hacked computer?

Usually no. Disconnect it from the network instead. Powering it off can erase volatile evidence that investigators need to understand how the attacker got in and what they accessed.

How quickly do you have to report a data breach?

It depends on the law and sector. Under the GDPR, controllers generally must notify the supervisory authority within 72 hours of becoming aware of a reportable breach. Other rules set different deadlines, so involve legal counsel early.

Should you pay a ransomware demand?

CISA and the FBI advise against paying. Payment does not guarantee recovery and can fund further attacks. Involve counsel, law enforcement and your insurer before making any decision.

Sources and further reading

  • incident response
  • ransomware
  • data breach
  • digital forensics
  • incident response plan

Next step

Find out where you're exposed before an attacker does

Start with a free 30-minute assessment call with a security specialist. We'll review your setup, flag your highest-risk gaps, and outline a prioritized plan, whether or not you work with us afterwards.