Skip to main content

Exposure validation and protection

Offensive security. In your defense.

ShieldProbe. Audit-grade AI penetration testing for web apps, APIs, networks and servers. Our AI runs the attack, and a named consultant approves each Assess finding before you see it.

Assess findings reviewed by a named consultant48-hour delivery for agreed scope and ready accessView sample report
Explore testing scope

Assess / Prove the exposure

Know what an attacker can do.

ShieldProbe proves the exploit and delivers evidence reviewed by a named consultant.

The evidence continues into protection and code repair.

Example StoreSP-014Order accessible by another customer
GET /api/orders/order-b07200 OK · Another customer’s order exposed
Assess portal · illustrative sample data
Read Assess 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.

Defend / Protect while you fix

Protect while you fix.

Add targeted protection inside your app for supported findings. Rules start in log-only mode, and your team decides when they block.

Example StoreSP-014Order accessible by another customer
GET /api/orders/order-b07This finding: logged only · Not blocked
Defend interface · sample application data
Read Defend evidence
SP-014Illustrative API case

Defend / Observe the request

Same requestGET /api/orders/order-b07
Integration
Defend SDK installed
Rule limits
No session or database access
Protection mode
Log only (ownership finding)
200 OK

The request is logged, not blocked. The application must check ownership.

Defend logs the request but can’t tell who owns the order, so the fix belongs in the code.

Fix / Put the evidence to work

Turn the finding into a fix.

Bring the attack into VS Code or Visual Studio (beta). Review the proposed patch, test it and raise your pull request.

Your developers control review, merge and deployment.

Example StoreSP-014Order accessible by another customer
GET /api/orders/order-b07Proposed patch · Developer review required
Preview mockup · representative Fix workflow
Read Fix evidence
SP-014Illustrative API case

Fix / Review the patch

Same requestGET /api/orders/order-b07
routes/orders.tsProposed patch
const order =
  await orders.findOne({
    id: req.params.id,
    ownerId: req.user.id
  });

if (!order) {
  return res.sendStatus(404);
}

The lookup now includes the signed-in owner. Review shared-team access policy before merging.

Developer review and branch tests required. Nothing auto-merges.

Representative Fix workflow

Continuous / Revalidate the change

Keep testing as you change.

Repository events you enable trigger targeted tests, so each fix is rechecked against the patched application.

Keep testing between scoped pentest engagements.

Developer preview. This replay runs with Defend off.

Example StoreSP-014Order accessible by another customer
GET /api/orders/order-b07Patched staging · Cross-customer request: 404
Preview mockup · Continuous developer preview
Read Continuous evidence
SP-014Illustrative API case

Continuous / Inspect the results

Same requestGET /api/orders/order-b07
Trigger
Enabled GitHub push
Branch
fix/order-ownership
Target
Patched staging · Defend off
Selected access checks / sample results
RequestResult
Another customer’s order404
Owner reads own order200
Signed-out request401
Shared-team accessReview needed

Defend is off, so the result reflects the code fix. The real owner can still read their order.

Continuous · developer preview

Example StoreSP-014Illustrative case
Same requestGET /api/orders/order-b07
200 OK · Another customer’s order exposed
Assess portal · illustrative sample data

The deliverable

Read the SP-014
sample report.

A useful finding connects the request, the response and the business impact. Assess findings are reviewed by a named consultant before delivery.

Open the report for the Example Store case you just followed. It uses fictional data.

Illustrative sample reportShieldProbe Assess
SP-014High

Order accessible by another customer

Scope
Example Store · Orders API
Evidence
Customer A can retrieve Customer B's order.
Required fix
Check ownership in application code.
Read sample report

Scope and method

A fictional grey-box API test with two test accounts, showing how a report sets out scope and evidence.

Reproduction evidence

Sign in as customer-a and request an order owned by customer-b.

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

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

Business impact

A signed-in customer can read another customer's order: unauthorized disclosure. Changing or deleting the order was not shown.

Remediation and protection

Bind the lookup to the signed-in owner and review the 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.

