IoT and Connected Device Testing

IoT and Connected Device Penetration Testing

A connected product is four systems at once: the device, its firmware, the radio and the cloud behind it. We test all four, and produce the evidence the PSTI Act expects. CREST-certified testers, fixed price from £4,960, scoped in 24 hours.

  • Unlimited retesting
  • No rescheduling or cancellation fees
  • Fixed quote within 24 hours
Accredited & recognised
Cyber Essentials certified Cyber Essentials Plus certified IASME certifying body ISO 27001 certified ISO 9001 certified Crown Commercial Service supplier UK Cyber Security Council member
CREST Member
Verified accreditation
10
Device test areas
FREE Retest
Until the finding is closed
24h
Scope to active testing
CLIENT REFERENCE
“I would highly recommend EJN Labs to any organisation seeking reliable, detailed, and well-managed penetration testing services, particularly for government or enterprise-level projects.”
SquareOneImran SaghirProject Lead, SquareOneRead the SquareOne case study →
CLIENT REFERENCE
“There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.”
CelloriDan WilcocksonFounder, CelloriRead the Cellori case study →
See all case studies →
WHY IT MATTERS
PSTI

Software you can fix on a Friday. A product in someone home is different: the firmware has to be updated over the air, the update has to be signed, and the device has to survive being taken apart by whoever bought it.

The device is the part you cannot patch quietly

So the test covers the physical side as well as the network one. Debug interfaces on the board, firmware extracted from flash, secrets stored in it, and whether secure boot actually prevents modified firmware from running.

Then the ecosystem: the pairing flow between app and device, the radio protocol in between, and the cloud API that trusts a device identity which anyone holding a device can also present.

ISO 27001, SOC 2, PCI DSS and Cyber Essentials Plus audits accept manual penetration test evidence. Scan-only evidence is generally insufficient.

CONNECTED DEVICE SPECIFICS

What We Actually Test in a Connected Device

Ten areas that apply because there is hardware in the product, on top of the application and cloud testing around it. Every finding is verified, reproducible and mapped to the PSTI Act, ETSI EN 303 645, CWE and CVSS 3.1.

IOT-01

Hardware interfaces

Debug and serial interfaces on the board, flash access, and what can be read or written with physical access.

IOT-02

Firmware analysis

Extracted firmware, hardcoded credentials and keys, third party components and their known issues.

IOT-03

Secure boot and update

Signature verification, rollback protection, and whether modified firmware can be made to run.

IOT-04

Default credentials and provisioning

Unique per-device credentials, first-use setup, and factory reset behaviour, as PSTI requires.

IOT-05

Radio and local protocols

Bluetooth, Wi-Fi, Zigbee or proprietary radio: pairing, encryption, replay and proximity attacks.

IOT-06

Device to cloud

Device identity and authentication to the platform, certificate handling, and what one device can do to another account.

IOT-07

Mobile app pairing

The companion app, its secrets, the pairing flow and the API it uses on the user behalf.

IOT-08

Cloud API

Every endpoint the device and app call, tested for object level authorisation and tenant separation.

IOT-09

Data handling

What the device collects and sends, storage on device, and what a second-hand unit still contains.

IOT-10

Compliance evidence

PSTI statements, ETSI EN 303 645 provisions, disclosure policy and support period, in a form an assessor accepts.

METHODOLOGY

SAMPLE FINDING

What a IoT and embedded finding looks like

Written the way a finding appears in our reports. The example below is reconstructed from publicly documented research, with hosts, paths and identifiers redacted. We do not republish client findings, named or anonymised.

CriticalCVSS 9.6 · CWE-290 · Illustrative example

Debug console gives the firmware, and the pairing layer lets a device be impersonated

Affected
A mains powered camera product, hardware revision [redacted], and the cloud pairing service it ships with.
What we found
Serial output was available on unmarked test pads and the bootloader dropped to a shell with no password, which gave us the full firmware and a support account reused across the product line. Separately, the peer to peer pairing layer let a device identifier be impersonated, so the mobile client connected to us rather than to the customer camera.
Why it matters
Anyone with physical access to one unit extracts a credential valid on every unit shipped, and an attacker on the network path intercepts the video and audio stream and replays the client credentials.
Fix
Disable the bootloader console and serial output in production builds, blow the debug fuses, sign and encrypt firmware, give every device a unique identity held in a secure element, and move to a pairing scheme that authenticates both sides.

Reconstructed from public research: CVE-2021-28372, device impersonation on the ThroughTek Kalay peer to peer platform, published by Mandiant with CISA advisory ICSA-21-229-01.

Connected Device Penetration Testing: From Scope to Attestation

