Network Hacking: Safe Engagement Practices
The fastest way to lose a client is taking down payroll on a Tuesday. Safe engagement practices aren't bureaucracy—they're how you get invited back.
Assume every action is logged and every subnet has something fragile.
Safe engagement is also about emotional safety—clear stop conditions mean testers don't hesitate to call the client when something feels wrong mid-test.
Before you start
Written ROE: ranges, forbidden techniques, hours, contacts, and deconfliction with blue team if they're running detections.
Confirm backup and rollback for anything that modifies systems—not just exploits.
During testing
Rate-limit scans. Avoid default cred spraying at scale unless explicitly approved. Pause when IDS calls start.
Use a comms channel for 'heads up' messages
Snapshot critical findings before deeper pivots
Never test out-of-scope IPs 'just to see'
When things go sideways
Stop, notify, document. Honesty beats hiding a outage.
Professionalism on the wire matters as much as skill.
If it's not in the ROE, don't run it—even if the tool has a cool flag.
Debrief outages even if unrelated—transparency when something broke nearby prevents you becoming the default suspect.
Small habits compound—what feels like overhead early becomes speed when deadlines hit.
Keep ROE PDFs offline on your phone—VPN failures shouldn't stop you verifying limits.
After-action reviews
Debrief with blue team when allowed—your stealth success is their detection gap, framed politely.
Write a personal lessons-learned even on smooth tests—outages teach more than wins.
Insurance and contracts
Understand liability clauses before aggressive tests—some contracts cap certain techniques entirely.
Keep emergency numbers in phone favorites, not buried in PDF ROE.
Post-engagement wash-up includes restoring any test accounts or scheduled tasks you created.
Worth reading next
Essential Steps in Network Penetration Testing Methodology
Network Hacking: Host Discovery for Authorized Scopes
Essential Commands for Linux and Windows: A Quick Reference Guide
Comments