Skip to content
ThreatVet

We find the way in before an attacker does.

Web, mobile, API and network penetration testing to OWASP WSTG and MASTG, PTES and NIST SP 800-115. We prove the impact, not just the finding, and we come back to check the fix.

Request a scoped quoteSee the methodology
finding recordseverity: High
id
TV-WEB-041
class
Broken access control, OWASP A01
vector
Object id in an API call accepts another tenant's value
impact
Reads and edits records belonging to other customers
mapping
OWASP WSTG, authorization testing
status
Reproduced, fix verified on retest

Example finding, illustrative, not a client engagement.

What it covers

A focused assessment of the systems you choose: the web and mobile apps, the APIs behind them, and the networks they run on. We test the way an attacker works, by hand and with tooling, and we prove each issue is real before it goes in the report.

Who it is for

  • Teams before a launch or a security review
  • Products carrying sensitive or regulated data
  • Companies meeting a customer or compliance requirement
  • Anyone who wants proof, not a scan report

What the adversary actually does

The classes we test for, drawn from the OWASP testing method.

  • A01Broken access controlReaches data and actions that should be out of reach by changing an id, a role, or a path.
  • A03InjectionFeeds crafted input into SQL, commands or templates to read data or run code.
  • A07Identification and auth failuresDefeats login, session or recovery flows to take over accounts.
  • SSRFServer-side request forgeryMakes your server call internal services or cloud metadata on their behalf.
  • A08Insecure deserialisationSends hostile serialised objects to trigger code execution.
  • A05Security misconfigurationFinds exposed admin, default credentials, verbose errors and leaked secrets.

How we run an engagement

A PTES-aligned lifecycle. Vyra widens coverage; senior testers drive the exploitation and judgement. Automation does not replace manual testing here.

  1. 01

    Scope and rules of engagement

    Agree targets, limits, timing and emergency contacts before anything runs.

  2. 02

    Recon and mapping

    Enumerate the real attack surface: hosts, endpoints, auth flows and dependencies.

  3. 03

    Vulnerability discovery

    Test methodically against OWASP WSTG and MASTG, not just an automated scan.

  4. 04

    Exploitation

    Prove the issue by exploiting it safely, chaining where it increases impact.

  5. 05

    Post-exploitation and impact

    Show what the access is worth: data reached, privilege gained, blast radius.

  6. 06

    Report and remediation

    Reproducible findings with severity and fixes your engineers can act on.

  7. 07

    Retest

    We re-run the proven attacks after you remediate and confirm each is closed.

Standards we map to

Standards and what we map to each
FrameworkWhat we map to it
OWASP WSTGThe web testing method we work through, control by control.
OWASP MASTGMobile app testing for Android and iOS.
PTESThe engagement lifecycle, from pre-engagement to reporting.
NIST SP 800-115Technical testing approach and evidence handling.

What you receive

  • A map of your real attack surface
  • Reproducible findings with severity and business impact
  • Proof of exploitation, handled safely
  • Prioritised, engineer-ready remediation guidance
  • An executive summary for stakeholders
  • A retest once you have remediated

Scope a penetration test

Tell us what you want tested and why. We will scope it and send a quote. For smaller, fixed needs, see our packages.

Request a scoped quoteSee packages