Scope & threat model
Confirm repositories, deployed addresses, roles, dependencies, business-critical invariants and review boundaries.
Architecture & manual review
Trace key execution paths and inspect trust boundaries, privileged actions, external calls and protocol assumptions.
Testing & validation
Use targeted tests and available analysis tools to validate suspected issues and explore relevant edge cases.
Findings & severity
Document issue description, impact, affected components, reproduction context and recommended mitigation.
Remediation review
Where included in scope, inspect fixes and report whether findings are fixed, partially fixed, acknowledged or unresolved.
Final report
Deliver scope, methodology, limitations, findings summary and retest notes. Public disclosure requires client agreement.
Risk should be explainable.
Severity is assigned using impact, exploitability, preconditions and affected assets. Labels alone are not a guarantee of safety.
Material loss or control
Issues that may enable major asset loss, unauthorized control or severe protocol disruption.
Meaningful constraint
Issues with material but more limited impact, conditions or affected scope.
Hardening & observations
Lower-impact weaknesses, configuration concerns or recommendations for defense in depth.