Incident Response, Digital Forensics and Cyber Recovery
Free to read online. For a copy of this book, or to quote, highlight or reproduce any part of it, please request permission through the contact page beforehand.
Publication and use note
This document is an educational manuscript draft prepared for development, teaching and professional discussion. It is not legal advice, a guarantee of security, or a substitute for a qualified assessment of a specific environment. Technical configurations, product features, standards editions and legal obligations change. Before publication or operational use, verify all claims against current authoritative documentation and the relevant jurisdiction. Practical activities must be conducted only in authorised, controlled environments.
Preface
This volume forms part of the Cybersecurity & Digital Risk Management collection. It is designed to connect clear conceptual explanations with practical decisions, professional judgement and reflective learning. The aim is to help readers understand not only which controls may be useful, but why they matter, where they can fail and how their effectiveness can be evaluated.
Teach structured, evidence-aware incident management that limits harm and restores trustworthy operations.
Intended readership
The material is intended for students, educators, IT and security practitioners, managers, auditors, entrepreneurs and interested readers. Readers should adapt examples to their own context and seek specialist advice where technical, contractual or legal consequences are significant.
Learning outcomes
- Define roles and escalation paths for incident response.
- Triage events and preserve relevant evidence appropriately.
- Coordinate containment, eradication and recovery decisions.
- Explain chain of custody and limitations of digital evidence.
- Conduct post-incident reviews and improve resilience.
How to use this book
Read the chapters in sequence for a structured introduction, or use individual chapters as workshop material. Complete the practical tasks in a lab or with fictional data. For group learning, ask participants to state assumptions, compare alternative controls and explain the trade-offs between security, usability, cost, privacy and availability.
Contents
- Chapter 1: Incident Response as an Organisational Capability
- Chapter 2: Triage, Classification and Escalation
- Chapter 3: Containment and Eradication
- Chapter 4: Evidence Preservation and Chain of Custody
- Chapter 5: Ransomware and Account Compromise
- Chapter 6: Cloud and Hybrid Incident Handling
- Chapter 7: Business Continuity and Recovery
- Chapter 8: Communications, Review and Lessons Learned
- Applied case study
- Practical activities and assessment
- Glossary
- Selected references and further reading
Chapter 1: Incident Response as an Organisational Capability
An incident is an event that threatens or compromises the confidentiality, integrity or availability of systems or data. Not every alert is an incident, and not every incident is a cyberattack. A response capability requires clear authority, trained people, technical visibility, communication routes and pre-agreed decision criteria. Plans should reflect the organisation's size, legal context and operational dependencies.
Preparation includes maintaining asset inventories, contact lists, playbooks, backup procedures and supplier escalation details. Teams should know who can isolate a system, suspend accounts, contact legal counsel or approve public statements. Exercises expose gaps before a real event creates pressure.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on incident response as an organisational capability?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 2: Triage, Classification and Escalation
Triage determines what is known, what is uncertain, the possible scope and the urgency of action. Record the initial report, source, time, affected assets, observed indicators and actions already taken. Classification should consider business impact, data sensitivity, service criticality and the possibility of ongoing harm.
Escalation criteria should be explicit. A suspicious login on a low-impact test account may be handled differently from an administrator account accessing sensitive production systems. Analysts should avoid both premature dismissal and unsupported certainty. When evidence is incomplete, state confidence and what would change the assessment.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on triage, classification and escalation?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 3: Containment and Eradication
Containment aims to limit harm while preserving essential operations and evidence where possible. Options may include disabling compromised credentials, isolating endpoints, restricting network paths or pausing a vulnerable service. The appropriate choice depends on the threat, operational impact and likelihood that the attacker remains active. Decisions should be documented and authorised through the incident process.
Eradication removes the cause or persistence of compromise, but teams should not rush to rebuild before understanding the scope. Resetting one password may be insufficient if session tokens, recovery methods or other accounts were compromised. Verify clean configurations, patch exploited weaknesses and check for related affected systems.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on containment and eradication?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 4: Evidence Preservation and Chain of Custody
Digital evidence may include logs, files, device images, cloud audit records, messages and configuration history. Collection should follow authorised procedures and preserve integrity. Record who collected the material, when, from which source, using which method and where it was stored. Limit access and maintain a record of transfers. Hashes can help detect changes to collected files, but they do not by themselves prove that the original collection was complete or lawful.
Forensic actions can alter a system, and volatile data may disappear when a device is shut down. Responders should follow approved procedures and seek qualified forensic assistance when necessary. Legal requirements differ by jurisdiction, employment context and the type of investigation. Do not access personal accounts or devices beyond the authority granted.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on evidence preservation and chain of custody?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 5: Ransomware and Account Compromise
Ransomware incidents may involve encryption, data theft, credential abuse and attempts to disable recovery systems. Initial response should establish scope, isolate affected systems safely, protect backups and engage leadership, legal, privacy, insurers or law enforcement as appropriate. Communication should be factual and coordinated. Payment does not guarantee decryption or deletion of stolen data.
Account compromise may persist through active sessions, app authorisations, forwarding rules, recovery changes and newly registered authentication methods. Responders should review identity logs, revoke sessions and tokens where appropriate, rotate credentials and verify that recovery channels remain controlled. Recovery should include monitoring for repeat access.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on ransomware and account compromise?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 6: Cloud and Hybrid Incident Handling
Cloud investigations depend on provider logs, identity records, resource configuration history and service-specific evidence. Retention may be limited or disabled by default, so logging decisions should be made before an incident. Establish which party can collect each record and how quickly it can be obtained. Preserve snapshots or exports using approved methods and maintain access controls.
Hybrid environments complicate scope because identity, endpoints, cloud services and suppliers are connected. A compromised identity may affect multiple platforms. Build incident playbooks around business services and dependencies rather than treating each technology silo independently.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on cloud and hybrid incident handling?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 7: Business Continuity and Recovery
Recovery restores service to a known-good state and verifies that the threat has been removed. Prioritise services based on business impact, dependencies, recovery objectives and available capacity. Before reconnecting systems, confirm secure configuration, patching, identity integrity, logging and data consistency. Recovery is not complete merely because a server starts.
Business continuity plans address how essential work continues during disruption, including manual workarounds, alternate suppliers and communications. Recovery exercises should test realistic constraints such as missing staff, unavailable identity systems or compromised backups. Record deviations from target recovery times and update plans accordingly.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on business continuity and recovery?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Chapter 8: Communications, Review and Lessons Learned
Incident communication should be accurate, timely, audience-appropriate and coordinated. Internal teams need actionable instructions; customers and partners need relevant facts; regulators or other authorities may require specific notifications depending on applicable law. Avoid speculation, premature attribution and promises that cannot be supported by evidence.
A post-incident review should identify what happened, how it was detected, what decisions were made, what worked and what should change. Focus on system improvements rather than blame. Assign actions, deadlines and verification criteria. Share lessons in a way that protects sensitive evidence and does not expose unnecessary personal information.
Chapter application
Apply the chapter's ideas to a real organisation or a fictional scenario. Identify the assets, people, processes and dependencies involved; state the assumptions you are making; and explain how you would verify that the proposed safeguards work. Keep all testing within systems you own or are explicitly authorised to assess.
Reflection questions
- What are the three most important ideas from this chapter on communications, review and lessons learned?
- Which assumptions would need to be verified before applying this guidance in a real environment?
- What evidence would demonstrate that the proposed controls are operating effectively?
Integrated case study
A finance employee reports that a supplier's bank details were changed after a suspicious email exchange. The organisation should pause the payment if possible, verify details through a known channel, preserve emails and audit logs, notify finance and security leads, assess whether accounts were compromised and document the decisions taken.
Case study analysis
- Identify the important assets, stakeholders and business objectives.
- Describe the likely threat scenarios and the evidence needed to assess them.
- Recommend immediate actions and longer-term preventive improvements.
- Explain how the organisation should document decisions and measure effectiveness.
- Identify privacy, legal, ethical or operational considerations that require specialist review.
Practical activities and assessment
- Run a tabletop exercise using a ransomware scenario and timed injects.
- Complete an evidence-handling worksheet for three fictional artefacts.
- Draft an incident severity matrix and escalation tree.
- Create a recovery checklist for a critical business service.
Suggested assessment rubric
Glossary of key terms
Asset: Something of value to an individual or organisation, including data, services, identities and systems.
Authentication: A process used to establish that a user, device or service is the entity it claims to be.
Confidentiality: Protection against unauthorised disclosure of information.
Control: A safeguard or process intended to modify risk.
Incident: An event that compromises or threatens the security or operation of systems, services or information.
Least privilege: The principle of granting only the access and permissions needed for a defined task.
Residual risk: Risk remaining after controls and treatment decisions are considered.
Resilience: The ability to anticipate, withstand, recover from and adapt to disruption.
Threat: A potential cause of unwanted harm.
Vulnerability: A weakness that could be exploited or otherwise contribute to harm.
Selected standards and further reading
The following are starting points for verification and further study. Confirm the current edition, applicability and licensing conditions before quoting or relying on a standard.
- National Institute of Standards and Technology (NIST). Cybersecurity Framework (CSF) 2.0. NIST, 2024.
- International Organization for Standardization. ISO/IEC 27001, Information security management systems — Requirements. Consult the current edition.
- International Organization for Standardization. ISO/IEC 27002, Information security controls. Consult the current edition.
- International Organization for Standardization. ISO 31000, Risk management — Guidelines. Consult the current edition.
- Center for Internet Security. CIS Critical Security Controls. Consult the current version.
- National Institute of Standards and Technology. NIST Privacy Framework. Consult the current version.
- OWASP Foundation. OWASP Top 10 and other relevant application-security guidance. Consult the current version.
- National Institute of Standards and Technology. Relevant SP 800-series publications on security, privacy, incident response and contingency planning; verify the publication status and current revision.
Editorial development checklist
- Verify every technical claim and update examples to reflect current practice.
- Add properly sourced APA 7 in-text citations throughout the manuscript before publication.
- Review jurisdiction-specific legal and regulatory sections with qualified advisers.
- Add diagrams, figures and accessible alt text where they materially aid understanding.
- Conduct technical peer review and copy-editing; validate all exercises in authorised lab settings.
- Add index, acknowledgements, final copyright details and publisher information when known.