l1ackers
Not marked. Sign in and it follows you. Next: 046: When you find something real

~/tutorials/045-rules-of-engagement.md

045: Rules of engagement

The lesson before this one was the report. This one is the paper that makes all of it lawful, and it is a technical lesson in disguise, because scope is where real engagements are actually lost.

The letter

An authorization to test is a short document with specific sentences in it. What systems, by address and by name. What windows of time. What classes of testing are allowed and which are excluded. Who signs, with a title that binds the company, and a phone number for the emergencies.

You read it before you accept the work, line by line, and the reading is technical. Systems by address means you resolve every name and check the addresses against what you believe the scope is. Exclusions mean your scanner is configured to skip them, not that you remember to. The letter is not a feeling of permission. It is an interface, and you configure against it.

Where there is no letter, there is no test. A verbal yes from an administrator is not a yes from the company. A screenshot of a conversation is not a signature. This is not caution. It is the difference between a career and a felony, drawn in one document.

Reading one, line by line

The fastest way to learn the letter is to read one the way you will read it on a job. The published policy of a bug bounty program is the same document with the money sentence removed, and the vocabulary never changes. Here is the reading discipline, six lines, each line a question you bring to the page.

Scope by name. Every asset listed, resolved. If the policy names a wildcard like *.example.com, the reading question is what that wildcard actually covers, and the answer is a resolver, not an opinion. Subdomains that do not resolve are not in scope no matter what the wildcard implies, and a host that resolves to a third party's address is the third party section, next.

Third party gear. The cloud the site lives on, the CDN in front of it, the provider's router. Their boxes are not the client's to authorize, and a real policy says so in a sentence. When you find one of their addresses inside a scope range, you stop at the boundary and write the boundary down.

Exclusions. The inverse scope. Systems named as out of bounds inside an in-bounds range, and the reading question is which of your tools needs configuring so the exclusion is enforced by the machine and not by your memory.

Test windows and rates. When you may test, and how hard. A policy that says no automated scanning is a policy that bans your scanner and permits your hands, and knowing which side of that line each of your tools sits on is the whole game. Rate limits are the same discipline one rung gentler.

Safe harbor. The sentence that says if you stay inside the rules, they will not pursue you for the incidental damage honest testing causes. Its absence is a fact about the program, not a detail. Some programs offer none.

The clocks. Report windows, fix windows, publication windows. Lesson 046 lives entirely inside this line, and the policy is where the numbers come from.

That reading, done once on a published policy, teaches more than any summary of one. The Try it sends you to a directory of them.

The questions that come up anyway

Somebody asks you to look at something adjacent. The answer is a new line in the letter or a no. Scope does not stretch verbally.

You find something serious outside scope in the data you lawfully collected. You stop touching it, document that you saw it, and report it in the finding that says: seen, not pursued, outside scope. Clients respect that sentence. It is the mark of somebody they can hire again.

A third party's equipment appears inside the client's address space. Cloud tenants, hosted services, a provider's router. Their box is not your client's to authorize. The letter's job was to tell you this before you scanned it.

The three questions have one shape: the moment you notice something outside the paper, the testing stops being the question. The paper is the question, and the answer is always written, never improvised.

The habit, before anybody pays you

Start now, in the lab. Write the authorization for your own exercises: what networks exist, what the rules are, when you tear it down. The letter you write for your own lab is the same document you will read on a job, wearing both chairs at once, and writing it teaches the shape faster than reading ten.

Machines state their rules in files, and this one's is public and short:

cat ~/robots.txt

A policy in plain lines: what is welcome, and what to be gentle with. Other machines state theirs elsewhere, and asking is cheap:

$ dig +short l1ackers.com

That one runs on your box. The shell below it has one zone and says why, and the shape of that refusal is the shape of every policy you will ever read: what it will not do, why, and what to do instead.

Try it

  1. Read a real authorization letter, with the six-line discipline above. Bug bounty directories publish hundreds, and the vocabulary is the same vocabulary. Take one policy and write the six answers in six sentences.
  2. Draft the letter for your own lab, from the reveal below as a starting shape. Addresses, rules, teardown. Change it to match what you actually run, because a letter that does not describe the real lab protects nobody.
  3. Run your next lab session strictly inside it. The muscle you are building is stopping, and it only trains by stopping with something you wanted to do. The one violation to engineer deliberately: point a tool at something just outside your own letter, watch yourself stop, and write the stop down.
Reveal the answer

The lab letter, whole, the shape to steal. This one is written for the two machine VirtualBox lab from lesson 031, host-only network, and every blank is a decision the drafter makes on purpose:

AUTHORIZATION TO TEST, LAB 1

Signed by: (the person who owns the machines)
Title: owner, sole operator
Contact: (a phone number that answers during test windows)
Valid from 2026-10-01 to 2026-10-31, weekdays 19:00-22:00 local.

IN SCOPE
  192.168.56.0/24, the host-only network built in lesson 031, and every
  machine attached to it during a test window:
  - the attacker box, 192.168.56.101, the Ubuntu guest
  - the target box, 192.168.56.102, Metasploitable 2 or Juice Shop guest
  Host addresses confirmed against the hypervisor's DHCP leases before
  every window, because a lease that moved is a different machine.

TESTING PERMITTED
  Port scanning, service enumeration, exploitation of the named target,
  credential attacks against lab accounts only, privilege escalation on
  the target guest.

EXCLUDED
  The host machine and its physical network. The router, the internet,
  and every address not listed above. Denial of service of any kind,
  including accidental: no floods, no resource exhaustion, nothing that
  would crash the target rather than enter it.

RULES OF HANDLING
  Loot stays inside the lab network. Findings go in the report shape of
  lesson 044. Nothing leaves the hypervisor.

TEARDOWN
  After every window: both guests powered off, the host-only network
  left as built, and snapshots restored to the lesson 031 baseline.
  Teardown is part of the window, not an afterthought.

BREACH PROCEDURE
  If a test touches anything outside the scope list, the window ends
  immediately, the event is written down with timestamps, and the letter
  is amended before the next window opens.

Read it back and notice what every section is doing. The scope list is addresses, not feelings, with a resolution step built in, the same discipline the six-line reading taught. The exclusions name the accident the operator is most likely to have, the denial of service that scanning tools can cause without being asked to. Rules of handling is the line that keeps lab data from leaking into a real person's password reuse. The teardown clause is why the lab stays reproducible, and the breach procedure is the muscle from the Try it, pre-written, so that the day something goes wrong the paper already says what happens instead of you inventing it under stress.

One more line professional letters carry that lab letters do not need yet, and knowing the difference is the point: insurance and liability, who pays if the house burns down. When the day comes that somebody else signs your letter, read that section twice and ask one question about it, because it is the one section of the document with your name in it instead of theirs.

Then the tier's last lesson, which is what happens when the paper exists and something real answers anyway.

Not marked. Sign in and it follows you. Next: 046: When you find something real
l1ackers · shell this is a way in, not a requirement
$