Attack Path Testing: Scan the Whole Product, Not One Piece

Scanning one asset at a time misses the bugs that run between them. Put your web apps, APIs, servers, and code in one scan and see how a weakness in one reaches the next.

  • Find bugs that a single-asset scan cannot see, where one asset is only exploitable through another.
  • Stop reviewing the same bug twice in two reports without knowing they share a cause.
  • Set up one scan for the whole product instead of one per asset, with credentials entered once.
  • Send developers a fix that points at the code, not just the endpoint where the bug showed up.

One scan for the whole product

Real attacks move between assets

A token left in a repository, accepted by an API, used from a mobile app. Scan those three apart and you get three clean results, and miss the path straight through them.

01

Pick what goes in the scan

Add web apps, APIs, networks, repositories, and files, as many as you want. You do not need a mobile app at all.

02

Add a mobile app if you have one

One Android, iOS, or HarmonyOS app can go in, from the store or an uploaded build. Mobile is the only one limited to one per scan.

03

Get findings you can act on

Findings from every asset, validated by the AI agent with proof-of-concept exploits, in one consolidated report.

Proof, not correlation

Chains we've proven

Correlating findings from separate scans tells you two issues might be related. Ostorlab tests the assets together and backs a chain with a proof-of-concept exploit.

Healthcare provider

Source map leak to full account takeover

  1. Source maps Production source maps exposed the paths to admin-only endpoints.
  2. Admin endpoints Those endpoints exposed a set of undocumented admin APIs.
  3. Authorization gap Every admin API checked authorization — except the impersonation API.
  4. Account takeover Impersonate any user and take over any account.

One unprotected API turned a source map leak into full account takeover.

Bank

Two usernames to remote code execution

  1. Source leak Source code exposed two internal usernames.
  2. Password reuse One matched an account that shared its password and carried no role.
  3. Permission bypass That account reached an API that skipped role checks.
  4. Privilege escalation A role-assignment call granted it admin.
  5. Configuration API Admin unlocked a configuration API.
  6. Remote code execution A configuration change led to code execution on the server.

Two leaked usernames chained all the way to remote code execution.

You can also add supporting files, such as API schemas and architecture documents, so the agent tests against how your product is meant to work. Supported assets and files

Why Teams Scan Assets Together

Catch bugs that span two assets

An API that trusts too much and the app that calls it are only a bug together. Scanned apart, both look fine and nothing gets reported.

Go straight from finding to the code

When the app and its source are in the same scan, findings can point to the code behind them, so nobody has to hunt for where the bug lives.

Leave nothing outside the scan

Assets split across separate scans leave gaps nobody owns. One scan over the product means every asset is covered.

Set it up once, not once per asset

Credentials, scan profile, effort, and custom checks are entered a single time. Adding an asset takes one line, not a whole new scan.

Scan code without repository access

If you cannot get access to the repository, upload an archive instead and still get findings in the code. No waiting on approval.

One list, ranked, not five reports

Findings from every asset arrive in one list, ordered by what matters most, so teams fix instead of comparing reports.

What you can put in a scan

Add as many of each as you want. Mobile is the only one limited to one per scan.

Web applications

Sites, portals, and the backends your product runs on.

Unlimited

APIs

REST, SOAP, and GraphQL endpoints, with schemas if you have them.

Unlimited

Networks

IPv4 and IPv6 addresses and ranges behind your product.

Unlimited

Source code

GitHub, GitLab, Azure DevOps, Bitbucket, and self-hosted Git.

Unlimited

Archives and files

Repository archives, config files, and other supporting files.

Unlimited

Mobile app

Android, iOS, and HarmonyOS, from a store or an uploaded build.

Up to one

Before you start

What to expect from a multi-asset scan

A mobile app is optional. A scan of web apps, APIs, networks and code alone is just as valid.

What you get

  • One consolidated report, with each finding's severity, affected asset and remediation guidance.
  • Attack chains across assets, validated with proof-of-concept exploits.
  • One set of settings for the whole scan: profile, AI provider, effort, test credentials, prompts and custom checks.

What you need

  • At least one asset, added one at a time: web apps, IP addresses or ranges, repositories, archives, files, and up to one mobile app.
  • An AI provider: Cyber Models credits, or your own key (BYOK Simple or BYOK Advanced).
  • An effort level: Core, Advanced or Elite (about 50, 200 or 400 credits). Higher effort covers more risks.
  • For code, a Git integration (GitHub, GitLab, Azure or Bitbucket), or an uploaded archive (.zip, .tar.gz, .tgz, .7z) that needs no repository access.
  • Optional: test credentials, from a login and password to 2FA, client certificates and HTTP headers.

What it covers

  • Web apps, and the backends, APIs and portals your other assets talk to.
  • IPv4 and IPv6 addresses and ranges, Git repositories and repository archives.
  • Supporting files such as API schemas, scripts and configs, so the scan reflects how your system is built.
  • One mobile app: Android, iOS or HarmonyOS, from a store or an uploaded build.

What it doesn't cover

  • At most one mobile app per scan. Every other asset type has no limit.
  • SBOM and lock files are not assets. You upload them in the SBOM Files step.
  • Effort levels that cost more than your credit balance stay disabled until you add credits.
  • Custom checks are not enabled by default. Contact Ostorlab support for access.

Trusted by Security Teams Worldwide

Discover why industry experts love working with our platform

4.8 / 5
FAQ

Frequently asked questions

Straight answers on coverage, setup, and how results reach your team.

Can't find your answer? Book a demo or contact us.

Scan your whole product

Find the bugs that only show up when your assets are scanned together.