IoT Security Regulation Overload? Your Guide to PSTI, NIS2, & CRA Compliance
summary
UK PSTI engagement runs over the next 12 months and offers an opportunity to change scope and wording rather than a new compliance deadline; standards and enforcement still converge toward a two‑year compliance horizon while many devices have hardware life cycles 1–3 years creating a timing gap. Expect mapping work: the IoT security framework already maps to EN 303 645 and NIST 8259 and has been used in desktop assessments, so using that framework reduces pre‑compliance cost and covers many requirements in PSTI engagement over next 12 months.
AI-written summary · about
chapters (9)
- 0:00IoT security regulations intro
- 1:11PSTI regulation process
- 2:16NIS2 and CRA timeline
- 3:40NIS2 impact on manufacturers
- 4:26Security vs practicality
- 6:10Compliance as business protection
- 7:14Frameworks to cut pre-compliance costs
- 9:03Frameworks to emerging standards
- 10:28Framework alignment with RED
related talks
18mNavigating the galaxy of domestic IoT security standards, legislation and codes
46mThe Perfect Storm, What NIS2 and CRA Mean for Your IT Security Strategy
50mConsumer IoT Security: Creating a Baseline Standard
27mIoT: What will security standards and certification look like ten years from now?
12mIoT Cyber Security Regulations
12mSecure from the Start: Aligning with CRA and Global IoT Regulations
01h 01mNIS2 & CRA: Europe's Response to Cyber Shenanigans
01h 18mEU CRA TL/DR for PSIRTS - What Product Security Needs To Do To Be Compliant with the CRA