Discuss an engagement
Menu

Scoping questions / Penetration testing

Hardware and IoT test scoping questions

The questions asked when scoping a hardware and IoT security test, and why each one matters. Answer them online or in a fillable PDF.

Answer on this page Download the fillable PDF

10 questions · Fillable PDF · No email required to download

These are the questions a SilentGrid consultant asks when scoping a hardware and IoT security 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.

Hardware and IoT
  1. Sizing

    Why we ask: each model has its own board, firmware and interfaces.

  2. Why we ask: firmware extraction can destroy a board, so spare units may be needed.

  3. Why we ask: each port and radio adds its own test cases.

  4. Why we ask: they save extraction time and allow deeper analysis.

  5. Why we ask: the device is often the way into the backend that trusts it.

  6. Why we ask: it sets the threat model, including how much physical access an attacker is assumed to have.

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