Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 38 ยท Getting Started

Legal and Ethical Testing

Understand authorisation, scope and rules of engagement before you open Burp Suite. Learn safe practice targets and how to stay inside the law.

Security testing looks the same, technically, whether it is a professional assessment or a crime. The only difference is permission. Sending a modified request to a website you do not own can break computer-misuse laws in many countries even if you meant no harm, even if you only "looked around", and even if the site turned out to be badly protected.

So before any tool lesson, this one sets the ground rules. They protect the people who use the target, the organisation that owns it, and you.

Never test a system without clear, written permission from someone who has the authority to give it. "It was easy to get in" and "I was going to report it" are not defences. If you are unsure, stop and ask.

Authorisation comes first

A proper engagement starts with a written agreement. Whatever it is called (statement of work, authorisation letter, test agreement), it should state:

  • Who is allowed to test, and on whose behalf.
  • What is in scope: exact hostnames, applications, API paths, environments.
  • What is out of scope: third-party services, production databases, other customers' data.
  • When testing may happen (dates and time windows).
  • How: which techniques are allowed, whether denial-of-service style load is forbidden, whether real user accounts may be touched.
  • Contacts: who to call immediately if something breaks or you find something severe.

This agreement is often called the rules of engagement. Burp's own features mirror it: the target scope lets you tell Burp exactly which hosts it may act on, so a slip of the mouse does not wander onto a site you were never cleared to test.

Scope is a hard line

Imagine the agreement covers app.example.test but not payments.thirdparty.test, which the app calls during checkout. If your proxy captures a request to the payment provider, you may see it, but you must not attack it. Third parties never agreed to be tested, and your client cannot grant permission on their behalf.

Many cloud providers publish their own testing policies (what you may do against your own account's resources). Read them: some allow scanning of your own instances, some forbid certain load tests.

Safe places to practise

You cannot learn by testing random websites, so build a legal practice setup:

  • Your own lab. Run intentionally vulnerable applications on your own machine or a private virtual network. Popular open-source training apps (such as OWASP Juice Shop or DVWA) are built for this. Keep them off the public internet.
  • Purpose-built online labs. Some training sites explicitly invite testing with Burp on their lab environments, and publish the terms. Stay inside the rules they publish.
  • Bug bounty programmes. Programmes publish scope, allowed techniques and reporting channels. Read the whole policy for each programme, because they differ and are updated.
  • Your employer's systems, with written approval from the system owner and, where needed, your security team.

Handling data responsibly

Real applications hold personal information. Even in an authorised test you may stumble on customer records.

  • Minimise. Prove the issue with the least data possible. One record is enough to demonstrate an access-control flaw; downloading a table is not.
  • Do not keep what you do not need. Burp project files contain full request history, including cookies and passwords you typed. Treat them as sensitive, encrypt storage, and delete them when the engagement ends, as your agreement requires.
  • Do not share captured credentials or tokens in chat, tickets or screenshots. Redact them.
  • Report, do not exploit. Show that a weakness exists; do not use it to read private data, change records or pivot into other systems unless the agreement explicitly allows it.

Disclosure

If you find a problem, tell the owner through an agreed channel, give enough detail to reproduce it, and give them reasonable time to fix it before any public discussion. A reporting chapter comes later in the Burp Suite track; for now remember that the goal is a safer system.

Try it: a rules-of-engagement checker

This stand-in models a tiny authorisation gate. Given a list of in-scope hosts and a time window, it decides whether a proposed action is permitted. Real engagements are far richer, but the habit it teaches is exactly right: check first, act second.

Python Stand-in: check an action against the agreement

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Try it: redacting secrets before you share evidence

Reports and screenshots often contain tokens. This stand-in masks sensitive header and body values in a captured request so it is safe to paste into a ticket.

Python Stand-in: redact secrets in evidence

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

A short ethics checklist

  1. Do I have written permission from someone with authority?
  2. Is every host I touch inside the written scope?
  3. Is this inside the agreed time window and technique list?
  4. Am I using the minimum data and impact to prove the point?
  5. Do I know whom to call if something breaks?

If any answer is "no", pause. A professional is defined less by skill than by restraint.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What separates a legal security test from an illegal intrusion?

    Technique is the same either way. Permission from the system owner, ideally written, is what makes a test lawful and ethical.
  2. 2. During an authorised test you notice the app calls a payment provider that is not in your scope. What should you do?

    Scope is a hard line. Out-of-scope third parties must be left alone, though you may report that the integration exists.
  3. 3. Which is the safest place to practise with Burp Suite?

    Your own lab, or an online lab that publishes terms inviting testing, gives you legal targets to learn on.
  4. 4. Why should Burp project files be handled carefully?

    A saved project can hold real credentials and personal data. Encrypt, limit access and delete it when the agreement says to.

Summary

  • Permission, not technique, makes testing lawful; get written authorisation first.
  • Rules of engagement define who, what, when, how and whom to contact.
  • Stay strictly in scope, including time windows and forbidden techniques.
  • Practise only on your own labs, published training sites and programmes whose terms you follow.
  • Minimise data, protect and delete evidence, and report responsibly.

Next: Burp editions and tools tour