liveBook · Manning

Incident response guideline

As explained in Grokking Software Architecture

An incident response plan is a documented set of actions for detecting, containing, investigating, and recovering from a security incident.

When a secret may be compromised, a concise, rehearsed response playbook helps teams act quickly and limit the attacker’s opportunity. section 11.5.3

A response to a suspected secret leak should:

  • Revoke the secret and generate a replacement. section 11.5.3
  • Force re-authentication by severing active connections or temporarily blocking affected services. section 11.5.3
  • Review logs to establish the timeline and scope of suspicious activity. section 11.5.3
  • Notify security, operations, and—if customer data is involved—legal stakeholders. section 11.5.3
  • Find and fix the leak’s root cause to prevent recurrence. section 11.5.3

How Grokking Software Architecture covers it

How deep it goes
Specify five response actions and recommend documenting and rehearsing them.
Examples
Use suspected leaks from a hardcoded Git commit or social engineering to motivate root-cause investigation.
What you can do after
Apply a five-step playbook to revoke compromised credentials, contain access, investigate, notify stakeholders, and remediate the cause.
How it connects
Connects secret rotation with credential revocation, re-authentication, log analysis, and incident notification.

Also explained in

Compare how 2 books explain incident response guideline →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.