Program Scope and Rules of Engagement
What you'll learn: How bug bounty programs define exactly what researchers can and cannot test, and the legal boundaries that keep everyone safe.
Why Scope Matters
Think of scope as drawing a fence around a playground. Researchers need to know which equipment they can test for safety issues, which areas are off-limits (maybe construction zones), and what testing methods won't get them kicked out. Without clear boundaries, even well-intentioned security work can cause harm or legal trouble.
Defining In-Scope Assets
In-scope assets are the specific systems, domains, and applications researchers are authorized to test. This might include:
- Specific domains like
*.example.combut excludinginternal.example.com - Web applications, APIs, and mobile apps with version numbers
- Public-facing infrastructure but not third-party integrations
Programs typically list these explicitly: "Test our main site and Android app, but not our payment processor."
Out-of-Scope Targets
Out-of-scope targets are systems researchers must not touch—even if vulnerabilities exist there. Common exclusions include third-party services, physical security, social engineering, or customer data environments. Violating these boundaries can terminate participation and invite legal action.
Allowed Testing Methods and Safe Harbor
Rules of engagement specify what testers can do: automated scanning limits, prohibited DoS attacks, data access boundaries, and authentication requirements. For example: "You may create test accounts, but don't access other users' data."
Safe harbor policies provide legal protection for researchers who follow the rules. They promise the organization won't pursue legal action for good-faith testing within scope—essentially a "we won't sue you" guarantee when you're helping, not harming.
Legal Protection
These policies protect both parties. Researchers get assurance they won't face prosecution under computer fraud laws. Organizations get controlled, responsible testing instead of uncoordinated probing that might cross ethical or legal lines.
Key Takeaway: Clear scope, rules of engagement, and safe harbor policies create the legal and technical boundaries that enable researchers to hunt for vulnerabilities safely while protecting both the organization and the tester from unintended harm or liability.