Legal Agreements and Authorization
What you'll learn: How proper legal documentation protects both the penetration tester and the client during security testing operations.
Why Legal Protection is Non-Negotiable
Penetration testing involves activities that could be considered illegal without explicit permission—you're essentially simulating an attack on systems you don't own. Without proper legal authorization, you could face criminal prosecution, even if your intentions were good. Think of it like entering someone's house to test their locks: without written permission, you're breaking and entering.
Core Legal Documents
Written Authorization Contract
This is your primary permission document. It must clearly state:
- Who is authorized to test (specific individuals or team)
- What systems are in scope (based on your scoping work)
- When testing will occur (dates and timeframes)
- How testing will be conducted (methods permitted)
Non-Disclosure Agreements (NDAs)
NDAs protect sensitive information discovered during testing. You'll see:
- Client confidential data (business information, vulnerabilities)
- Security findings that could harm the organization if leaked
- System architecture details
- Duration of confidentiality obligations (often 2-5 years)
Safe Harbor Agreements
These clauses protect you from legal action if something goes wrong despite following the agreed rules. They acknowledge that security testing carries inherent risks and the client accepts responsibility for potential disruptions within scope.
The Golden Rule
Never begin testing without signed contracts in hand. No verbal agreements, no implied permissions, no exceptions. If legal disputes arise, your signed authorization is your shield.
Key Takeaway: Written authorization through contracts, NDAs, and safe harbor agreements transforms potentially criminal activity into legitimate security work—without these documents, you have no legal protection, regardless of your good intentions.