WISeKey International Holding Ltd, announced that its subsidiaries, SEALSQ Corp and WISeSat AG have joined forces to create an ultra-secure picosatellite solution for Quantum-Ready internet of things (IoT) communications.
The initiative will leverage the integration of the VaultIC408 secure element to secure each endpoint within the network, ensuring top-tier security levels throughout. Leveraging their advanced miniaturisation techniques, the collaboration between both companies aims to provide solutions able to reduce costs and increase accessibility, so that businesses of all sizes can afford dedicated satellites to provide connectivity to their ecosystems.
Seventeen WISeSat-ready satellites have already been launched into orbit with SpaceX as part of an 80-satellite constellation. These satellites are able to deliver global and real-time IoT connectivity for industrial applications, featuring a remarkable data latency of only 10 hours.
Through the SEALSQ and WISeSat collaboration, the new generation of WISeSat-ready satellites will incorporate post-quantum solutions, with microchips and devices designed to withstand the development of computational power. These post-quantum devices can be utilised in good range of applications, such as multi-factor authentication devices, to ensure uncompromising data security in the quantum age.
This collaboration underscores the commitment of both companies to develop a practical solutions in response to the evolving challenges of the digital world. It marks a significant step forward in the creation of quantum-ready IoT systems that provide secure and real-time connectivity across the globe.
Viewers can go here, to track in real-time our WISeSats-ready Fossa Satellites circling Earth. Global coverage is provided by a single satellite. The revisit time of a single satellite is approximately 24 hours, so depending on the latency of the information required, application will need more or fewer satellites. A constellation of 60 satellites provides a revisit time of 5 minutes.
Comment on this article below or via Twitter: @IoTNow_OR @jcIoTnow