Fixed scope. Fixed price. A signed report and an attestation letter in 10 business days — or every quarter, automatically, for NIS2, DORA and ISO 27001 files.
Your auditor, insurer or enterprise customer does not want a scanner subscription. They want a dated document naming what was tested, what was found, and what was fixed.
Scope, method, executive summary, every finding with evidence, CVSS 4.0, CWE/OWASP mapping and the exact remediation step. Written for two readers: the CFO reads page one, the engineer reads the rest.
A one-page letter stating what was tested, when, by whom, and the outcome — addressed to a named third party on request. This is the document that clears the questionnaire.
After you fix, we retest the same findings and issue a closure addendum. Proof of remediation is what turns a finding list into an audit artefact.
Pick the depth your auditor, insurer or enterprise customer requires. Every scope includes the report, the attestation letter and one retest of remediated findings.
Public applications, exposed services, TLS and email authentication. The scope an insurer usually asks for first.
Access control, IDOR, sessions, business logic and API testing with the roles we agree on. The scope most customer questionnaires expect.
Code review, CI/CD and secrets, cloud configuration, dependency analysis — plus the NIS2/DORA/ISO control mapping appendix.
Prices are on the pricing page — every tier is fixed, so there is no quote to negotiate.
You sign a short authorization: domains, IPs, dates, test window. Nothing is scanned before it is signed.
Passive collection first, then active testing inside the agreed scope, rate-limited and logged.
Findings are triaged, false positives removed, rated with CVSS 4.0 and mapped to OWASP/CWE.
You receive the PDF and the attestation letter. After you fix, one retest closes the findings.
Honest boundaries are part of the deliverable — an auditor will ask, and the report says it on page one.
Public web applications and APIs, external network services, TLS and cipher configuration, email authentication, exposed administration interfaces, session and access-control weaknesses, business-logic abuse, known CVEs for detected versions.
Denial of service, social engineering against staff, physical access, third-party SaaS vendors, mobile binaries, remediation implementation. Each can be added by written agreement.
Evidence is stored encrypted, access is limited to the tester assigned to your engagement, and raw evidence is deleted 12 months after report delivery unless you ask us to keep it.
A redacted report from a fictional 40-person company: the executive summary, two findings at different severities, and the attestation letter. No email required.
No. You receive an attestation of testing performed, not a certificate of compliance. Certification is issued by accredited bodies; our report and letter are the evidence they and your auditor ask for.
Fixed scope and a standard report template remove the discovery phase, the account manager and the custom deck. You pay for testing and evidence, not for meetings.
Only for the white-box tier, and only read access to the listed repositories. Grey box needs an account with the roles we agree on. Black box needs nothing.
You still get the report and the attestation — a clean result is exactly what an auditor wants to see. The document states the scope and dates so the absence of findings is meaningful.
A named tester, stated in the report and the attestation letter, with the tools and methodology documented in the appendix.
Subscriptions can be cancelled at any time and stop at the end of the paid period. One-off reports are refundable within 30 days, unconditionally, before delivery of the final report.
Scope in one call, report in ten business days. Start with the black-box report if you are unsure.