Scoping questions / Penetration testing

Desktop app penetration test scoping questions

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

10 questions · Fillable PDF · No email required to download

These are the questions a SilentGrid consultant asks when scoping a desktop application 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.

Desktop applications

  1. Sizing

    Why we ask: each platform is tested on its own build.

  2. Why we ask: each is decompiled and instrumented differently.

  3. Why we ask: clients that connect directly to a database often expose credentials or queries to every user.

  4. Why we ask: privileged components are the usual path from standard user to administrator.

  5. Why we ask: these channels often accept commands from any local user.

  6. Why we ask: a weak update mechanism gives code execution on every machine it is installed on.

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).