Scope record
Each proposed engagement begins with an explicit record of permitted hosts, repositories, credentials, test identities, time windows, data-handling constraints, and excluded actions.
- Written authorization before execution
- Allowlisted targets and explicit exclusions
- Named escalation path for unexpected impact
Evidence workspace
A finding should explain the trust boundary, affected component, preconditions, observed behavior, impact, and a reproducible path—not just attach a severity label.
- Evidence separated from model interpretation
- Fictional demonstrations clearly labeled
- Human review before delivery
Remediation loop
Proposed guidance connects the root cause to a practical control change. A scoped retest then checks the reported path without implying that the entire system is defect-free.
- Root-cause context
- Fix guidance with trade-offs
- Point-in-time verification