SecureBlockLog in
Start a pentest
Kickoff in 48 hours

Book a real penetration test the way you buy anything else.

Scope it in two minutes, see a fixed price on the spot, and have OSCP- and CREST-certified testers on your stack within 48 hours. Reports drop straight into SOC 2, ISO 27001, PCI DSS and HIPAA evidence requests.

Manual testing, not a scanFree retest includedResults in 10 business days
app.secureblock.com/order
1Assets
2Scope
3Timeline
4Contact
Step 1 of 4
What do you need tested?
Web application
Domain / staging URL
API
42 endpoints · OAuth
Cloud environment
AWS / GCP / Azure
Mobile app
iOS or Android
2 of 4 selected
Evidence accepted forSOC 2ISO 27001PCI DSSHIPAATester certificationsOSCPCRESTOSCE
The platform

Your team and your testers in the same workspace.

Findings land live as testing happens. Every issue has a direct line to the tester who found it — no ticket queue, no account manager in between.

app.secureblock.com/projects/acme-corp-web/overview
SecureBlock
Dashboard
Projects
Taskboard
Team
Reports
Settings
Projects/Acme Corp — Web Application
AC
Acme Corp — Web Application
Start: 12 Jan 2026 · Due: 12 Feb 2026 · Lead: M. Kovač (OSCP)
In progress · Day 6 of 10
Overview
Vulnerabilities
Scope
Tasks
Reports
Notes
Description

Full web application and REST API penetration test covering authentication, authorisation, business logic, and OWASP Top 10 across all in-scope endpoints. Includes multi-role testing for admin, user, and guest principals.

Testing progress60%
Day 6 of 10 · report est. Day 12
Open findings5
1 Crit2 High1 Med1 Low
Activity
MK
M. Kovačadded findingCritical · 9.1

Horizontal IDOR on /api/v2/invoices/{id}

2h ago
DO
Dana O.commented

Does the list endpoint also leak cross-tenant IDs? Pagination might expose them too.

2h ago
MK
M. Kovačreplied

Confirmed — /api/v2/invoices has the same missing ownership check. Updating this finding to include it.

3h ago
DO
Dana O.set "Mass assignment" status toFix verified
5h ago
SB
SystemProject started · NDA signed · credentials confirmed
Day 3
MK
Add a comment…Send
AI
AI Assistantonline

What's the best remediation for the Horizontal IDOR on /api/v2/invoices/{id}?

AI

Root cause is a missing ownership check server-side. The API returns data for any valid integer ID regardless of the caller's tenant.

  • Validate tenant_id ownership before returning any resource
  • Replace sequential integer IDs with UUIDs or opaque tokens
  • Add a server-side assertion: if invoice.tenant_id ≠ current_user.tenant_id → 403

Should we also add rate limiting to prevent enumeration?

AI

Yes — ownership checks are the fix, but rate limiting limits blast radius if a similar issue surfaces elsewhere. Also add audit logging for any 403s on resource endpoints.

Ask about this finding…Ask

We scoped on a Tuesday and testing started that Thursday. The report went straight into our SOC 2 evidence folder untouched — our auditor had zero follow-ups.

Dana Okonjo
CTO, Ledgerpath
SOC 2 Type II · 2026

The findings read like they were written by someone who had actually used the product.

Marcus Reid · Head of Security, Fernwood

Retest was included and turned around in three days, so we closed the audit finding in the same quarter.

Priya Nandakumar · VP Engineering, Certiv
How it works

From "we need a pentest" to scheduled in one sitting.

No RFP, no three-week sales cycle, no scoping spreadsheet.

STEP 01
Scope it yourself

Pick your asset types and answer four questions. Two minutes, no call required.

STEP 02
Get a fixed price

A transparent quote with the scope multiplier and retest shown line by line.

STEP 03
Lock in dates

Pay now or approve after a scoping call. Either way the window is reserved.

STEP 04
Testing begins

Certified testers work manually. Findings appear in-platform as they are confirmed.

STEP 05
Report and retest

Evidence-ready report in 10 business days, then a free fix-verification retest.