Verification

Replayed against patched staging with Defend off: 404 for cross-customer access, 200 for the legitimate owner and 401 for a signed-out request. Shared-team access still needs a policy decision.

Review and delivery

A named consultant approves every Assess finding before it reaches you. Your engagement sets the scope, access, delivery date and retest terms. The report supports your audit; acceptance is your auditor’s decision.

Illustrative sample data. No customer information.

Close the window of exposure

The report starts the work.
Keep the evidence moving.

When testing takes weeks and remediation takes months, the application stays exposed while the fix moves through engineering. A good pentest report gives you exploit evidence and remediation guidance. ShieldProbe carries that evidence into protection for supported findings, a proposed code fix and follow-up tests.

While a fix is prepared
Conventional engagementYour team implements the agreed mitigations.
With ShieldProbeEnable targeted Defend rules for supported application findings.
When developers repair it
Conventional engagementUse the report and any agreed consultant support.
With ShieldProbeReview a proposed code patch with the attack context attached.
As the application changes
Conventional engagementArrange retests and further testing within the agreed scope.
With ShieldProbeUse enabled repository events to select follow-up tests.

Defend is purchased separately and runs inside your app, in log-only mode until your team turns on blocking. Your developers review every Fix patch. Continuous is in developer preview.

A historical benchmark, reconstructed

From a profile photo
to a $50,000 transfer.

A note in a profile photo exposed credentials. Those credentials opened a finance dashboard, where a business-logic flaw made the transfer possible.

About this scenario

This reconstruction follows one connected attack path in a financial application: exposed credentials, authenticated dashboard access and an exploitable transfer workflow.

The $50,000 is the transfer the attack made possible in that scenario. It is not money recovered or a ranking of vendors.

The Example Store report above is a separate, fictional case.

See the Assess interface (opens image in a new tab), shown with anonymized sample data.

  1. Profile photoA visible note exposes credentials.
  2. Finance dashboardThe credentials provide access.
  3. Transfer workflowA business-logic flaw allows the transfer.

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.

What we test

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.

What we test

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.

What we test

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

Connected to your workflow

Fits where
the work happens.

Security gets reproducible findings. Engineering gets the attack behind the proposed fix.

  • Security and audit teams

    Scope, exploit evidence, business impact and remediation guidance in the Assess report.

    Explore Assess
  • Your applications

    Defend middleware runs inside your app. It starts in log-only mode, and your team decides when supported rules block.

    Explore Defend
  • VS Code and Visual Studio

    Proposed code patches with attack context. Your developers review, test and raise the PR. Visual Studio is in beta.

    Explore Fix
  • GitHub and Azure DevOps

    Targeted tests on the repository events you enable. Continuous is a developer preview.

    Explore Continuous

Close your exposure window.

Bring your scope. See the evidence, the protection options and the developer workflow with our team.

Plan your assessment

What do you need before testing starts?

We agree the authorized targets, scope, test constraints and operational contacts with you. Authenticated web and API testing needs suitable test accounts, and internal systems need an approved connector or access path. We confirm access before we commit to a delivery date.

Can you deliver results in 48 hours?

Yes, for an agreed scope once access is ready. We confirm timing before testing starts, and larger or more complex scopes can take longer.

What does an assessment include?

An agreed test scope, reproducible exploit evidence, business impact and remediation guidance. A named consultant reviews every Assess finding before delivery. Fixed findings can be retested for 12 months under your engagement terms. Defend and Fix are separate modules.

What is required to use Defend?

Defend is purchased separately and installed in your application. It starts in log-only mode, and your team turns on blocking for supported findings. Some findings, such as ownership flaws that need session or database context, are logged but not blocked; those need a code fix.

Which modules are available, and what is in preview?

Assess, Defend and Fix are available: Assess for scoped pentesting, Defend as middleware in your apps, and Fix in VS Code, with Visual Studio in beta. Continuous is a developer preview and runs only on repository events you enable. We confirm integrations and commercial terms for your environment.