Smart-city programmes put electronics outdoors, on public networks, and in places nobody visits for years at a time. That combination — long service life, physical exposure, and a network an attacker can reach — is what makes municipal deployments different from ordinary industrial work, and it is where Ambimat’s smart-city work is concentrated.
The security layer is what this category currently covers. Listed here is Secure your Smart City Infrastructure, Ambimat’s AmbiSecure solution for LoRaWAN deployments: a system-on-chip plus Ambimat firmware that holds the AppKey, NwkKey and session keys in hardware rather than in the main controller’s memory, generates keys for joining the network server, verifies that firmware arriving over the air is genuinely yours before it is applied, and takes the AES work off the host so you are free to choose the controller that suits the rest of the design.
The practical reason this matters: LoRaWAN’s own specification is strong — two layers of 128-bit session keys, end-to-end payload encryption the network operator cannot read — but it is symmetric cryptography, so the whole model rests on how safely those keys are stored and provisioned. A secure element is the difference between a specification that is secure on paper and a fleet that stays secure after ten years in a street-light enclosure.
If you are scoping a municipal deployment, the questions worth settling early are how devices will be personalised or activated over the air, who holds the root keys, and how you will re-key a fleet you cannot physically reach. Ambimat’s IoT security white papers cover the wider architecture — device identity and lifecycle, zero-trust segmentation, secure OTA, and mesh hardening for Zigbee and low-power 2.4 GHz mesh networks.
