HomeProcess

Process

Scope. Build. Break. Fix. Four stages, each with something you can hold at the end of it.

  1. Scope

    We agree what gets built, what gets tested, and what is off limits.

    Output: scope document

  2. Build

    Short cycles and working software at every step.

    Output: deployed release

  3. Break

    We attack it like an outsider would, inside the agreed scope.

    Output: findings report

  4. Fix

    Every finding ships with a fix and a retest.

    Output: retest results

Scope

We agree what gets built, what gets tested, and what is off limits. In writing, before any work starts.

You bring

  • Your goals and deadline
  • Access to the people who decide
  • For testing: proof you own the target

We deliver

  • Scope document
  • Timeline and quote

Build

Short cycles, working software at every step, and code you can read. You see progress on a real URL, not in slides.

You bring

  • Content and brand assets
  • Feedback on each cycle

We deliver

  • A staging URL from the first week of build
  • The repository, updated daily

Break

We attack it like an outsider would, with your permission and inside the agreed scope. Every lead is reproduced by hand before it is reported.

You bring

  • A test window
  • Test accounts for each role

We deliver

  • Findings report
  • A call to walk through it

Fix

Every finding ships with a fix and a retest, so the report ends with closed issues instead of a to-do list.

You bring

  • Review of our pull requests, or your own fixes

We deliver

  • Retest results
  • Updated report with final status

Rules of engagement for testing.

These apply to every security test we run.

01

Written authorisation

No testing starts without written permission from the owner of the system.

02

Inside the scope

Hosts, accounts and techniques are listed up front. Anything else is out.

03

Nothing destructive by default

Tests that could affect availability or data are agreed first, or run on staging.

04

Your data stays yours

We access only what is needed to prove a finding, and report it only to you.

Got something to build, or something to break?

Tell us what it is. A few lines are enough to start.