Scoping questions / Penetration testing

Wireless penetration test scoping questions

The questions asked when scoping a wireless network penetration test, and why each one matters. Answer them online or in a fillable PDF.

9 questions · Fillable PDF · No email required to download

These are the questions a SilentGrid consultant asks when scoping a wireless network penetration test. Answering them first makes the call shorter and the quote more accurate.

"Not sure" is a fine answer. Working out the unknowns is part of what the scoping call is for.

Questions marked Sizing help us prepare an accurate quote.

Before any test

  1. Why we ask: the reason sets the depth and report format, and the date fixes the testing window and any retest.

  2. Why we ask: production needs tighter limits on load, data and timing. A test copy allows more thorough techniques.

  3. Why we ask: the schedule is built around them.

  4. Why we ask: retesting is agreed at scoping, so it is scheduled and priced from the start.

Wireless networks

  1. Sizing

    Why we ask: each site and network is assessed on location.

  2. Why we ask: networks that accept domain passwords are open to evil twin credential capture. Certificate-based networks are not.

  3. Why we ask: a guest network that reaches internal systems is a common and serious finding.

  4. Why we ask: deauthentication disconnects real users, so it needs approved timing.

  5. Why we ask: it shows what an attacker in the car park could reach.

Send your answers

Your answers go to the consultant who will run the scoping call. Leave out credentials, internal addresses and other sensitive detail: general descriptions are enough.

Unanswered questions are fine; the call covers them. Handled under the privacy policy. The form is protected by Cloudflare Turnstile, which sets no cookies (Cloudflare privacy policy).