How a Budget Security pentest works
A Budget Security pentest runs in four stages: asset registration, scoping in tester-days, manual testing by OSCP-certified testers, and delivery in the Budget Security platform. You register your assets once. Each asset is scoped into tester-days, so you see the price before you book, and your account manager confirms the scope, usually within 24 hours. Testing is done by hand by a network of 40 OSCP-certified testers following OWASP, NIST SP 800-115, and CIS-aligned standards. The test starts within 7 days of booking, the report follows within 48 hours after testing ends, and you pay after the report is delivered.
Asset registration
Before the first test, you register the assets you want tested: web applications, APIs (REST, GraphQL, SOAP), mobile apps (iOS and Android), and external and internal networks. Cloud tests are arranged with your account manager.
For each asset, the platform keeps what the tester needs:
- Asset type (web app, API, mobile app, external or internal network)
- URL, API specification, app store link, or IP range
- Test approach: black box, grey box, or white box, depending on the asset
- Test accounts and credentials, stored encrypted
Assets stay in your account. The next test of the same application starts from the same record, so there is no re-scoping from scratch.
Scoping in tester-days
Every asset is scoped into tester-days. How that happens depends on the asset:
- Web applications: scoped automatically from a crawl of the application, or through a short scoping call
- APIs: from an OpenAPI specification you upload, from manual inputs, or through a call
- Mobile apps: from the app store link or developer access
- External networks: from your list of IP addresses
- Internal networks: tested remotely from a test device placed on your network
Your account manager confirms the scope, usually within 24 hours. You then see the number of tester-days and the price, and when you book you can adjust the days up or down. If the scope changes later, re-scoping is one click or a message to your account manager.
Why scoping in tester-days beats sales-call scoping
Traditional pentest consultancies scope engagements during a sales call. A senior consultant talks to the customer, asks about the asset, and produces an estimate. This estimate is subject to:
- Estimation drift: different consultants produce different scopes for the same asset
- Over-scoping: consultancies have a commercial incentive to scope larger, and there is no transparency mechanism for the customer
- Under-scoping: when budget is the customer's stated constraint, consultancies sometimes accept a scope that cannot meet the customer's actual compliance goal
- Opacity: the customer rarely sees what coverage they are trading away
Scoping in tester-days makes the cost of coverage visible before you commit. You see what you are buying, at a published day rate: $985 per tester-day for US clients (€849 per day for EU clients).
OSCP-certified testing
Every test is carried out by an Offensive Security Certified Professional (OSCP) tester from our network of 40. OSCP is the practical, hands-on penetration testing certification: candidates must demonstrate real exploitation against live targets in a 24-hour exam, not pass a multiple-choice theory test.
Testing follows industry-standard methodologies adapted per test type:
| Test type | Standards followed |
|---|---|
| Web application pentest | OWASP Web Security Testing Guide (WSTG), OWASP Top 10 |
| API pentest | OWASP API Security Top 10 |
| Network pentest | NIST SP 800-115 |
| Cloud pentest | CIS Benchmarks (AWS, Azure, GCP), cloud-provider security baselines |
| Mobile pentest | OWASP MASVS, OWASP MASTG |
Automated scanning is used only as a coverage check. The substantive findings come from manual exploitation: business-logic flaws, authentication bypasses, IDOR chains, server-side request forgery, race conditions, multi-step exploit chains. These are findings that automated scanners miss by design.
Dashboard delivery
Every result of a Budget Security test lives in the platform, not in an encrypted PDF attached to an email. Findings are published when the test ends, and the report follows within 48 hours after testing ends.
The platform gives you total insight into your findings:
- Every finding explained: severity, CVSS score with a plain-language explanation, impact, fix, replication steps, and evidence
- Track every fix: status per finding (open, in progress, fixed, mitigated, accepted risk), notes, and full history
- Developer-only accounts: invite developers who see findings only, not orders or billing
- One-click Jira issues: turn any finding into a Jira Cloud issue
- Fix prompt for your AI coding tool: each finding as a ready-made fix task for tools such as Copilot, Claude, or Cursor, with no payload and no captured credentials
- Attack map: where the testing team models your system, an interactive diagram shows what an attacker could reach and the worst they could do there
- Retest: available, priced up front, and booked from the platform
Why a platform beats a PDF
A pentest PDF is a snapshot in time. It is rarely searchable, often not version-controlled, frequently lost in shared folders, and impossible to track remediation against. The platform is built for the security manager running a continuous security program:
- Findings can be assigned to developers and tracked to closure
- Remediation status is visible to leadership at any time
- A retest is booked from the platform, not a separate procurement cycle
- Assets and past findings carry over to the next test
What a Budget Security report includes
Every test includes:
- Executive summary: a risk-rated overview written for stakeholders and audit reviewers
- Detailed vulnerability report: a PDF per tested asset with every finding, its severity, CVSS score, description, impact, replication steps, evidence, and references
- Written fix recommendations: practical fix guidance for each finding, not generic advisory text
- Platform access: track progress, follow every fix, and download your reports
Also available, priced up front: a retest, an after-test walkthrough, a report discussion, a separate summary document, and a statement letter. Compliance mapping is available on request. Reports are in English; Dutch reports are available on request.
Compliance framework coverage
Budget Security pentests are used as evidence for these compliance frameworks:
- SOC 2: supports Trust Services Criteria CC4.1 (monitoring controls) and CC7.1 (system vulnerability detection)
- ISO 27001: supports Annex A controls A.8.8 (management of technical vulnerabilities) and A.8.29 (security testing in development and acceptance)
- NIS2: supports Article 21(2)(e), assessing the effectiveness of cybersecurity risk-management measures
- HIPAA, PCI DSS, DORA, and GDPR Article 32: scope is tuned per framework on request
FAQ
Frequently asked questions
How is a pentest scoped?
Is the actual testing done by AI?
How long does a pentest take from booking to report?
What standards does Budget Security follow?
Can I see the price before I commit?
Can I get the report in Dutch?
Ready to scope your pentest?
Open the pricing calculator. Pick your asset type and the number of tester-days and see the price, before creating an account.
Open pricing calculator