Paid work
Security services with published starting prices
Three packages, priced from a floor rather than hidden behind a quote form. The scope is agreed in writing before any testing starts, and nothing outside that scope is touched.
1. Web and API Security Assessment
from $500
| Scope | An agreed list of targets, confirmed in writing before work starts. |
|---|---|
| Coverage | OWASP Top 10 and OWASP API Top 10, with emphasis on authorization and cross-tenant flaws, broken authentication and session handling, injection, and rate limiting. |
| Duration | Five business days. |
| Deliverable | A findings report with impact, reproduction steps and remediation guidance for each finding, plus a retest of critical findings. |
| Boundaries | No testing outside the agreed scope. Scope guards refuse private, loopback and link-local targets by default. |
2. Secure Code Review and Threat Modelling
from $300
| Scope | Up to two pull requests, or one service. |
|---|---|
| Focus | Access control, session handling, input validation and injection paths, with a short threat model of the changed surface. |
| Duration | Three business days. |
| Deliverable | Inline findings with severity and concrete fix suggestions, plus a written summary of the threat model. |
3. Security Automation Build
from $800
| Scope | One small CI-friendly tool for your stack: scanner triage, a dependency gate, log normalisation, or detection-rule linting. |
|---|---|
| Duration | Two to three weeks. |
| Deliverable | A repository with a test suite, a CI pipeline and documentation, delivered with a working demo and a clean run. |
Also available, quoted on scope
- Detection-rule review and coverage analysis.
- Cloud IAM and permission review.
- Post-quantum migration-readiness inventory.
How an engagement runs
- Scoping. You send the targets or the diff. I confirm what is in scope and what is out, in writing.
- Authorization. Written confirmation that you own the targets or are authorized to test them. Testing does not begin before that exists.
- Execution. Read the code path first, reproduce with the smallest possible proof, and stay inside the scope list.
- Reporting. Findings with impact, reproduction steps and remediation guidance, structured so engineering teams can route them without re-formatting.
- Retest. Critical findings are retested after fixes land.
Frequently asked
Do you need a signed agreement?
A written scope and authorization statement is required. A full services agreement is fine too, and confidentiality terms can be included without changing the price.
Will you test production?
Only with explicit written authorization naming the production targets, and only within the agreed scope. Rate limits and safety guards are configurable.
What if the scope changes mid-engagement?
Additional targets are quoted before they are touched. The published starting prices apply to the scope described on this page.
Do you work remotely?
Yes. Engagements are run remotely for clients in any location, with a short scoping call to confirm the target list and constraints.