Labs / Defensive Tools
Road 22 of 33
Defensive Tools
The blue team's working kit: first follow one record at rest, in transit and in use to see what there is to guard, then name known-bad files with signatures, detonate the unknown in a sandbox, read endpoint and network telemetry, block attacks on the host and inline on the wire, keep data from leaving, and catch an intruder with traps.
Start this roadKnow the data: where a record sits, travels and works
Follow one record through three states and four protections.
Detect and analyse: signatures, sandbox, telemetry and decoys
Name known-bad files, detonate the unknown, read telemetry, set traps.
- 01 Malware signatures: catching a known-bad file by its bytes Flag a known-bad file with a YARA rule and a ClamAV signature, then meet the limit signatures cannot cross.
- 02 Malware sandboxing: detonate it and watch what it does Run an unknown sample under strace on an isolated machine and read the behaviour no signature could name.
- 03 EDR telemetry: the endpoint tells on the intruder Query a host's own live state with osquery and find a backdoor the network never saw.
- 04 Writing a NIDS signature, and tuning out the false alarm Write a Suricata rule for your own network, load it live, and tune away its false positive.
- 05 Honey-traps: decoys that only a snooper trips Set a decoy host and a canary token nobody legitimate touches, and catch the one who does.
Block and contain: the host, the wire and the data
Stop attacks on the host, inline on the wire, at the data.
- 01 Host intrusion prevention: the server bans its attacker Watch fail2ban read the auth log and block a password-guessing attacker at the host's own firewall.
- 02 Inline IPS: the gateway drops, not only watches Put Suricata on the forwarding path through NFQUEUE, then block a flagged request while the floor keeps browsing.
- 03 Data-leak controls: catching a secret on its way out Match a confidential marker in forwarded traffic, watch it, block it, and see why HTTPS hides it.