CREST-aligned methodology built on OWASP Web Security Testing Guide, OWASP ASVS, NIST SP 800-115, and PTES. Each finding maps to all four standards plus your specific compliance regime.

01

Reconnaissance

Application mapping, technology fingerprinting, content discovery, parameter enumeration, authentication-flow analysis, role-matrix construction.

02

Vulnerability Assessment

Authenticated and unauthenticated automated scanning across every user role, plus targeted manual checks for known weakness patterns.

03

Manual Exploitation

Hands-on testing by a CREST-certified pentester. Business-logic exploitation, chained vulnerabilities, privilege escalation, impact validation.

04

Reporting + Retest

Executive summary, technical report with CVSS scores and reproduction steps, walkthrough call, free retest after remediation, attestation letter.

CREDENTIALS

Verified Accreditations Auditors Accept

Every credential below is independently verifiable. UK procurement teams, FCA supervisors, ISO 27001 / SOC 2 auditors, and cyber insurance underwriters all recognise these standards.

GET YOUR QUOTE

Get a CREST Connected Device assessment pen test quote in 24 hours

A fixed-price quote back in one business day, from a named CREST assessor. No sales pipeline, no chasing.

  • CREST and IASME accredited. Testing your auditors and clients already recognise.
  • Fast-track testing within 24 hours where required. Free retest of every fix included.
  • Live findings via your client portal, not a four-week PDF.
  • Fixed price from £4,960 for a small, single-scope engagement, agreed up front. Most engagements run £7,240 and up. No day-rate surprises.
What clients say
There wasn’t another company we could find that could deliver what we needed in the timeframe we needed. The client loved it, and we got instant ROI from the engagement.
CelloriDan WilcocksonFounder, Cellori

Under NDA Further named references available on a scoping call.

What happens next
  1. We reply within one business day with a fixed-price quote from a named CREST assessor.
  2. You approve the scope and we book a start date, usually within 24 hours.
  3. Live findings land in your client portal as we test, with a free retest of every fix.
Accredited & recognised
CREST member Cyber Essentials certified Cyber Essentials Plus certified IASME certifying body ISO 27001 certified ISO 9001 certified UK Cyber Security Council Crown Commercial Service supplier

Get your fixed pen test quote in 24 hours

⚡24h reply ✓CREST tester ↻Free retests

or book a 20-min scoping call first

We reply within one business day. Your data stays with us. No newsletter signup.

COMPLIANCE READY

Reports Mapped to Every Framework

Findings are explicitly tagged to the relevant control reference. Your audit team submits the report directly without translation work.

ISO 27001:2022

Annex A.8.8 management of technical vulnerabilities plus A.5.15-5.18 and A.8.2-8.5 access control validation.

SOC 2 Type I & II

CC6 logical access, CC7 system operations, CC8 change management evidence.

PCI DSS

Requirement 11.4 application penetration testing across cardholder data environments, including ecommerce penetration testing for online retail platforms.

FCA SYSC

SYSC 4.1.1R, 6.1.1R, 13 mapped to each finding for FCA-regulated firms.

UK GDPR

Article 32 effectiveness testing, customer-data security controls, ICO-acceptable evidence.

Cyber Essentials Plus

Direct certification through our IASME body status, single-vendor delivery.

PRICING

Transparent Connected Device Penetration Testing Pricing

Pricing depends on the number of device variants, whether firmware and hardware sit in scope alongside the cloud and mobile sides, and how far the radio work goes. The day count flexes; the included deliverables stay the same across all engagements.

✦ ALWAYS · ON EVERY TIER · NO EXCEPTIONS ✦
✓Free retests, no time limit
✓Free rescheduling
✓No cancellation fees
✓24-hour scope to active testing
✓Live findings to client portal
✓Executive + technical report
✓60-min walkthrough call
✓Letter of attestation
SMALL / SMB
£4,960–£7,240
4 to 6 testing days

Single user role, basic CRUD application, marketing website with auth. Around 5 working days from kickoff to report.

Get a fixed quote
ENTERPRISE
£9,880–£13,600
8 to 11 testing days

Multi-tenant platform, complex authorisation matrix, integration-heavy applications. Around 15 to 20 working days from kickoff to report.

Get a fixed quote

Part of Technologies We Pen Test. These are examples of the stacks we publish pages for, not a complete list. If yours is not here we still test it. Related pages:

Full UK pen test cost guide

WHY EJN LABS

What You Get From Connected Device Penetration Testing

Six concrete differentiators competitors don’t all match.

CREST-Certified Testers, Verifiable

Every test by a CREST-certified pen tester (CRT, CCT APP, CCT INF where applicable). Verify our company status at crest-approved.org.

24-Hour Startup, Where Required

From signed scope to active testing in a single business day for incident response, audit deadlines, or regulator-driven timelines.

