[ COMPLIANCE · SESSIONS ]

Connected Product Compliance: proposed sessions.

Nine proposed sessions for product security, compliance and sourcing teams and buyers. No dates or speakers yet. Add your email and tell us which you would come to.

Tell me when it's on

A bright electronics compliance test lab. Illustrative.

9 proposed sessions · Seattle and online

  1. The 24-hour clock: running a vulnerability report

    Manufacturers must report actively exploited vulnerabilities. What an early warning needs, who signs it, and how a team rehearses it.

    Product security · Proposed

  2. Software bills of materials that regulators can ask for

    What goes in, who keeps it current, and what a buyer can verify.

    Product security · Buyers · Proposed

  3. Access by design: the Data Act rule for new products

    Under the Data Act, new connected products must be designed so users can access their data by default, where relevant and technically feasible. What teams changed in the product.

    Product teams · Proposed

  4. Battery passports: what product makers must show

    Under the EU Battery Regulation, the battery passport is the first digital product passport the EU requires. What product makers must show, and which data they do not yet hold.

    Compliance · Sourcing · Proposed

  5. Connected medical devices: what the FDA expects

    Device makers on threat models, software bills of materials and patch plans in a premarket submission, and how they keep them current after launch.

    Device makers · Proposed

  6. Forced-labor rules: can you trace it to the source?

    What EU rules and US customs ask for, how far back you have to go, and what a batch-level trace looks like on a real product.

    Sourcing · Compliance · Proposed

  7. One product, three regimes: EU, UK and US

    How teams map the EU cyber rules, the UK default-password ban and the voluntary US Cyber Trust Mark onto one design.

    Compliance · Proposed

  8. Test labs, tracers and consultants: who was worth it

    A buyer panel on what they bought for compliance, what it delivered and what they did not need.

    Buyers · Proposed

  9. Over-the-air updates for cars and e-bikes: who owns the risk

    Vehicle and e-bike makers on update rules, rollback and what happens when an update leaves a rider unable to use the bike.

    Firmware leads · Proposed

  10. What should we cover next?

    Tell us the one problem you want solved. The most-asked ones become sessions.

    You pick · Tell us

IoT Hub Meetup · Thing Company, LLC · © 2026

iothubmeetup.com · Events · Privacy · Terms