Skip to content
RootCut

Request a test

Not sure? Book a call

Request a test

What would you like us to test?

Pick the area you're worried about. Not sure? Use “Help me choose”.

A few clicks, about 3 minutes, with a rough estimate in man-days. We reply within one business day to scope it with you and set up your portal account.

Not technical, or no time for questions? Skip them and talk to one of our testers

How much should we know before we start?

More information means less time guessing and more time finding real problems.

How much should we know before we start?

What's the address of the application?

Do we test the live application or a copy?

A test copy (staging) keeps any risk away from real users and data. Testing live is fine too: we are careful and agree the timing with you.

Do we test the live application or a copy?

How big is it?

Count pages and API endpoints together. Helps us plan the time.

How big is it?

Which kinds of users exist?

We test that each role only sees what it should. We'll need one test account per role.

Which kinds of users exist?

Where is it hosted?

Some cloud and hosting providers have rules for security tests. We check them and tell you if they need a notice from you.

Where is it hosted?

Which providers?

Is there a WAF in front of it?

A WAF (web application firewall), IPS or DDoS protection sits in front of your systems and blocks traffic that looks like an attack. Not sure? Pick Not sure and we'll check.

Is there a WAF in front of it?

Should we be let through it?

We recommend allowing our IP addresses: otherwise the WAF blocks most of our tests, so we would mostly test the WAF instead of what is behind it. Real attackers find ways around it, so what is behind it must be safe too.

Should we be let through it?

Add a source code review?

Finds issues a normal test can't see. Done together, as one request.

Add a source code review?

Code review is always white box: we read the code directly.

Source code review

What should we review?

What should we review?

Source code review

Languages and frameworks?

Source code review

How much code?

Lines of code, without libraries. We can count it for you with a free tool.

How much code?

Source code review

How will you share the code?

How will you share the code?

Source code review

Anything you're especially worried about?

Optional. e.g. login & sessions, payments, file uploads, access control, secrets in code.

Source code review

Is there a running copy we can use to confirm findings?

Is there a running copy we can use to confirm findings?

Source code review

Where is it running?

Source code review

Is there architecture or API documentation?

If yes, add it in the Attachments step.

Is there architecture or API documentation?

Include a retest?

After you fix the findings, we test them again and update the report, so you can show they are closed.

Include a retest?

When may we test?

Tests can slow down systems a little. Pick when that's acceptable.

When may we test?

When would you like it to happen?

We usually need 1–2 weeks' notice. We'll confirm exact dates with you.

When would you like it to happen?

Which dates work for you?

We'll confirm exact dates with you.

How do we reach you?

We reply within one business day to scope the test and set up your portal account.

You

Check and send

Nothing is sent until you press the button below. You can change anything.

    Already a client? Sign in to the portal