Transparent and auditable secure elements. Donβt wait β start building with TROPIC01 DevKits now! https://xitter.cf/t.co/FbtYAoGRHw
Prague
Joined March 2020
- Tweets546
- Following123
- Followers4.4K
- Likes754
π Next month our team takes TROPIC01 devkits to two shows:
π electronica and SEMICON Europa, Munich, 10β13 Nov
β Enlit Europe, Vienna, 10β12 Nov
π TROPIC01 is an auditable hardware root of trust in the form of a secure element, with docs and SDK published without an NDA. Talk through with us where it fits your CRA work.
π Full CRA obligations apply from 11 December 2027. Products designed now will ship under them.
π§ Tomas Prejda is in Munich, and Ε imon Fic is in Vienna. They are bringing devkits to take back to your own bench.
π¬ Message them directly on LinkedIn to set a time to meet.
#electronicafair #SEMICONEuropa #EnlitEurope
π Tomas Prejda will be at @itsa_ITSecurity Expo & Congress in Nuremberg, 27β29 October. Heβll bring TROPIC01 devkits to both.
π¬ In Nuremberg, we are excited to discuss the independent testing of TROPIC01. KU Leuvenβs fault-injection evaluation of the secure element came out in June, and a ΔVUT thesis found the chip passed 1,286 AIS 31 randomness tests.
π§ Weβre also exploring the market fit for our next-generation product. And weβd love to hear what the ideal secure element looks like from your side. Which interfaces, certifications, lifecycle requirements and supply guarantees actually decide your design-in?
π¬ Planning a product line for the market? DM Tomas to set a time.
#itsaexpo
π§ When you write firmware for a secure element, the attack protections live in the source. Whether they survive compilation into the chip is a separate question.
π Read about how we have built AI review into our release checks, plus five tips for teams trying the same: buff.ly/Wfz7hh2
#FirmwareSecurity #EmbeddedSystems
π ABI Research puts secure element shipments at 352M in 2025, rising to 859M by 2029. Those parts will be in the field well into the 2030s. Who reviews that firmware, and with what? 1/3
π§ TROPIC01's application and coprocessor firmware are published on GitHub. When we want a frontier AI model to review them, we point it at our repos.
No new exposure, and no compliance gauntlet for code we've already published. 2/3
π Chapter 1 of our series on AI-assisted secure element development is up, with the rest landing on Wednesdays over the next few weeks. Read it at π buff.ly/FDSVWq8
3/3
π Chapter 1 of our series on AI-assisted secure element development is up, with the rest landing on Wednesdays over the next few weeks. Read it at π buff.ly/FDSVWq8
3/3
π· CAIM1 is building a 4K cinema camera that signs footage at the moment of capture, with the signing keys held in a TROPIC01 secure element rather than software. 1/4
π¬ Their team reviewed the TROPIC01 design before committing to it. Such a review is what publishing our design is for. 3/4
When an edge gateway acts as the local hub for a variety of smart devices, including sensors, cameras, and mesh routing, software-only security models fail if the operating system is compromised.
Thatβs why the @ContentWiseInfo Smart Home system uses the TROPIC01 secure element.
In an era of increasingly connected ecosystems, itβs more critical than ever to look under the hood of the devices powering our smart homes. What features do you value most when securing your own smart spaces, or how would you approach the design of a truly secure edge gateway?