Written authorization first.Ownership, assets, allowed techniques, data handling, timing, observers, and stop conditions are agreed before testing.
Minimize real-world impact.Use isolated targets and synthetic data where possible. Collect only the evidence required to prove and repair the flaw.
Disclose for remediation.Coordinate with the owner, protect sensitive details, and give the patch a fair path before public technical discussion.
Evidence over theatre.Separate observed behavior from inference. Preserve the trigger, environment, prerequisites, and limits of every conclusion.
Repair belongs in scope.A report is not the end state. We connect the exploit to code, configuration, identity, monitoring, and a repeatable verification step.
No silent expansion.Finding a new path does not expand permission. Testing pauses at the boundary until the owner explicitly changes the scope.