Cybersecurity
IoT security services for connected products
We assess the software side of a connected product, from its firmware to the app and cloud services it depends on, and help product teams design security in from the start. We are building our product security practice on IEC 62443-4-1 and 4-2 and NIST IR 8259.
Overview
A connected product is more than a device. It is the software on the device, the app that controls it, the APIs between them and the cloud services that register, update and command every unit in the field. A weakness in any one of those parts can expose the whole product, and because the same software runs on every unit, one weakness is rarely confined to a single customer. Our IoT security services look at all of the software parts together, so the gaps between them are found as well as the gaps inside each one.
We are building our product security practice on IEC 62443-4-1 and 4-2 and NIST IR 8259. Today the practice offers two things: a security assessment of a product's software, and secure product design for teams that want security built in before launch.
Who it suits
This service suits companies that design and sell connected products: smart home devices, sensors, trackers, wearables, connected equipment and the platforms behind them. Typical reasons to start are a first product nearing launch, a large customer asking how the product was tested, a vulnerability reported by a researcher, or a new version that changes how devices connect or update.
It does not suit a company looking for hardware or chip-level testing, or for security of factory and industrial control systems. We don't offer either at this time, and we say so early so you can plan.
Security assessment of a connected product
An assessment looks at the product the way an attacker would, starting from what anyone can reach. We review the firmware and device software for the problems that recur across connected products: credentials written into the code, outdated open source components, encryption that is missing or weak, and debug features left switched on in production builds. We test the companion app and its APIs, with particular attention to how a device is paired to an account, because that is where one customer can often reach another customer's device. We review the cloud back end for the paths that would let an attacker register fake devices, read other customers' data or send commands to many units at once.
Every assessment ends with a written report. Each finding has its evidence, the parts of the product it affects, how serious it is and how to fix it, and the report opens with a summary your product leadership can read without the technical detail. We walk your engineers through it before they start on the fixes.
Secure product design
Fixing security after launch costs more than designing it in, and for a product already in customers' hands, a fix means an update every unit has to receive. Design work starts earlier. With your engineers, we build a threat model of how the product could be attacked, from the device to the cloud, and turn it into security requirements they can build and test against. The requirements draw on IEC 62443-4-2, which sets out the security capabilities a component should have, and on NIST IR 8259, which sets out the cybersecurity activities NIST recommends manufacturers carry out for their customers.
We also set up the development process that keeps security in place as the product changes: when a design change needs a security review, what is checked before a release, and how a vulnerability reported from outside is received, fixed and disclosed. That process is based on IEC 62443-4-1, the part of the standard written for product developers.
The standards behind the work
IEC 62443 is a family of standards for the security of industrial automation and control systems, and its parts 4-1 and 4-2 are the ones written for the companies that make products. NIST IR 8259 is NIST's guidance on the cybersecurity activities an IoT product manufacturer should carry out before and after a product is sold. We use them because customers and regulators recognise them, and because they give a product team a structure to work to. Using a standard as a basis is not a certification, and we don't certify products.
Deliverables
What you get
- Firmware and device software review
A review of the software that runs on the device, looking for hard-coded credentials, outdated components, weak encryption and debug features left switched on, without opening or probing the hardware itself.
- Companion app and API testing
Testing of the mobile or web app that controls the product and of the APIs it calls, covering how users sign in, how a device is paired to an account and whether one customer can reach another's device.
- Cloud back-end review
A review of the cloud services the product reports to, such as device registration, telemetry storage and the systems that send commands, for the gaps that would let an attacker reach many devices at once.
- Assessment report
A written report of every finding, with the evidence, the parts of the product it affects, how serious it is and how to fix it, plus a summary your product leadership can read without the technical detail.
- Product threat model and security requirements
For a product still in design, a threat model of how it could be attacked and a list of security requirements your engineers can build and test against, drawn from IEC 62443-4-2 and NIST IR 8259.
- Secure development process
The steps that keep security in your product's development, such as security reviews of design changes, checks before a release and a way to handle reported vulnerabilities, based on IEC 62443-4-1.
Process
How an engagement runs
- 01
Agree the scope
We agree which parts of the product are in scope, from the device software to the app and the cloud, which versions we test and who on your team answers technical questions. Nothing is tested without written authorisation.
- 02
Learn the product
Your engineers walk us through how the product works, how a device is set up and updated, and where its data goes. We read the documentation and plan the work around what matters most.
- 03
Assess or design
2 to 6 weeks; design 2 to 4 months
For an assessment, we test the software, app and cloud services and record each finding as we go. For design work, we build the threat model and requirements with your team and fit the process to how you already develop.
- 04
Report and walk through
You receive the report or the design documents, and we walk your engineers through them, so each finding or requirement is understood before anyone starts on it.
Proof
Credentials and partners
Marco Villarruel, Founder & CEO
- CASE
FAQ
Frequently asked questions
How long does it take and how is it priced?
A security assessment of a connected product takes two to six weeks and is fixed price, with what is in scope named before we start. Secure product design work takes two to four months and is priced as a fixed fee or as time and materials. The size of the product sets most of the effort, such as how many device models, apps and cloud services are involved.
A customer or regulator asks for proof that our product is secure. What can we give them?
The assessment report shows what was tested, what was found and how each finding was fixed, and the threat model and security requirements from the design work show how security was built into the product. Both are documents you can share. We don't certify products, and we don't prepare a formal submission against a standard at this time, so if a customer requires a certificate, an accredited body will need to issue it.
Do you test the hardware itself?
Not at this time. Our assessments cover the software side of a product, its firmware, its app, its APIs and its cloud services. We don't open devices, read chips or probe circuit boards. If your product needs hardware testing, we say so when we scope the work, so you can plan for a specialist laboratory alongside us.
Do you secure factory or industrial systems?
Not yet. This service is for companies that build connected products, not for the networks and control systems that run a plant or a production line. For the IT side of a manufacturing business, such as servers, networks and cloud accounts, our other cybersecurity services apply.
Related
Related services
Red Teaming & Penetration Testing
Penetration testing services for web apps, APIs, networks, cloud and Active Directory, plus red teaming. Every test ends with a report and a retest.
ExploreSecurity Governance
We design your information security program on ISO/IEC 27001 and NIST CSF, with policies, risk and metrics reporting, and a process for assessing suppliers.
ExploreThe engagement
- Duration
- 2 to 6 weeks; design work 2 to 4 months
- Pricing
- Quoted for each engagement
An assessment is fixed price. Design work is fixed price or time and materials, agreed in the scope before work starts.
- IEC 62443-4-1
- IEC 62443-4-2
- NIST IR 8259
Next step
Tell us about your connected product
Describe the product, what it connects to and where it is in its life. We reply within two business days.