RUN.01 — Pentest

Pentest engagements that survive client legal review.

A SecHive pentest produces evidence the client's security team can hand to engineering and the consultancy's QA can hand to legal. No transcript hunting required.

What you get

  • Scope policy file checked into the run, gating every action.
  • Per-finding evidence chain: signed payload, runtime receipt, side-effect delta, source reference.
  • Reviewer disposition stamped with operator identity.
  • Deterministic replay.sh per finding.
  • Mode-aware report (executive + technical) with redaction manifest.
  • Cosigned attestation for the report bundle.

Engagement shape

  • Discovery: SecHive loads the scope and inventories the surface.
  • Hypothesis: HypothesisGraph builds candidate weakness list.
  • Validation: Benign PoCs run under scope guard.
  • Operator review: findings triaged in mission control.
  • Reporting: deliverable rendered with proof pack attached.
  • Retest: rerun the same proof pack post-fix.