# Why we published a testing method that tells you when to stop

*Newsletter: The Stop Rule · Issue 1 · Platform: Substack · Source: Publishing_Kit.md v1.3*

*About the newsletter: A short, practical newsletter on authorized security testing: scope, refusal, stop-at-proof, and writing a record a reviewer can defend. Defensive and educational only, built on public standards. Free to read.*

---

Welcome to the first issue.

Here's a pattern I keep noticing: almost all security-testing writing teaches you how to go deeper — more tools, more techniques, more ways in. Almost none of it teaches you where to stop, let alone how to show in writing that you did.

That gap is why this newsletter exists.

Every week I'll send one short, practical note on four things:

- Scope — deciding what's in and out before you touch anything, and turning down what isn't written down.
- Stop-at-proof — the smallest bit of evidence that shows a finding is real, and why more isn't more defensible.
- The record a reviewer can read — keeping facts, guesses and ruled-out items apart so a second person can check your work.
- Updates — when the public standards move (OWASP, CWE, CVSS), what changed and what's worth a re-read.

None of it is my invention. It maps to frameworks you can look up yourself — NIST SP 800-115, OWASP WSTG/ASVS, MITRE CWE/ATT&CK, FIRST CVSS. And the line I won't cross: defensive, educational use only. No real targets, no working payloads, no legal text for any one country.

The whole method is free and public: https://friendly-skiff-f57.notion.site/ — read it before you subscribe and judge it for yourself.

If you run engagements or teach testing, I'm glad you're here. Reply and tell me: how do you record the "we stopped here" decision today?

See you next week.
