IoT Device Pentest Readiness Check

Fourteen yes/no questions that measure how ready your IoT and OT devices are for firmware, communication and companion API security testing.

  • 14 questions
  • ± 6 minutes
  1. 1Details
  2. 2
  3. 3
Before you start

Before you start

Four short fields so we can send you the result and follow up if you wish.

The result summary is sent to this address.

By continuing you agree that these details are used to send your result and to follow up, per our Privacy Policy.

14 questions · ± 6 minutes

What this questionnaire covers

Questions are grouped by area. Open any area to see its questions before you start.

How the score is read

The score is the percentage of yes answers across all questions, mapped to one of these three levels.

0–39%

Not Test-ready

Basic device scope and controls are not ready. Tidy the device inventory, default credentials, and network segmentation first.

40–74%

Partially Ready

Your devices are ready to be tested with some caveats. Complete the lowest-scoring areas before testing begins.

75–100%

Test-ready

Your devices are ready for effective security testing. Next: agree the scope and the device samples to be tested.

Device scope5 questions
  1. Is the inventory of IoT/OT devices (type, firmware version, location, function) complete and current?
  2. Are representative device samples available for physical and firmware testing?
  3. Is technical documentation (communication protocols, companion cloud APIs) available?
  4. Are IoT devices placed on a network segment separate from the main IT network?
  5. Does the device vendor/manufacturer support security updates and allow third-party testing?
Firmware and communication security5 questions
  1. Is the firmware update mechanism secure (digitally signed and unable to be modified by unauthorised parties)?
  2. Have default device credentials been changed systematically across all units, not just a sample?
  3. Is device-to-server/cloud communication encrypted (TLS/DTLS) with server certificates verified?
  4. Does the device have protection against unauthorised physical access (debug ports, tamper detection)?
  5. Is the device's companion cloud API (mobile app/backend) tested for authorisation so one account cannot access another account's devices?
Follow-up4 questions
  1. Is IoT device network activity monitored to detect anomalies such as botnet-infected devices?
  2. Does the incident response plan cover scenarios where IoT/OT devices are compromised?
  3. Have findings from previous IoT testing been remediated and re-verified?
  4. Is every finding tracked in a central register with an owner and deadline?

Frequently asked questions

What standard does IoT device testing follow?

The OWASP IoT Top 10 for general IoT devices, and the IEC 62443 reference for industrial OT environments (SCADA/ICS), which carry additional operational safety considerations.

Does testing risk damaging physical devices?

Testing is designed to be non-destructive on prepared samples. Damage risk is discussed and agreed in the rules of engagement before testing begins.

What is the difference between consumer IoT and industrial OT in this testing?

Consumer IoT generally focuses on internet-connected devices such as cameras and sensors. Industrial OT (SCADA/ICS) carries additional operational safety considerations and a more careful testing methodology to avoid disrupting production.

How long does IoT device testing take?

Usually 2 to 3 weeks depending on the number of device types and the complexity of the communications tested.

Plan the IoT device test with our team

IoT/OT device security testing covering firmware, communications and companion cloud APIs, based on the OWASP IoT Top 10, with a free retest.