logo
Defence blues
Responding to active impact
  • Red tradecraft
  • Privacy greenhouse
  • Purple crossroads
  • Indigo observatory
  • Contact
Initializing search
    • Blue team @Home
    • Servers without a security team
    • Honeytech for humans
    • Blue team for dev
    • OT and ICS security
    • Counter moves
      • Closing the doors just walked through
      • The machine at the point of impact
      • Traffic patterns as evidence
      • The surface designed to be accessible
      • The application layer as a target
      • Infrastructure you defend but do not own
      • Where the container meets the host
      • Systems that were never meant to be networked
      • The domain as an attack graph
      • The gap between access and authority
      • Harvesting stored secrets
      • Surviving the reboot
      • From target to target
      • Plausibility as cover
      • Memory corruption and its limits
      • Watching data being gathered
      • Watching the exits
      • Limiting the blast radius
        • Impact: defender context
        • Responding to impact events
        • Responding to active impact
          • Impact response runbook
          • Ransomware response playbook (NGO, 20 staff)
        • Responding to active impact
          • Impact response runbook
          • Ransomware response playbook (NGO, 20 staff)
      • Operational cost of security controls
    • Golem Trust Computing Ltd.
    • Department of Silent Stability
    • The Home for Bewildered Beasts of Legend
    • Archive

    Responding to active impactΒΆ

    Runbooks for responding to active impact events, covering ransomware, destructive attacks, and service disruption scenarios.

    • Impact response runbook
    • Ransomware response playbook (NGO, 20 staff)
    2026-05-27 11:27
    © Copyright 2026, TyMyrddin.
    Created using Sphinx 7.2.6. and Sphinx-Immaterial

    Made with love in the Unseen University, 2026, with a forest garden fostered by /ut7