IoT marketing for B2B hardware makers is mostly a documentation problem. If you sell IP cameras, gateways, industrial sensors, smart building controllers or any other connected device to businesses and public bodies, the deal rarely turns on your launch video. It turns on whether a security reviewer, an integrator and a procurement officer can each find the proof they need, for their market, without waiting for a sales call. This guide covers who buys connected hardware, the certification rules that differ by region (the EU Cyber Resilience Act, the UK's PSTI regime, India's STQC testing for CCTV cameras and US federal procurement rules), the proof pages buyers look for, and how to segment and personalize your website so each visitor sees the evidence that applies to them.
A note before we start: this is a marketing guide, not legal or compliance advice. Where we summarise a regulation, we link the source. Have your compliance team confirm what applies to your products.
Our View: The Security Reviewer Is Your Real Audience
Most hardware websites are written for the person who will use the device: the facility manager, the plant engineer, the city's traffic team. That person matters, but in a connected-hardware deal they are rarely the one who can stop it. The device sits on someone's network. So before it is bought, someone in IT or OT security asks how it authenticates, which ports it opens, how firmware is updated and how long it will get patches. In regulated markets and public tenders, someone else checks whether it holds the certificates the rules require.
Our position: for an IoT OEM, the security, certification and support-period pages are conversion pages, not legal footnotes. A buyer who cannot find a test report or a vulnerability disclosure policy does not email you to ask. They move to the vendor whose documentation answered the question in five minutes. We would rather see a hardware company spend a quarter fixing its trust pages than a quarter producing another product teaser.
Who Buys Connected Hardware
A connected-device purchase usually involves more roles than a software purchase, because someone has to install it physically and someone has to approve it on the network. Our glossary entry on the buying committee covers the general idea; this is how it looks for hardware.
| Role | What they check | What they need from your website |
|---|---|---|
| System integrator or installer | Compatibility, installation effort, margin, support quality | Integration docs, protocol support, partner programme, spec sheets they can paste into a bid |
| IT or OT security | Authentication, encryption, exposed services, firmware updates, patch history | Security overview per product line, vulnerability disclosure policy, security advisories |
| Procurement and tender teams | Mandatory certificates, country of origin, contract terms | Certification matrix by product and market, downloadable test reports, tender pack |
| Operations owner (facilities, plant, public safety) | Does it solve the problem, reliability, total cost | Use cases by industry, reference sites, cost and lifetime information |
| Distributor or reseller | Which products are approved in which countries | Market availability per model, marketing assets, price list access |
Two of the five rows are mainly about proof, not product benefits. That is the mismatch most hardware sites have: the homepage speaks to the operations owner, and everyone else hunts through PDFs.
Certification Requirements Differ by Market
The same camera or gateway can face different rules in each market it is sold in. A buyer only cares about their own market, which is why a single global "Compliance" page with twenty logos rarely helps anyone. Here is a short overview of the rules that most often come up for connected products.
European Union: the Cyber Resilience Act and the radio rules
The EU Cyber Resilience Act entered into force on 10 December 2024. The obligation to report actively exploited vulnerabilities applies from 11 September 2026, and the main obligations apply from 11 December 2027. It sets cybersecurity requirements for products with digital elements across their design, development and maintenance, requires manufacturers to handle vulnerabilities over the product's lifecycle, and products that comply will carry the CE marking to show it. Some product categories need a third-party assessment by a notified body.
Radio products have an earlier deadline. The cybersecurity requirements of the Radio Equipment Directive, activated by Delegated Regulation (EU) 2022/30, apply from 1 August 2025 to in-scope internet-connected radio equipment, with the EN 18031 series as the harmonised standards. For a European buyer in 2026, "is it CE marked" now includes a cybersecurity question.
United Kingdom: PSTI
The UK's product security regime under the PSTI Act came into effect on 29 April 2024. For consumer connectable products it requires three things: passwords that are unique per device or set by the user, a published way to report security issues, and a published minimum period for security updates. Even B2B makers whose products can also reach consumers end up publishing these statements, and business buyers have started asking for them too.
India: STQC testing for CCTV cameras
India is the clearest example of a market where one certificate decides whether you are even on the shortlist. The Ministry of Electronics and IT (MeitY) set essential security requirements for CCTV cameras in 2024, and testing against them sits with labs under the STQC Directorate. Buyers in India's public procurement look for STQC-certified cameras before they compare image quality or price, so a camera maker without a valid test report is out of government tenders regardless of how good the product is. The lab checks authentication on every management interface, default passwords, open ports and services, encrypted communication, signed firmware updates and exposed debug interfaces. Camera makers without in-house security engineering often bring in an embedded engineering partner such as Silicon Signals, whose STQC camera solution prepares devices for these tests.
The rules reach beyond tenders. As Khaitan & Co summarises, MeitY's April 2024 amendment to the compulsory registration order brought the essential security requirements into the registration that CCTV cameras need before they can be sold in India. Implementation dates have been moved more than once since then, so check the current notification before you put a date on your website.
United States: federal procurement
US federal buyers ask a different question first: who made it. FAR 52.204-25, which implements Section 889 of the 2019 National Defense Authorization Act, restricts federal contracting involving telecommunications equipment from Huawei and ZTE, and video surveillance and telecommunications equipment from Hytera, Hikvision and Dahua used for public safety, government facility security and similar purposes. If your products and components are clear of these, a short, specific "Section 889" statement saves every federal integrator a round of emails.
Industrial and building automation
For industrial control and building systems, buyers often reference the IEC 62443 series, and consumer-facing devices are commonly measured against ETSI EN 303 645. Neither is a market-entry law in itself, but both show up in tender specifications and security questionnaires, so say plainly which parts you have assessed and by whom.
What Most IoT Makers Get Wrong
- Certificates as logos. A row of badges in the footer tells a reviewer nothing. Which models? Which firmware version? Issued when, valid until when, by which lab? A logo without a document behind it reads as decoration.
- Everything gated. Putting the security whitepaper behind a full lead form feels like lead generation, but the person downloading it is usually a reviewer who will never talk to sales. Gate the tender pack if you want, with three fields. Leave the security overview and disclosure policy open.
- One global page. An Indian integrator, a German municipal buyer and a US federal contractor each scroll past two thirds of a global compliance page to find their row. Many give up.
- No support period. Buyers now plan around how long a device will receive security updates. If you do not say, they assume the worst.
- Silence about vulnerabilities. A published advisory history with fixes looks more trustworthy than no history at all. Reviewers know every product has bugs.
The Proof Pages a Hardware Buyer Looks For
- Security overview per product line. Authentication options, encryption in transit and at rest, which services are on by default, how firmware is signed and updated, and how to harden the device. Write it for the reviewer, with real settings, not adjectives.
- Certification matrix. Rows are products, columns are markets, cells name the certificate or statement and link the document. See the example below.
- Vulnerability disclosure policy and advisories. How to report an issue, response timescales, and a list of past advisories with affected versions and fixes.
- Support and end-of-life page. The security update period per model, with end dates.
- Integration documentation. Protocols and platforms you support, with versions. For cameras that usually means ONVIF profiles and video management systems; for industrial devices, the fieldbus and messaging protocols.
- Tender pack. Spec sheets, test reports, declarations of conformity and origin statements in one download, per market.
- Industry pages. Use cases and reference sites by vertical, written for the operations owner.
Example certification matrix for an invented camera maker (illustrative, not a statement about any real product):
| Product | EU | UK | India | US federal |
|---|---|---|---|---|
| Dome camera, 4 MP | CE declaration incl. RED cybersecurity (EN 18031) | PSTI statement of compliance | STQC essential requirements test report | Section 889 statement |
| Bullet camera, 8 MP | CE declaration incl. RED cybersecurity (EN 18031) | PSTI statement of compliance | Testing in progress, expected date stated | Section 889 statement |
| Network video recorder | CE declaration | PSTI statement of compliance | Not sold in this market | Section 889 statement |
The "testing in progress" and "not sold in this market" cells matter as much as the certified ones. They save a buyer from asking and a salesperson from guessing.
Segmenting the Site by Industry, Role and Region
Once the proof exists, the next job is getting each visitor to their part of it. For connected hardware, three dimensions do most of the work.
Industry. A hospital, a factory and a city traffic department buy the same camera for different reasons and under different rules. Swap the hero, use cases and reference sites by industry. Our guide to industry-specific website personalization covers how to choose verticals and what to change for each, and the B2B healthcare marketing guide shows how one regulated vertical breaks down by buyer.
Role. Integrators, security reviewers and procurement teams arrive through different doors: integrators through spec sheets and partner pages, reviewers through the security overview and advisories, procurement through tender packs. Use those entry points to change the call to action, as described in our post on personalizing a B2B website by job title and role. A reviewer on the security page should see "Download the security overview", not "Book a demo".
Region. This is where hardware differs most from software. The visitor's country decides which certificates they need, so the proof strip on product pages can follow it: an Indian visitor sees STQC and registration status first, an EU visitor sees CE, RED cybersecurity and the support period, a UK visitor sees the PSTI statement, and a US public-sector visitor sees the Section 889 statement. Two rules keep this honest. First, country from an IP address is the location of the visit, not always the buyer's market (integrators bid across borders), so the full matrix stays one click away for everyone. Second, personalization only reorders and highlights. Never hide a market's compliance status from anyone, and never show a certificate you do not hold.

