Skip to main content
Cloudflare Launchpad About the Launchpad

Enterprise penetration testing

Enterprise penetration testing,
with the scope under control.

Penetration testing for web apps, APIs, networks and servers, inside the targets, access and actions you approve. A named consultant approves each finding before your team sees it. The report can be ready in 48 hours, depending on agreed scope and access readiness.

Example scope map

Illustrative, not a product view

Where are the targets?

Agree the exposed targets.

Owner: the application or API owner.

We agree target ownership, authorization and any third-party permission with you. External web and API testing can start black-box or grey-box; network and server testing starts black-box.

External reachability

Web applications and APIs

Agreed internet-reachable targets, roles and business workflows.

Black-box or grey-box
Internal reachability

Networks and servers

Agreed ranges and services within the authorized environment.

Black-box starting access
Agreed testing boundary (dashed line)Target owner · testing window · escalation · stop conditions

Your operating rules are part of the scope.

Before testing starts, we agree target owners, roles, private access and testing windows with you, plus anything that needs extra sign-off, who to call and when to stop.

That includes network penetration testing, internal or external, for on-premises and cloud-hosted servers (black-box). For AWS-hosted targets, see AWS pentesting scope and permission.

Review the scope matrix
A clear owner at each handoff
  1. Your team
    Authorize and prepare

    Confirm targets, roles, access, windows and escalation.

  2. ManticoreAI
    Test and review

    Test the agreed scope. A named consultant approves each finding before delivery.

  3. Your owners
    Act and verify

    Act on findings, review protection and code changes, and check the retest.

What each team receives.

Security

Demonstrated impact, scope reached and priorities.

Engineering

Reproduction evidence (request and response for application findings) and proposed patches for supported findings.

Assurance

Scope, method, the named reviewer and limitations, together for your assessor.

Procurement

Delivery date, retest terms and data handling written into the engagement.

A web and API example

Evidence your team can act on.

An Assess report connects tested scope, reproducible findings, business impact and a clear next action.

This example uses fictional data to show how a report is laid out.

Illustrative sample reportShieldProbe Assess

SP-014 High · illustrative severity

Order accessible by another customer

Scope
Example Store, Orders API. Two authorized test accounts.
Observed impact
Customer A can retrieve Customer B's order.
Required correction
Check object ownership in application code.
Read sample report

Executive summary and scope

A fictional grey-box API test, not a completed customer engagement: one authenticated route, tested with two test users. A real report sets out everything in scope.

Method and reproduction

Sign in as customer-a. Request order-b07, which belongs to customer-b. Compare the returned owner with the authenticated account.

GET /api/orders/order-b07
Authenticated account: customer-a

HTTP/1.1 200 OK
{ "id": "order-b07", "ownerId": "customer-b" }

Impact and severity rationale

One customer can read another customer's order: unauthorized disclosure. Changing or deleting the order was not shown. High assumes the order data is sensitive; a real report gives the severity method and business context behind each rating.

Remediation and protection

Bind the lookup to the signed-in owner and review the intended shared-team access policy. Defend can log this request but not block it, because a rule cannot see sessions or the database to decide who owns an order.

Illustrative verification record

Patched staging, Defend off: cross-customer access returns 404, the legitimate owner returns 200, and a signed-out request returns 401. Shared-team access still needs a policy decision. Sample results.

Review and delivery

A named consultant approves every Assess finding before delivery. Your engagement sets the authorization, targets, method, access, exclusions, delivery date and retest terms. The report supports your audit; acceptance is your auditor's decision.

After the finding.

Assess delivers consultant-approved evidence. For supported findings, Defend (sold separately) can protect the app while engineering works on the permanent fix. It starts in log-only mode, and your team decides when it blocks.

Fix proposes patches for developer review. Continuous, in developer preview, runs targeted tests on the repository events you enable. Defend and Fix cover application findings; network and server findings come with remediation guidance in the report.

Bring these inputs to the scoping conversation.

  • Target types, owners and approximate scope.
  • Internal/external access and required user roles.
  • Testing windows, safety limits and desired report date.
  • Assessor requirements and remediation owners.
  • Procurement, support and data-handling requirements.
  • Price depends on targets, endpoints, access and retest terms. See what changes a quote.

Vendor due diligence

The Trust Center covers access, hosting, subprocessors and evidence retention. We’ll work through your contractual requirements with you.

Inference uses Microsoft-hosted OpenAI models through Azure Foundry. Microsoft processes prompts and outputs; they are not made available to OpenAI.

Audit evidence

Explore SOC 2, ISO 27001, PCI DSS or HIPAA assessment support.

Start with one application.

Judge the evidence, then expand the program.

Plan enterprise scope