Your annual pentest was true for about three weeks.

Your product keeps shipping. We test your external attack surface continuously and send weekly reports with reproducible findings.

Start a scoping conversation

An annual test answers the wrong question.

It tells you what was vulnerable when the test ran. Your next release changes the question: are we introducing risk as we ship?

You ship a new feature, add an API or change who can access what. The old report describes the old surface.

Someone still has to run the tests, investigate the results and give engineering findings they can reproduce.

We report a vulnerability only after we've exploited it.

Ongoing fuzzing and AI-powered testing across your agreed external scope. A report every week.

Find

Test your authorised domains, wildcard subdomains, web apps, APIs and endpoints.

Prove

Demonstrate exploitability within the agreed testing limits. Include evidence and steps to reproduce it.

Report

See verified findings, testing activity and coverage limits each week.

No verified findings does not mean no vulnerabilities exist.

Unauthenticated testing needs no login. Authenticated testing uses agreed test accounts. Mobile apps are excluded.

Illustrative · no customer data

See what your engineers would receive.

See the affected asset, evidence, reproduction steps and fix.

High in this fictional scenario

Cross-tenant invoice access through object reference

A North workspace billing user can retrieve a fictional West workspace invoice.

Asset: billing.asterbridge.test · /api/v1/invoices/{invoiceId}

billing.asterbridge.test · /api/v1/invoices/{invoiceId}

The evidence.

REQUESTGET /api/v1/invoices/inv_2026_08421

RESPONSE

HTTP/1.1 200 OK

tenant_id: org_west_272

Overview

High in this fictional scenario

Cross-tenant invoice access through object reference

A North workspace billing user can retrieve a fictional West workspace invoice.

Asset: billing.asterbridge.test · /api/v1/invoices/{invoiceId}

Evidence

billing.asterbridge.test · /api/v1/invoices/{invoiceId}

The evidence.

REQUESTGET /api/v1/invoices/inv_2026_08421

RESPONSE

HTTP/1.1 200 OK

tenant_id: org_west_272

Reproduction

Authenticated testing

The steps to reproduce it.

01
Sign in with the authorised North test account
02
Request the agreed West test invoice
03
Check the tenant in the response.

Remediation

billing.asterbridge.test · /api/v1/invoices/{invoiceId}

The fix.

Enforce tenant ownership on every invoice read. Add a cross-tenant regression test.

Asset → Evidence → Reproduction → Remediation

Download the sample report (PDF)

Testing starts with an agreed scope.

Before testing starts, agree the assets, access, limits and stop contacts in writing.

Illustrative · no customer data

Authorised assets

Give engineering the evidence and reproduction steps. See what was tested and what was outside coverage.

You can check who's testing your systems.

Kunsh Tanwar

Your tester and direct contact for agreeing the scope.

[email protected] ↗

Companies I’ve helped secure

Through their bug bounty programs.

MicrosoftLogitechWalmartFireblocks

SiriusXM

Bug bounty program response

“Thanks again for helping us secure our systems, and we look forward to more high quality submissions from you.”

Wells Fargo

Bug bounty program response

“We're pleased to award you a bonus per the guidelines in our policy. Thank you for your submission; we look forward to seeing more reports from you!”

Amazon

Bug bounty program response

“Thank you for your submission. We have added a reward on this submission. Thanks for your continued engagement.”

Cisco Meraki

Bug bounty program response

“Thank you again and please continue researching on our program.”

Choose the access you need tested.

Continuous testing and weekly reports. Agree the scope before work starts.

Unauthenticated

$499 USD / month

Endpoint fuzzing and AI analysis without a login.

Includes

Certificate-transparency monitoring, reconnaissance and prioritised targets
Unauthenticated testing sprints
Weekly verified reports with coverage statements
Every finding impact-checked; urgent issues escalated to you first

Guardrails

Written scope
No destructive, data-changing or logged-in testing
Up to 5 requests per second; we ask before bulk actions

Authenticated + unauthenticated

$1,499 USD / month

Everything above, plus testing with authorised accounts.

Includes

Two-pass testing: without a login, then signed in
Test accounts created only with your approval
Supervised browser sessions with expiry and liveness checks
Authenticated findings merged into the same weekly report

Guardrails

Signed scope and authorised accounts
Your approval before write actions, escalation or deletion
Traceable proof; no changes to third-party systems

Testing + knowledge-base curation

$5,499 USD / month

Everything above, plus retained testing context accessible to your security team.

Includes

A curated knowledge base of your testing history: sanitised, deduplicated and reviewed before merge
Divergent results re-tested
Retained context for your security team, under governance

Guardrails

Automated curation checks plus reviewer sign-off
Your approval for access, retention, export and deletion
Trial terms apply; the knowledge base is not part of a trial

Previous handoffs, browser-session records, logs and findings inform future hunts and scans.

Authorised domains, wildcards, web apps, APIs and endpoints. Mobile apps excluded.

Start with two weeks.

$199 USD · Unauthenticated · No login

$699 USD · Authenticated + unauthenticated · Authorised accounts

Two weeks · Two weekly reports

Discuss a trial scope ↗

Questions before a call.

.v2-root .faq-list{display:none}

Does this replace our annual pentest?

Keep the assessment your customer or auditor requires. This adds testing between assessments.

Will testing affect production?

Testing carries risk. Agree techniques, limits, windows and a stop process before work begins.

Can we use the report in a customer review?

It includes evidence and reproduction steps. Ask the reviewing team what they require; acceptance is their decision.

What does our team need to do?

Agree the scope, provide any test accounts needed and act on the findings. We run the testing and report the evidence; your team owns the fixes.

We already use security tools. Where does ETX fit?

Use ETX for ongoing external testing you want to hand over. Agree the coverage alongside your existing tools.

Can we try it before choosing a monthly plan?

Start with a two-week trial and two weekly reports. Agree the assets and access before testing begins.

What do you need tested?

Bring your external assets and the change or deadline behind the request. We'll discuss a scope.

Book a discovery call

Your annual pentest was true for about three weeks.

An annual test answers the wrong question.

We report a vulnerability only after we've exploited it.

Find

Prove

Report

See what your engineers would receive.

Cross-tenant invoice access through object reference

The evidence.

The steps to reproduce it.

The fix.

Cross-tenant invoice access through object reference

The evidence.

The steps to reproduce it.

The fix.

Testing starts with an agreed scope.

You can check who's testing your systems.

Kunsh Tanwar

Companies I’ve helped secure

Choose the access you need tested.

Unauthenticated

Authenticated + unauthenticated

Testing + knowledge-base curation

Start with two weeks.

Questions before a call.

Does this replace our annual pentest?+

Will testing affect production?+

Can we use the report in a customer review?+

What does our team need to do?+

We already use security tools. Where does ETX fit?+

Can we try it before choosing a monthly plan?+

What do you need tested?

Start a scoping conversation