FAQ   21 questions

Ask beforewe start.

These are the questions clients put to us on the first call. If yours is missing, a tester will answer it.

§1
Before you sign
6 questions
§2
During the test
5 questions
§3
Report and retest
6 questions
§4
Price and paperwork
4 questions
§1   Before you sign

Is this the right test?

What does a test give us that a scanner does not?

A scanner lists what might be wrong. A tester tries it, chains small weaknesses together and shows how far they reach. Every finding comes with proof.

Which test should we start with?

Tell us what you want to protect and why. If nothing has been tested before, an external network test is usually the cheapest first look. We will say so if a smaller test is enough.

Who actually does the work?

The testers named in your scope. They are on the first call, they run the test and they walk you through the report.

Can you test production systems?

Yes, and most clients prefer it. You agree the test windows in writing, and anything fragile goes on an excluded list.

Do our staff need to know?

Your stop contact must. For a network or application test we usually tell IT as well. For social engineering or a red team, only the person who signed knows.

How soon can you start?

Most tests start within three weeks of signing. That figure is sample data. The scope gives you the exact dates.

§2   During the test

Whilewe are in.

Can a test take our systems down?

We work to avoid it. No denial of service unless you sign for it, and we ask before anything that could affect a live service.

What if you find something serious on day one?

We call your named contact the same day with the proof and a fix. Critical findings never wait for the report.

How do we stop the test?

One call from your stop contact to +1-555-0187, at any hour. Everything stops, and nothing restarts until they say so.

What happens to any data you reach?

We take the smallest proof that shows the access, keep it encrypted and delete it after the retest. The rule is in the signed scope.

Will our monitoring see you?

It might, and that is useful to know. We log the time of every action, so your defenders can compare what they saw with what we did.

Two testers reviewing a dark wall console together
§3   Report and retest

What you get at the end.

Day 38

We come back and run every Critical and High again, free.

What is in the report?

A summary for your board, the attack path, and each finding with its proof, severity and fix. A sample runs to 38 pages.

How do you score findings?

With CVSS, plus a plain note on what the finding reached in your systems. Our work follows NIST SP 800-115 and PTES.

Do we get to ask questions?

Yes. On day 8 the testers go through the findings with your team on a call. Bring the people who will fix them.

What does the free retest cover?

Every Critical and High in the report. You get the result in writing, finding by finding.

What if a fix does not hold?

The finding stays open in the retest letter, with the reason and what to change.

Can we share the result with customers or auditors?

Yes. Ask for a short summary letter that leaves out the technical detail. The full report stays with you.

§4   Price and paperwork

Fixed before we start.

How do you set the price?

By scope, not by the hour. After a thirty-minute call you get a written scope and a fixed price within two working days.

What can change the price?

Only a scope change you agree to in writing. If we need longer than planned, that is our cost.

Will you sign an NDA?

Yes, before the first call if you want. You sign the rules of engagement before anyone touches a system.

What certifications do you hold?

The scope lists each tester's certifications, and we send copies on request. Certificates on this demo are demo samples.

Typical length
External network
5 days
Web and API
8 days
Cloud
6 days
Internal and AD
7 days
Social engineering
5 days
Red team
4 to 8 weeks
Not answered here?

Ask a tester.

Thirty minutes, no salesperson
Tester at a dark desk reading an attack path on a laptop