Coverage

Every surface you ship, tested by hand.

Pick one asset type or all six — the scope drives the price, and nothing is bundled that you don't need.

Platform

Your pentest doesn't end in a PDF.

Every engagement runs through the SecureBlock platform — findings, conversations with your testers, retests and evidence exports, all in one place.

Reports live in the platform

Findings land as they are confirmed — not as a PDF three weeks later. Export evidence the moment your auditor asks.

Talk to the testers directly

Comment on any finding and the tester who wrote it answers. No ticket queue, no account manager in between.

Manage the whole engagement

Scope, schedules, credentials, retest requests and team access — one place, with a full audit trail.

app.secureblock.com/projects/acme-corp-web/vulnerabilities
Projects/Acme Corp — Web Application
AC
Acme Corp — Web Application
Start: 12 Jan 2026 · Due: 12 Feb 2026 · Lead: M. Kovač (OSCP)
In progress · Day 6 of 10
Overview
Vulnerabilities
Scope
Tasks
Reports
Notes
Vulnerabilities4
Export evidence+ Add finding
#DateTitleSeverityStatus
0114 JanHorizontal IDOR on /api/v2/invoices/{id}criticalOpen
0214 JanMass assignment on POST /users/profilehighFix verified
0315 JanSession fixation on password reset flowmediumRetest requested
0415 JanMissing HSTS preload on marketing subdomainlowOpen
Methodology

Depth you can audit, not just claim.

Every engagement follows OWASP WSTG, PTES and NIST SP 800-115, executed by testers who hold OSCP, CREST CRT or OSCE.

OWASP WSTGPTESNIST SP 800-115MITRE ATT&CK
Day 0
Kickoff call

Scope confirmed, credentials exchanged, NDA in place.

Day 1–10
Active testing

Manual testing. Confirmed findings published as they land.

Day 12
Report delivered

Evidence-ready report with remediation per finding.

Within 90 days
Free retest

We verify your fixes and reissue the report.

app.secureblock.com/projects/acme-corp-web/findings/sb-01
Projects/Acme Corp/Vulnerabilities/Horizontal IDOR — invoices
Horizontal IDOR on /api/v2/invoices/{id}
Description

An authenticated user can access invoice records belonging to other tenants by substituting their own resource identifier in the URL path. The ownership check is absent server-side — the API returns data for any valid integer ID regardless of the caller's tenant.

Steps to reproduce
  1. 1. Authenticate as Tenant A. Retrieve any invoice: GET /api/v2/invoices/1842
  2. 2. Replace the ID with a known Tenant B value: GET /api/v2/invoices/1843
  3. 3. Server returns 200 OK with Tenant B billing data.
Impact

Complete tenant isolation bypass. Any authenticated user can enumerate and exfiltrate invoice data, payment terms, and line items for every customer in the system.

Vulnerability context
Risk
critical9.1
Target
api.acme.com
Day 2 of 10
Status
Open
Created by
M. Kovač
OSCP · 14 Jan 2026
Affected asset
/api/v2/invoices/{id}
Compliance

Which report do I need?

Pick your framework and we'll show the scope and cadence auditors expect.

Required scope
External web app + API in scope of the trust services criteria
Frequency
Annually
Retest
Expected by auditors
Type II auditors ask for evidence that findings were remediated — the free retest covers it.
Pricing

Fixed price. No discovery call. Quoted in two minutes.

Answer four questions about your scope and get the exact number your finance team needs to approve.

1Asset type2Scope size3Auth depth4Compliance framing
= your fixed price

No custom SOWs, no "prices on request." The form takes two minutes and ends with a number you can act on immediately.

All testers OSCP or CRESTFree retest within 90 daysKickoff within 48 hours
FAQ

Questions buyers actually ask.

Still unsure? Ask an engineer in chat — not a sales rep.

Standard lead time is two to three weeks from checkout; expedited engagements start within 48 hours of the kickoff call. Active testing runs 5–15 business days depending on scope, and the report lands two days after testing ends.

Know where you stand before your auditor does.