Skip to main content
Cloudflare Launchpad About the Launchpad

ShieldProbe platform overview

From proven exposure to a verified fix.

ShieldProbe's AI tests web apps, APIs, networks and servers within your agreed scope. A named consultant approves each pentest finding before you see it. For supported application findings, add in-app protection that starts in log-only mode, a code patch your developers review, and a retest.

Illustrative evidence record / SP-014Customer A received Customer B's order.GET /api/orders/order-b07 · 200 OK

Testing networks or servers? Every finding comes with remediation guidance in the report. Defend and Fix cover application findings. See what we test

Choose a module to see what it does with this finding.

Assess keeps the request, response, scope and impact together. A named consultant approves each finding before you see it.

Explore Assess
Assess portal · illustrative sample data
Read the evidence
SP-014Illustrative API case

Assess / Evidence review

Same requestGET /api/orders/order-b07
Signed in as
customer-a
Order belongs to
customer-b
200 OK
{
  "id": "order-b07",
  "ownerId": "customer-b"
}

Another customer’s order was returned. The ownership check is missing.

In this example, a consultant has reviewed the request, response and customer context before delivery.

The four modules

Four modules. Start with the problem you have.

  • An audit or compliance deadline: start with Assess.
  • A live exposure while the fix is in progress: Defend.
  • Slow remediation: Fix.
  • Frequent releases: Continuous (developer preview).

Assess

Prove what can be exploited within an agreed application, API, network or server assessment.

Starts with
Authorized targets, agreed method and access.
Your next action
Review consultant-approved evidence and prioritize the correction.
You get
Consultant-approved findings with request, response and impact, in the portal and the report.
Status
Core engagement.
Explore Assess

Defend

Protect supported application findings while the code fix is prepared.

Starts with
A supported finding and the installed Defend SDK.
Your next action
Watch matches in log-only mode, confirm normal traffic is unaffected, then switch on blocking.
You get
Middleware that runs inside your app, not an edge WAF. It logs only until you turn on blocking.
Status
Sold separately. Supported application findings.
Explore Defend

Fix

Turn the finding into a code patch, with the attack beside it.

Starts with
The finding, its evidence and relevant source.
Your next action
Review, test and raise the PR through your development workflow.
You get
A proposed patch in VS Code (Visual Studio in beta). Your developer raises the pull request; nothing merges on its own.
Status
Supported application findings.
Explore Fix

ContinuousDeveloper preview

Retest the running app when code changes, on repository events you enable.

Starts with
A connected repository and a staging or preview URL.
Your next action
Check what the retest found and that real users still get through.
You get
Selected tests on repository events you enable, against authorized targets.
Status
Developer preview.
Explore Continuous

What we test

Web, API, network and server pentesting.

Choose the systems to test, where they run and the access we start with. Each assessment has an agreed scope and consultant-reviewed evidence.

Web applications

Customer portals, dashboards and browser-based applications.

Test authentication, sessions, access controls and business workflows. Follow weaknesses through to their demonstrated impact.

Location
Internal or external
Access
Black-box or grey-box
Methodology
Agreed OWASP Top 10 or full WSTG scope

APIs

REST, GraphQL and SOAP APIs, including backend services and integrations.

Test endpoint authorization, data exposure, input handling and API workflows, using the agreed accounts and API specification.

Location
Internal or external
Access
Black-box or grey-box
Methodology
Agreed OWASP API Security Top 10 or full WSTG scope

Networks & server infrastructure

Internet-facing services, private networks, and on-premises or cloud-hosted servers.

Test exposed services, misconfigurations and exploitable weaknesses. Validate privilege escalation and lateral movement where the agreed scope permits.

Location
Internal or external
Access
Black-box only
Methodology
Agreed PTES scope
Internal or external?

External: test internet-facing systems from our infrastructure.

Internal: reach private applications, APIs, networks and servers through an approved connector or access path.

Black-box or grey-box?

Black-box: start without supplied login credentials and test the reachable, authorized surface.

Grey-box: use supplied test accounts and context to test authenticated web and API workflows.

Network and server infrastructure assessments currently use black-box testing.

Not sure where to start? We'll help you define targets, access and permitted activities before testing begins.

Scope your assessment

See the evidence

The illustrative sample report shows scope, request/response, impact, remediation and verification. It uses fictional data.

For background, read about report quality.

Start from your buying need.

Not sure which modules you need?

Tell us what you test and how you ship. We’ll recommend a starting point and confirm what’s available for your environment.

Visit the Trust Center or compare engagement models.

See it on your own application.

Walk through a finding with our team and ask about your environment.

See the platform