The Stop Rule
A free, source-mapped method for authorized security testing.

The pentest methodology that knows when to stop.

Most writeups cover finding the issue. This one covers the part that makes the work defensible: a written scope gate, stop-at-proof boundaries, and a record a second person can actually check. Read the whole method free — pay only for the fill-in sheets you use during a test.

Read the free method Short reads & posts
Defensive and educational only. No real targets, no working payloads, no jurisdiction-specific legal text.

What the method gives you

Built on public standards

Nothing is proprietary magic. Every card points to a reference you can look up yourself.

NIST SP 800-115
OWASP WSTG / ASVS
MITRE CWE / ATT&CK
FIRST CVSS v4.0

Short reads & posts

The same idea, told in a few different places. Each links back to the free method.

Published DEV Community

The Part of Pentesting Nobody Writes Down: Knowing When to Stop

Read on DEV →

Long read Medium

The Part of Pentesting Nobody Writes Down: Knowing When to Stop

Read the draft →

Newsletter Substack

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

Read the issue →

Discussion Reddit

A free, source-mapped method for keeping an authorized pentest defensible

Read the post →

For teams LinkedIn

A defensible test is one a reviewer can rebuild without you in the room.

Read the post →

Short post X

Can you show where you stopped, and why?

Read the post →

Why this exists

The method is fully public because the point is to be checkable. The paid layer is only the fill-in paperwork people actually use mid-engagement — never the reading. If you spot an unclear step or a stale version, write to 3326175627@qq.com.