Illustrative example
Example, with an invented company and round numbers. A maker of network cameras, "Northlight Vision", sells in Europe and India through integrators. Its product pages show the same badge row to everyone, and its tender pack sits behind a ten-field form. Of roughly 2,000 monthly visits to product pages from India, about 40 reach the compliance page and 5 request the tender pack.
Changes: visitors from India see a proof strip at the top of each product page with the STQC test status per model and a three-field tender pack request. EU visitors see the CE and RED cybersecurity declaration, the security update period and a link to the disclosure policy. Visitors who arrive on the security overview get "Download the security overview" as the main action. The full matrix stays linked from every page.
What to measure: tender pack requests per visiting integrator or agency, security overview downloads, and time from first contact to security approval. If tender pack requests from India move from 5 to 15 a month, that is three times as many chances to be named in a bid. The numbers are illustrative; the point is to measure proof consumption, not page views.
Running This on Your Website
Two capabilities are needed: knowing which organisation and market a visit comes from, and changing the page for it. Markettailor's visitor identification shows which integrators, agencies and enterprises are researching your products, and its segmentation builds audiences by industry, company size, location and behaviour, so the proof strip, hero and call to action can follow each segment. Any personalization tool that can segment by country and firmographics will do the same job; the hard part is the content kit, not the tooling.
A sensible order of work:
- List your products and markets, and fill in the certification matrix honestly, including the gaps.
- Publish the security overview, disclosure policy and support periods as open pages.
- Build one tender pack per market with a short form.
- Add a region-aware proof strip to product pages, starting with your two largest markets.
- Change the main call to action on security and integration pages by entry point.
- Review the matrix every quarter and whenever a certificate is issued, renewed or a deadline moves.
Frequently Asked Questions
What is IoT marketing?
IoT marketing is the marketing of connected devices and the platforms around them. In B2B it means selling hardware such as cameras, sensors, gateways and controllers to businesses and public bodies, where security reviews, certification and integration documentation weigh as much as product features.
Which security rules matter for connected products sold in the EU?
Two sets come up most often. The Radio Equipment Directive's cybersecurity requirements have applied to in-scope internet-connected radio equipment since 1 August 2025. The Cyber Resilience Act entered into force on 10 December 2024, with vulnerability reporting obligations from 11 September 2026 and its main obligations from 11 December 2027. Confirm with your compliance team which apply to each product.
Is STQC certification required for CCTV cameras in India?
For government procurement, buyers look for cameras tested against MeitY's essential security requirements by STQC labs. MeitY has also brought those requirements into the compulsory registration that CCTV cameras need to be sold in India, with implementation dates that have moved over time, so check the current notification.
Should IoT companies gate their security documentation?
Keep the security overview, vulnerability disclosure policy and support periods open, because the people reading them are reviewers who rarely talk to sales. A short form in front of a full tender pack is reasonable, since requests for it signal an active bid.
How do you personalize a website by region without hiding compliance information?
Use the visitor's country to choose which certificates and statements appear first, but keep the full certification matrix linked from every page. Personalization should reorder and highlight proof, never remove another market's status or show a certificate the product does not hold.