Chips
Any chip. Any embedded system.
Every modern processor has security built in: a root of trust, crypto engines, one-time fuses and a secure area. It's powerful, and easy to get wrong. Whatever chip your product uses, from a small microcontroller to an FPGA or an AI processor, if it has security features such as a hardware root of trust, we turn them into full protection.
By industry
Chips we see in your industry
A few examples of chips common in each industry. We secure these and any other.
Defense & Aerospace
- AMD Zynq UltraScale+ and Versal
- Altera Agilex
- Microchip PolarFire
- NXP Layerscape
Medical Devices
- STM32
- NXP i.MX RT and i.MX 8
- Nordic nRF
- TI Sitara
Automotive
- NXP S32
- Infineon AURIX
- Renesas R-Car and RH850
- Qualcomm Snapdragon automotive
Robotics & Drones
- NVIDIA Jetson Orin and Thor
- Qualcomm robotics platforms
- NXP i.MX 8M Plus and i.MX 95
- Rockchip
Consumer & Commercial
- Nordic nRF52 and nRF54
- Qualcomm audio SoCs
- Espressif ESP32
- Silicon Labs EFR32
Using something else?
Tell us your chip. If it has security features, we can put them to work.
Proven
Already delivered on
Security packages we have built and delivered on real programs. A new chip family moves faster because we reuse this work.
AMD Zynq UltraScale+ MPSoC
Secure boot, encrypted firmware and FPGA logic, and per-unit keys in production.
NXP i.MX 8 family
Secure boot for embedded Linux, encrypted firmware and AI models, and per-unit keys.
STM32U5
Secure boot and protected firmware and keys on a low-power microcontroller.
Altera Agilex 7
Signed and encrypted FPGA configuration and protected keys on a high-end FPGA.
Why it matters
Why chip-level knowledge matters
Each chip is different.
Mistakes are permanent.
Features don't add up on their own.
Your first step
Start with a free 30-minute security review.
A call with Shaul Shohat, our founder, about your device. You leave with the 1–2 biggest security gaps worth fixing first, and a clear next step.
No cost, no commitment. We sign an NDA if you need one.
What we look at
- 01Your chip: which security features your product uses, and which are still switched off
- 02Your firmware, AI models and keys: at boot, in updates and on the production line
- 03The rules you face: your customer's spec, the EU CRA, FDA 524B or a defense program
