The audit-upgrade cycle
Every engagement runs as one persistent cycle document. Findings are numbered, each carries its evidence, and none is closed until a re-check passes on your live system.
- 01
Orient
We agree the scope in writing, you grant the least access the modules need, and the cycle document opens with its scope and method.
- 02
Audit
Each module in scope runs its checks. Every finding is recorded with the evidence it rests on and a planned fix.
- 03
Report
We review the draft ourselves before you see it. You receive it in your portal and as a PDF.
- 04
Fix
In severity order: a failing check, the fix, the passing check. Every change names the finding it fixes.
- 05
Verify
The module's re-check runs against your live system. A finding is verified only on a passing re-check after the fix.
- 06
Close
The final report lists what was done, what comes next, and what we need from you. Our access is removed.
- 07
Monitor
Verified checks become your regression suite, run on every change.
Timeline
Day 0
Payment. The cycle document opens; passive modules start the same day.
When you sign
Scope letter signed and least access granted; scoped modules start.
By the promised date
Your reviewed report, in the portal and as a PDF.
Within 30 days
Sign a fix sprint and the audit fee is credited in full.
After the fixes
Live re-checks, then the final report and access removed.
What we need from you
Passive modules (WEB, SEC, A11Y, PRIV, PERF, SEO) look only at what any visitor can see and need no access.
Scoped modules (APP, CODE, CLOUD, AI) run only after someone with authority over each system signs a scope letter naming the targets, the techniques and the time window. We ask for a deploy key, an app installation or a read-only role, never a personal password or personal access token.
What we never do
- Get around a bot wall, CAPTCHA, rate limit, paywall or login, on anyone.
- Run any test beyond a normal visitor's page load without a signed scope letter.
- State legal conclusions or certify compliance (SOC 2, PCI, HIPAA). We report against frameworks and cite the rule.
- Name a client or show their findings publicly without written permission.
Rules we hold ourselves to
- No finding without evidence
- A finding cannot be saved without at least one evidence record: a request, a header, a screenshot, a line of code.
- Fixed means a linked change
- A finding moves to fixed only with a change that names it, and to verified only after a passing re-check.
- No legal conclusions
- Where a finding touches a rule, we cite the rule and ask you to confirm with your counsel.
- Access ends with the cycle
- A cycle cannot close until every access grant you gave us is recorded as removed.
- We pass our own checks
- Our marketing pages load nothing from another company. The only exception is Cloudflare's bot check on the request forms (free tools, the sample and checkout). Our own scanner checks the site before every release.