Sats Coop catalog

Linux incident response (first hour)

Suspect a compromised server? Do these in order. Authorised use on systems you own or administer only.

Free excerpt

1. Do not reboot or wipe

Memory and running processes are evidence. Write down the time (UTC), who noticed what, and every command you run.

2. Isolate, do not power off

Cut network access with a firewall rule or security group but keep the machine running; leave one admin path open from a known IP.

3. Capture volatile state

date -u; uptime; w; last -aF | head -30; ps auxwwf; ss -tulpna – save the output to another machine, not the suspect disk.

4. Hunt persistence

Check crontab -l for each user, /etc/cron.*, systemctl list-timers --all, every ~/.ssh/authorized_keys, /etc/ld.so.preload, new SUID files and find / -xdev -mtime -3 -type f.

5. Snapshot, then decide

Take a disk or VM snapshot before cleaning. Rotate secrets only from a clean machine, after containment. Decide: rebuild from known-good (usually right) or clean in place.

The paid runbook turns this into a 60-minute plan with scripts and templates.

Get the full pack

Sats Werkstatt