Live Findings, Not 4-Week PDFs

Critical issues reported during testing through your client portal. Your team remediates while testing continues.

Audit-Ready Reports

Executive summary plus full technical report with CVSS scores and explicit framework mappings (ISO 27001, SOC 2, PCI DSS, FCA SYSC).

Free Retests, Standard

Verify remediation of every finding before close-out. Letter of attestation for audit submission included. Most competitors charge £1,500-£3,000 per retest.

UK-Based CREST Testers

Every engagement performed by vetted, UK-based CREST-certified testers, matched to your needs, security clearance, and compliance scope.

FAQ

Frequently Asked

Do you need physical units?

Yes, at least two so one can be dismantled. We agree that during scoping.

Do you test to ETSI EN 303 645?

Yes, and the report maps findings to its provisions alongside the PSTI requirements.

Will the devices be returned?

Hardware testing is destructive to at least one unit. We tell you which before we start.

Can you cover industrial devices as well as consumer?

Yes. Industrial and OT devices follow the same method with different protocols, and the safety constraints are agreed first.

Do you provide PSTI statements for us?

We provide the evidence and the findings. The statement of compliance is yours to make, and we tell you what is missing.

What about the cloud platform?

Included by default. A connected product without its cloud is only half tested.

Do you test device enrolment and per-device keys?

Yes. We test how a new device is provisioned onto the platform, whether an enrolment token can be reused, guessed or replayed to enrol a rogue device, and whether each device holds its own unique key rather than a key shared across the fleet. A shared key means one compromised device can be used to impersonate others.

Do you test fleet ownership and remote commands?

Yes. We test whether devices can be reassigned between customers or sites cleanly, without one owner retaining access after a transfer, and whether commands sent to a device are authenticated and authorised so a device cannot be made to accept commands from anyone who can reach it on the network. We also check that command replay is not possible.

Can you test our IoT fleet alongside the customer portal that manages it?

Yes. Most connected device deployments have a web portal where customers or operators enrol devices, view telemetry and send commands, and testing the devices without that portal misses how ownership and permissions are actually enforced. See our customer portal page for how we scope the two together in one engagement.

Do you test connected vehicle platforms, not just individual devices?

Yes. We test the backend behind connected vehicles, including how vehicle ownership and device pairing are recorded, so a device cannot be paired to the wrong account or transferred without the right checks. We also test dealer and customer portal boundaries, so dealer staff cannot reach data or vehicles outside their own accounts.

How do you test remote commands and telemetry privacy on connected vehicles?

We test who can issue remote commands such as unlock, start or locate, and whether authorisation is checked correctly before a command reaches the vehicle. We also review telemetry handling for privacy, checking that location and usage data stays visible only to the account it belongs to, rather than being exposed through shared APIs or dashboards.

Do you test port and shipping systems, including manifest and vendor access?

Yes. We test port community systems and vessel or cargo operations platforms for manifest integrity, checking that cargo records cannot be altered by a party without the right authority. We also test how shipping lines, agents and vendors are separated within the same system, so one party’s access cannot reach another party’s manifests or bookings.

Does testing cover the IACS requirements for onboard vessel systems?

IACS UR E26 and UR E27 set class-society requirements for vessel and onboard system cybersecurity, built around supplier and integrator verification testing rather than naming penetration testing directly. Where a vessel or port system falls under these requirements, we can test alongside that process, while class societies handle type approval.

Do you test ground-station and satellite command systems?

Yes. We test ground-station portals, mission dashboards and telemetry APIs for command authorisation, checking that only the right operator or vendor account can issue commands to a satellite or ground asset. We also test how telemetry is authenticated, so a dashboard cannot be fed spoofed or replayed data without detection.

How do you handle vendor access to space and satellite ground systems?

We map every vendor and contractor account that reaches a ground-station or mission system and test whether that access is limited to what each vendor actually needs. We also test handover points between vendor-managed and operator-managed systems; in our experience these boundaries are where permissions most often carry over further than intended.

What is included in the price?

Scoping, testing, the executive summary, the technical report, a walkthrough call and free retests until the finding is closed. One scope, one number, no follow-up invoices.

How fast can you start?

Scope to active testing in 24 hours once the scope is agreed, subject to tester availability in your window.

Are your testers CREST certified?

Yes. EJN Labs is a CREST member company and testing is delivered by CREST-qualified testers. The membership is verifiable on the CREST marketplace.

EXPLORE EVERY SERVICE

20+ CREST-accredited testing services in one place

Web, mobile, API, cloud, AI, infrastructure, red team. Pick the test that fits your environment.

Penetration testing services
READY TO START

Get your connected product tested properly

Tell us what the device is and what it talks to. You will have a fixed scope and a number within 24 hours.