Educational audit

IoT Security Scorecard

An educational tool that takes you through the shape of a security audit for your connected-product deployment. You pick the archetype and markets; the tool resolves which regulatory frameworks apply and tailors the assessment accordingly.

Not a compliance tool. This scorecard is for orientation and learning. Formal assessment requires a qualified assessor and the authoritative standards themselves.

B+ Sample

Worked example: a Philips Hue Bridge

Signify's Philips Hue Bridge is the hub that turns a box of Zigbee bulbs into a system: it holds the mesh, talks to the app on the local network, and reaches the cloud for remote control and voice assistants. Sold in the EU and the UK, it is archetype 3, gateway + sensor fleet, in a home environment. Here is how the scorecard would work through it.

1. Screener and regulatory scope

Archetype 3 at home selects the consumer bank of 19 questions. With EU and UK as markets, the resolver returns ETSI EN 303 645, the EU Cyber Resilience Act, GDPR and the UK PSTI Act. Had the same bridge been deployed as a building-automation gateway, the tool would have escalated it to the composite bank (7 more questions on the management layer) and added the 5-question OT supplement, because a gateway managing a fleet in an industrial setting behaves like a general-purpose computer.

2. Answers

The answers below are a plausible reading of a Zigbee hub from public documentation. They are not Signify's audited posture, and the grade is not a verdict on the product. The point is to show what each answer does to the score.

CategoryAnswersPoints
Identity & accessStrong password at setup (2), optional 2FA off by default (1), lockout after repeated failures (2), keys in a protected partition (2)7 / 12
Software updatesAutomated signed OTA (3), signed with the manufacturer key (2), automatic rollback (2)7 / 9
Data protectionMixed on-device and cloud processing (2), core data plus opt-in analytics (2), account dashboard (2)6 / 9
CommunicationNo internet-facing admin interface (3), per-device Zigbee keys with pairing (2), segmentation documented but not enforced (1)6 / 9
ResilienceLights keep working without the cloud (2), basic logging only (1), systematic input validation (2)5 / 9
ComplianceFormal disclosure policy (2), ad-hoc pen test (1), internal component list, no SBOM (1)4 / 9
Total35 of 57 points, 61%C

3. Flags and ceilings

One mandatory flag fires: the CRA's SBOM obligation (Annex I, Part II, 1), because the component list is not in a standard format. No ceiling applies. Change one answer, though, and the arithmetic stops mattering: ship with a universal default password and the grade is capped at C− regardless of the other 18 answers, because PSTI Schedule 1 paragraph 1 bans the product from the UK market outright. Remove the update mechanism and the cap is C, because the CRA's secure-update requirement cannot be met.

4. What to do with a C

The category table tells you where the points are. Here, mandatory 2FA and a hardware secure element lift identity and access from 7 to 11; a CycloneDX SBOM in the build pipeline clears the flag and adds two points; security event logging with alerting adds two more. That is eight points, 43 of 57, a B, from three work items. The requirements generator writes those items up, with owners and clause citations.

When to use this, and when not

Use it when

Do not use it when

Frequently asked questions

How is the IoT Security Scorecard grade calculated?

Each applicable question scores 0 to 3 points. The total is divided by the maximum to give a percentage, which maps to a letter grade from A (90% and above) to F (below 45%). Two critical failures then cap the grade regardless of the percentage: a universal default password caps it at C-, and no update mechanism caps it at C.

Which standards is the scorecard aligned with?

The 19 consumer questions follow the provisions of ETSI EN 303 645. Regulatory flags cite the EU Cyber Resilience Act, the UK PSTI Act and GDPR. Composite products add CIS Controls v8, and industrial deployments add IEC 62443-4-2 and NIS2. Each flag names the clause it comes from.

What is a regulatory flag?

A flag is an answer that, on its own, puts you on the wrong side of a specific legal or standards clause in one of your target markets. Mandatory flags are market-access issues; advisory flags are expectations you will meet in procurement. Flags are listed separately from the grade because a B product with a mandatory flag still cannot ship.

Can I embed the scorecard on my own site?

Yes, and for free. The iframe snippet below renders the tool without site chrome, with attribution built in. No permission is needed and your readers do not have to sign up.

Is the grade a compliance result?

No. It is an educational orientation. It tells you which of the 19 areas need work and which clauses you would be measured against, so you can brief an assessor and prioritise a backlog. Formal assessment needs the authoritative standards and a qualified assessor.

Go further

Use this on your own site

This tool is free to embed — on a company blog, a course page, a standards resource list. No permission needed and no sign-up for your readers. Attribution is built into the embedded view.

<iframe src="https://tangibles-book.com/tools/iot-security-scorecard?embed=1"
        width="100%" height="720" style="border:1px solid var(--color-border);border-radius:8px"
        title="IoT Security Scorecard — Tangibles" loading="lazy"></iframe>

Prefer a plain link? The press kit has a link-only snippet, cover art, and book facts.