The bugs scanners miss,found by people.
Our specialists work through your live applications looking for flaws in access control, business logic and workflows, the kind that only a person notices. A bug is reported once it is reproduced, with proof and the steps to fix it.
- Order
- 10482
- Customer
- Mihai Pop
- Address
- Str. Exemplu 4, Iași
- Card
- •••• 8812
What you pay for
Bug hunting is priced per asset, like scanning: one domain or one subdomain. A domain does not include its subdomains, so each subdomain is an extra asset.
What you buy is a specialist's time on that asset. A single hunt finds what is there today. Monitored hunting keeps specialists on it every month, so every release gets looked at by a person, not only by a scanner.
- northwind.examplethe domain
- shop.northwind.examplea subdomain, counted on its own
- app.northwind.exampleanother subdomain
One round of hunting. Right before a launch or after a big change.
- One hunting round on the asset
- Every bug reproduced before it is reported
- Proof, severity, CVSS and fix steps per bug
- Anything you release after the hunt
Specialists stay on the asset every month and look at what you ship.
- Hunting every month, including new releases
- Confirmed bugs reported as they are found
- Proof, severity, CVSS and fix steps per bug
- A retest on production after each fix
Prices per asset, before VAT. Monitored hunting is sold for 1 or 3 years, paid up front. Testing starts only after written authorization.
Where people find what tools don't
- Broken access control
- Reading another customer's order by changing a number in the URL. Every request looks valid to a scanner.
- Business logic
- Stacked discounts, negative quantities, a payment step that can be skipped.
- Accounts and sessions
- Password reset flows, tokens that never expire, sessions that survive a logout.
- Data the screen hides
- APIs that return more than the app displays: emails, addresses, internal IDs.
How it runs
- 1ScopeYou authorize, in writing, which applications and accounts are in scope.
- 2HuntSpecialists use the app like a customer would, then like an attacker would.
- 3ReproduceNothing is reported until it is reproduced and its impact is clear.
- 4Report and retestEach bug arrives with proof and fix steps; after you fix, we test it again on production.
What a confirmed bug comes with
- The exact request and response that show the bug
- What an attacker could do with it
- Severity, CVSS score and CWE class
- Fix steps, and a retest once you ship the fix
Where to next
Tell us what you run. We will scope it with you.
Talk to an expert