Scoping In-Scope vs Out-of-Scope Assets
What you'll learn: How to clearly define which systems, networks, and applications are authorized for testing while explicitly marking off-limits resources to avoid legal trouble and operational disruption.
The Core Idea
After defining your Rules of Engagement, the next critical step is scoping — creating an explicit, detailed list of what you can test (in-scope) and what you absolutely cannot touch (out-of-scope). This isn't just a formality; it's a legal contract that protects both you and the organization.
Think of it like a construction zone: workers need clearly marked boundaries showing where they can dig and where critical utilities lie underground. Cross those lines, and you risk hitting a gas main.
In-Scope Assets
These are your authorized targets:
- Specific IP ranges (e.g., 192.168.10.0/24)
- Domain names and subdomains (e.g., app.example.com, but NOT mail.example.com)
- Web applications by URL
- Specific cloud resources identified by name or tag
- Network segments or VLANs
- Mobile applications with version numbers
Out-of-Scope Assets
These are strictly forbidden:
- Production payment systems (avoid business disruption)
- Third-party services you don't own
- Physical security systems (locks, cameras)
- Systems in other countries (jurisdiction issues)
- Personal employee devices
- Systems hosting protected data (medical, financial)
Why It Matters
Ambiguity kills penetration tests. "Test our web apps" isn't enough — which environments? Which domains? A single miscommunication can lead to testing a customer-facing production database, causing an outage, or worse, testing a third-party vendor's system and facing legal action.
Always get scope in writing, with explicit IP addresses, URLs, and exclusions. When in doubt, ask before testing.
Key Takeaway: Proper scoping creates a legally protected sandbox for your testing activities — be exhaustively specific about what's in and what's out, because one wrong move outside scope can end your engagement and your career.