Author Archives: saesoltech

Fast Enough, Too Big: Post-Quantum Signatures on the Road

Fast Enough, Too Big: Post-Quantum Signatures on the Road 

On a Raspberry Pi 5, post-quantum cryptography (PQC) signatures proved fast enough for vehicle-to-everything (V2X) communication, but most of them are too large for a single wireless message. Only two of the seven PQC configurations we measured fit in one message when the certificate is attached. In both, the vehicle keeps signing with the Elliptic Curve Digital Signature Algorithm (ECDSA), and PQC is applied only to the signature of the certificate authority (CA). 

This report presents the results and their implications. You can compare PQC signature options for V2X by speed and size, assess the effect on pseudonym certificate issuance, and see where standardization and Korean validation stand.

Why V2X Needs PQC

V2X trust rests on digital signatures, and the quantum threat to ECDSA makes PQC a requirement for V2X. 

Why Every Message Is Signed 

V2X lets vehicles in Cooperative Intelligent Transport Systems (C-ITS) communicate with a wide range of external parties: other vehicles and fixed devices such as roadside units (RSUs), including traffic lights and roadside devices that gather road information. These parties cooperate rather than act independently, allowing the transport network to operate more intelligently. 

That cooperation works only if each party can trust the messages it receives. V2X establishes that trust with digital signatures: every Basic Safety Message (BSM) a vehicle broadcasts, for example, carries one. From the signature, the receiver can confirm that the sender holds a valid certificate and that the content was not altered in transit.

The Quantum Clock on ECDSA 

V2X signatures have been based on ECDSA, whose small size and good speed suit mostly wireless environments. 

Quantum computing threatens ECDSA and the other public-key schemes in use today, and V2X is no exception. Once a cryptographically relevant quantum computer (CRQC) emerges, receivers can no longer be sure that a V2X message is authentic, and the trust underpinning the whole domain will be undermined. PQC is the family of algorithms for which no weakness against quantum attack is known. 

Three Regions, Three Timelines 

Governments are already setting timelines: 

  • The United States requires major federal systems to move digital signatures to PQC by the end of 2031. 
  • Europe targets a full transition by the end of 2035. 
  • In Korea, the National Intelligence Service announced the PQC schedule for its cryptographic module validation program in September 2026. 

PQC support is no longer optional. 

The Two Contenders: ML-DSA and FN-DSA 

The first question for V2X is whether PQC signatures keep the two advantages of ECDSA: small size and good speed. To answer it, Saesol Tech integrated two PQC signature algorithms into its own implementation of the IEEE 1609.2 standard, which defines V2X message signatures and certificate formats. It benchmarked them across a range of configurations. The two algorithms are: 

  • ML-DSA (Module-Lattice-Based Digital Signature Algorithm), standardized as Federal Information Processing Standard (FIPS) 204. 
  • FN-DSA (FFT over NTRU-Lattice-Based Digital Signature Algorithm), to be standardized as FIPS 206. 

Speed Is Not the Problem 

Even the heaviest combination uses at most 3% of the 100 ms budget for signing, and five of the seven PQC configurations verify more messages per second than ECDSA. 

The 100 ms Test 

A vehicle broadcasts 10 BSMs per second, so each message must be processed within 100 milliseconds (ms). In practice, the allowance is far smaller, because a vehicle communicates with many surrounding parties. Even so, we measured how much of the 100 ms one message consumes and how much headroom is left. The more headroom there is, the more peers a vehicle can serve before processing becomes a bottleneck. 

Verification runs more often than signing: a vehicle signs only its own messages, but must verify every message it receives from the parties around it. We therefore report verification as throughput, in messages verified per second, relative to current ECDSA. Table 1 lists the vehicle’s signature algorithm together with the signature algorithm of the CA that issued the vehicle’s certificate. 

The Numbers: Signing and Verifying 

Signing time and verification throughput 

The Real Bottleneck Is Size 

These results come from a Raspberry Pi 5 rather than an on-board unit (OBU) in a vehicle; measuring on commercial C-ITS devices is future work. Signing with even the heaviest combination takes no more than 3% of the 100 ms budget, leaving at least 97% headroom. Verification is faster still: ML-DSA-44 verifies 2.76 times as many messages per second as ECDSA. Taken together, PQC performs comparably to today’s ECDSA and, in several configurations, better. The exceptions are the two composite configurations, which verify fewer messages per second than ECDSA (0.50× and 0.95×). PQC is often assumed to be slow. Here, size rather than speed is the real constraint. 

Inside a 10-Hz Heartbeat Message 

A BSM passes through three layers on its way out, and only three values in the final message change size with the signature algorithm. 

Three Layers, One Message 

Message size depends on how a BSM is packaged for transmission, a process defined by three standards: 

  1. 1. The vehicle’s state, such as its position, speed, and heading, forms the BSM payload (SAE J2735). 
  1. 2. The vehicle signs the payload, producing the signed message defined in IEEE 1609.2: the Secured Protocol Data Unit (SPDU). The SPDU holds the payload and the vehicle’s signature, together with the signer’s certificate, so a receiver can verify a message from a sender it has not encountered before. The certificate, in turn, contains the vehicle’s public key and the CA’s signature. 
  1. 3. The SPDU is carried in a WAVE Short Message (WSM), the unit of wireless transmission (IEEE 1609.3). 

Three Values That Grow with PQC 

How a BSM is carried in a WSM 

As Figure 1 shows, three values, marked in blue, change size with the signature algorithm: the vehicle’s public key, the CA’s signature, and the vehicle’s signature; everything else is independent of the algorithm.

The 1,400-Byte Ceiling 

A WSM holds 1,400 bytes (B) by default and at most 2,302 B even after a configuration change. With ECDSA, the SPDU including the certificate is 333 B, which leaves ample room. 

One Message, Too Many Bytes 

Replacing ECDSA with PQC grows the SPDU from 333 B to between 937 B and 12,195 B, and only two measured combinations fit in a single 1,400 B WSM. 

ML-DSA: Nothing Fits 

With PQC, each of the three algorithm-dependent values grows to somewhere between a few hundred bytes and several kilobytes (KB). Even ML-DSA-44, the smallest ML-DSA variant, produces a 6,331 B message when used for both signatures, 19 times the ECDSA size and well beyond both WSM limits, the 1,400 B default and the 2,302 B maximum. Using ML-DSA for both signatures takes 5 fragments (ML-DSA-44) to 9 (ML-DSA-87). No ML-DSA parameter set fits in a single WSM in any configuration, including those that use different algorithms for the CA signature and the vehicle signature. 

FN-DSA: The Alternative to ML-DSA 

ECDSA’s small size does not carry over to PQC, so staying within a single WSM calls for a smaller scheme. The alternative to ML-DSA is FN-DSA, which is not yet fully standardized. 

Every Combination, Byte by Byte 

SPDU size by signature combination 

Two Algorithms, One Message 

When the vehicle signs with ECDSA and only the CA signs with FN-DSA-512, the message is 937 B and fits in one 1,400 B WSM. 

Two Designs That Fit 

Using FN-DSA for both signatures still exceeds the single-WSM limit: when the vehicle and the CA both sign with FN-DSA-512, the message is 2,408 B. Two other configurations fit: 

  • Role split. The vehicle signs with ECDSA, and only the CA signature on its certificate uses FN-DSA-512. The message is 937 B. 
  • Composite dual signature. The CA signature combines ECDSA and FN-DSA-512. The message is 1,002 B. 

Both fit, but each comes with two caveats: 

Caveat 1: The Vehicle Signature Stays Quantum-Vulnerable 

The vehicle’s ECDSA signature remains exposed to quantum attack. 

Signatures face a different quantum threat from encryption. Encrypted data is at risk from “harvest now, decrypt later” (HNDL) attacks. In contrast, signatures are at risk from “trust now, forge later” (TNFL): a signature or certificate that receivers trust today can be forged once a CRQC emerges. The longer a key must stay trusted, the greater the risk. Vehicle certificates are generally short-lived, which keeps the window for an attacker relatively small. CA certificates matter more and stay in use longer, so it is reasonable to apply PQC signatures to CA certificates and keep ECDSA, with its existing efficiency, on the vehicle. 

Caveat 2: The Standard Isn’t Final 

FN-DSA standardization is not complete. 

Even so, moves toward using it in V2X are already visible, and commercial products with experimental support could appear before standardization is finished. 

Sending an ID Instead of a Certificate 

In our measurements, a vehicle and CA that both sign with FN-DSA-512 and attach their certificates produce a 2,408 B message, which exceeds one WSM. Sending only the certificate identifier in place of the certificate reduces this to 797 B, which fits. The receiving vehicle must then already hold the sender’s certificate, so a separate path for delivering certificates apart from messages is needed, along with a protocol to run it. Defining that delivery method and validating it in scenarios such as RSUs is future work. 

3,120 Certificates, One Privacy Problem 

Standard PQC signatures make bulk issuance of pseudonym certificates less efficient and weaken privacy, unless PQC is applied only to the CA. 

Why Vehicles Carry Thousands of Certificates 

Beyond signing and verifying messages, V2X must also issue certificates efficiently. Privacy protection is an important requirement in V2X, so vehicles are issued short-lived pseudonym certificates in large quantities. A vehicle changes the certificate it uses about once a week, receives 20 certificates for each week, and picks one of the 20 at random whenever it needs one. The intent is that no one can trace a certificate back to the vehicle’s real identity from the certificate alone. 

How Butterfly Keys Keep Requests Small 

A vehicle that requests three years of certificates at once receives 3,120. To issue that many efficiently, the current Security Credential Management System (SCMS), the V2X certificate management infrastructure, uses a technique called butterfly key expansion: 

  1. 1. The vehicle generates one public-private key pair and uploads the public key. 
  1. 2. The server derives the public keys for thousands of certificates from it and issues the certificates. 
  1. 3. The vehicle computes the private key for each certificate itself. 

This works because elliptic curve public keys can be added together. Standard ML-DSA and FN-DSA keys do not have this property. 

What Happens Without Butterfly Keys 

Without butterfly key expansion, the vehicle must generate a key for every certificate it requests and upload each one. For 3,120 certificates, the upload grows from 49 B (including one public key) to about 3.9 mebibytes (MiB) with ML-DSA-44, and it keeps growing in proportion to the number of certificates. 

When Privacy Starts to Leak 

Privacy also weakens. SCMS is not a single server: the registration authority (RA) and the authority that issues pseudonym certificates (ACA) have separate roles and issue certificates together. With ECDSA today, linking a pseudonym certificate to a real identity requires the RA, which knows the vehicle’s identity, to collude with the ACA. With PQC, uploading large numbers of public keys in plaintext lets the RA link certificates to identities on its own. 

This privacy loss applies when the public keys are uploaded in plaintext. Encrypting them so that only the ACA can read them was not evaluated here, but it merits further study. 

How the Role Split Sidesteps It 

Accepting the privacy loss is not the only option. The role split described in “Two Algorithms, One Message”, with PQC on the CA signature only and ECDSA on the vehicle, also works here: vehicle keys stay ECDSA, so butterfly key expansion still works. The vehicle again uploads a single public key, and only the download of the larger certificates grows.

Where the Standard Stands 

The IEEE 1609 working group (WG) considered a role-split interim option in April 2026 and decided in July 2026 to submit a Project Authorization Request (PAR) for a PQC amendment to IEEE 1609.2. 

April 2026: An Interim Option on the Table 

In April 2026, the WG considered an interim option in which the vehicle keeps signing BSMs with ECDSA and only the CA that issues its certificate signs with Falcon-512 (April 2026 meeting materials). The WG estimated that converting everything to PQC would increase the data a vehicle sends by about 7 times, against only about 2.2 times for this option. This is the same structure as the role split in “Two Algorithms, One Message”, and the measurements in this report show that it fits in a single WSM. 

July 2026: The Work Gets Formal 

In July 2026, the WG voted to submit a PAR for a PQC amendment to IEEE 1609.2 (July 2026 meeting materials). The PAR itself does not select an algorithm; the direction on algorithms comes from a work proposal at the same meeting, which is still at the proposal stage: 

  • It adds FN-DSA and SLH-DSA (Stateless Hash-Based Digital Signature Algorithm), instead of ML-DSA, for CA signatures. 
  • The stated reason is that FN-DSA is the likely choice if vehicles adopt PQC signatures, so the verification code can align on a single algorithm. 
  • It states that this direction depends on the publication of FIPS 206. 

  • The PQC signature for vehicles is not yet decided. The presenter expects PQC support to be required in vehicles around 2032. 

Korea’s Road to Validated PQC 

Korea’s cryptographic module validation program (KCMVP) does not yet validate PQC signatures, but products that include PQC can already be certified. 

Korea’s Plan at a Glance 

A government plan already exists: the joint-ministry Comprehensive Plan for the Transition to a Pan-National Post-Quantum Cryptography System, September 2025. In September 2026, the National Intelligence Service announced AIMer, HAETAE, ML-DSA, and SLH-DSA as the candidate digital signature algorithms; FN-DSA is not among them (Notice on Candidate PQC Validation Targets and Schedule, September 1, 2026). The schedule is: 

  • January 2028: validation targets are selected. 
  • One year after selection: validation begins. 
  • Two years after selection: inclusion of PQC becomes mandatory. 

Certification Before Validation 

Products with PQC can be certified before validation begins. Under the current standard, PQC counts as a function outside the validation scope (a non-security function), may be included in hybrid form, and may operate in validated mode (Cryptographic Module Implementation Guide Part 1, Annex C.5, National Intelligence Service and others, December 2025). 

Built to Swap Algorithms 

FN-DSA is not on the Korean candidate list, but the September 2026 notice says the list may expand. Crypto-agility, a design that allows swapping the algorithm later, will become a practical requirement. 

Three Realistic Paths Forward 

PQC cannot replicate today’s pure single-algorithm design, in which ECDSA serves every case. This is partly because replacing the existing network infrastructure wholesale to absorb the size increase is out of reach. 

Pick the Algorithm by Layer 

Without a single-algorithm design, the question becomes which algorithm to use at which layer and for what purpose. The answer depends on how long a certificate remains valid and whether a given layer can handle the added size. The realistic options are: 

  • Protect the long-lived certificates. Keep ECDSA for pseudonym certificates in the wireless segment, and apply PQC to enrollment certificates delivered over wired links. Enrollment certificates stay in use for a long time, so they are more exposed to the TNFL threat, whereas pseudonym certificates change about once a week, which makes the quantum threat to them relatively small. 
  • Adopt PQC and standardize fragmentation. Adopt PQC signatures together with a standardized way to fragment and reassemble messages, and leave the privacy weakened by plaintext uploads as a topic for further research.

  • Test the role split, then decide. Implement and evaluate the FN-DSA role split first, since it satisfies the size limit, and decide on deployment after FIPS 206 is finalized and IEEE 1609.2 is amended. 

Making the Case for FN-DSA 

Every measured PQC combination that fit in one WSM used FN-DSA-512, yet FN-DSA is not standardized and is not on the Korean candidate list. Ahead of FIPS 206, the IEEE 1609.2 amendment, and Korea’s selection of validation targets, the industry needs to make the case for FN-DSA in V2X, backed by measurements. 

Signature Algorithms 

Algorithm Full form Standard 
ECDSA Elliptic Curve Digital Signature Algorithm — 
FN-DSA FFT over NTRU-Lattice-Based Digital Signature Algorithm FIPS 206 (planned) 
ML-DSA Module-Lattice-Based Digital Signature Algorithm FIPS 204 
SLH-DSA Stateless Hash-Based Digital Signature Algorithm FIPS 205 

Glossary 

Term Full form Description 
Butterfly key expansion — A technique that lets a vehicle request thousands of certificates while uploading only one public key: the server derives a separate public key for each certificate, and the vehicle works out each matching private key itself. 
Composite signature — A signature that carries two signatures together: one from the method used today and one from a quantum-resistant method. Also called a composite dual signature. 
FIPS Federal Information Processing Standard A series of U.S. government standards. Each standard has a number, such as FIPS 204 for the signature method ML-DSA. 
Fragmentation — Splitting a message that is too large for one wireless transmission unit (a WSM) into smaller pieces (fragments). The receiver puts the pieces back together. 
IEEE 1609.2 — The standard that defines how V2X messages are signed and secured, including the format of certificates. The signed message it defines is called an SPDU. 
KCMVP Korea’s cryptographic module validation program Korea’s program that validates cryptographic modules, meaning the hardware or software that performs signing and encryption. 
PQC post-quantum cryptography Cryptographic methods for which no weakness against attacks by quantum computers is known. 
Pseudonym certificate — A short-lived certificate designed so that it cannot be traced back to the vehicle’s real identity from the certificate alone. A vehicle holds many of them and regularly changes the one in use. 
Role split — A design in which the vehicle keeps signing with the method used today, and only the signature of the organization that issued its certificate uses a quantum-resistant method. 
SPDU Secured Protocol Data Unit The signed message in V2X. It bundles the message content, the sender’s digital signature, and the sender’s certificate, so a receiver can check it even if it has never met the sender. The WSM is the container that carries it over the air. 
TNFL trust now, forge later A threat to signatures: a signature or certificate that receivers trust today can be forged later, once a powerful enough quantum computer exists. The longer a key must stay trusted, the greater the risk. 
WSM WAVE Short Message The container that carries a signed message (an SPDU) over the wireless link. It has a size limit, so a larger signed message must be split into pieces. 

S2X ZeroLink

PRODUCTS

S2X ZeroLink

Zero Trust Network Access that securely connects only what’s needed — from people to

drones, robots, and AI.

S2X ZeroLink

Zero Trust Network Access that

securely connects only what’s needed


S2X ZeroLink is a Zero Trust Network Access (ZTNA) solution that extends secure authentication and encrypted connectivity into a Zero Trust-based access control framework.

It supports a wide range of endpoints beyond users and PCs—including IoT/OT devices, robots, and drones—and integratesidentity verification, access control, encrypted connectivity,auditing, and post-access monitoring within a single platform.

Key Functions


Identity-BasedAuthentication

User and device identification and authentication, with account authentication and MFA integration

Policy-Based Access Control

Group- and role-based access control with support for Default Deny, SDP, andmicrosegmentation

Secure Encrypted Connectivity

Secure network connectivity tailored to diverse environments, including Direct, NAT Relay, and VPN Gateway

Centralized Policy Management & Monitoring

Centralized management of identities, access policies, and connection status, with auditing and logging of access and policy changes

Do more with connectivity


S2X Tester 2.0: A Scalable and Versatile Test Automation Platform

Test automation has become a key competitive advantage that directly impacts product quality and development productivity. Building on its proven expertise in V2X technologies, SAESOL Tech has introduced S2X Tester 2.0, an OpenTAP®-based test automation platform.

S2X Tester 2.0 is a plugin-based platform that supports the entire testing workflow within a single environment—from Test Plan design and equipment control to test execution, result analysis, and report generation. Its greatest strength is its flexibility, enabling seamless application across a wide range of industries, including V2X, drones, defense, telecommunications, and embedded systems.

Now, let’s take a closer look at the key features and newly introduced capabilities of S2X Tester 2.0.

S2X Tester 1.0 Achieved OmniAir OQTE Certification

1. Hierarchical Test Plan Structure

S2X Tester 2.0 introduces an enhanced Test Plan management system with a newly designed hierarchical structure consisting of Test Cases, Test Steps, and Child Steps. This structure enables users to organize test procedures in a logical sequence while designing even the most complex test scenarios with greater clarity and efficiency.

Within a single Test Case, multiple Test Steps can be defined, and each Test Step can contain multiple Child Steps. This hierarchical approach makes it easy to build sophisticated test workflows while maintaining a clear and intuitive structure.

For example, a “Security Authentication Test” Test Case can include Test Steps such as Certificate Request, Digital Signature Verification, and Message Transmission Validation, with each Test Step further divided into detailed Child Steps to represent individual testing actions.

This hierarchical architecture not only improves the visibility and organization of test scenarios but also simplifies test asset reuse and maintenance, providing greater efficiency for managing large-scale testing projects.

2. Reduce Repetitive Work, Maximize Reusability

S2X Tester 2.0 introduces Test Step reusability, allowing frequently used Test Steps to be created as shared assets and reused across multiple Test Cases. This enables faster development of test scenarios while ensuring greater consistency throughout the testing process.

By managing tests with reusable Test Steps, the same testing logic can be efficiently applied across multiple Test Cases, improving both test asset management and long-term maintainability.

This capability is particularly valuable for repetitive tasks such as authentication procedures and message verification. As projects grow in scale, organizations can significantly reduce test development time while improving operational efficiency through standardized and reusable test workflows.

3. A Platform Built for Scalability and Compatibility

S2X Tester 2.0 adopts OpenTAP®, a global open-source test automation framework led by Keysight, as its Core Engine for backend control.

OpenTAP® is a proven test automation framework widely used by global test and measurement companies, including Keysight, in real-world testing environments. It provides world-class stability and reliability for equipment control and test scheduling.

By delegating critical low-level control operations to the OpenTAP® engine, SAESOL Tech ensures high system integrity and reliability. Meanwhile, SAESOL Tech’s proprietary technologies focus on delivering differentiated capabilities in user experience (UI), project management, plugin architecture, and test operation workflows.

Most importantly, as S2X Tester 2.0 is built on the OpenTAP® ecosystem, it can seamlessly utilize or integrate various OpenTAP® Test Steps and Test Case assets developed for Keysight environments. This compatibility with existing OpenTAP®-based test assets significantly enhances test asset reusability and improves overall development productivity.

4. Simplified DUT and Equipment Management with Profiles

S2X Tester 2.0 enables profile-based management of DUT and Equipment configurations. Test environments can be saved as Profiles and easily loaded or reused whenever needed, allowing users to configure consistent test environments across various projects.

This capability reduces repetitive setup efforts and enables more efficient test operations.

5. Flexible DUT and Equipment Expansion with Plugin Architecture

S2X Tester 2.0 adopts a plugin-based architecture that enables flexible expansion of DUTs (Devices Under Test) and Equipment.

Even when new test instruments or testing environments are introduced, they can be easily integrated and utilized through plugins, allowing the platform to adapt quickly to diverse project requirements.

This extensible architecture also provides long-term flexibility in response to evolving test environments and the adoption of new equipment, enhancing the value of S2X Tester 2.0 as a future-ready test automation platform.

Why, S2X Tester 2.0?

A Universal Test Automation Platform

S2X Tester 2.0 supports test automation across various industries—including V2X, drones, defense, telecommunications, and embedded systems—within a single unified platform.

Seamless Compatibility with the OpenTAP Ecosystem

With support for Test Steps and Test Cases developed on the Keysight OpenTAP® framework, users can seamlessly leverage existing test assets and maximize their reuse.

Proprietary High-Performance UI

Built with SAESOL Tech’s proprietary WPF-based UI without additional licensing constraints, S2X Tester 2.0 reduces licensing costs while enabling rapid feature expansion and an enhanced user experience tailored to customer requirements.

Enhanced Test Productivity

The hierarchical Test Plan structure and reusable Test Step functionality reduce test development time and improve maintenance efficiency.

Automated Test Result Generation

Automatically generates various test outputs, including HTML reports, logs, and video captures, simplifying test analysis, documentation, and sharing.

Conclusion

S2X Tester 2.0 has evolved beyond a simple feature upgrade into a next-generation test automation platform that supports the entire testing lifecycle within a single environment—from Test Plan design and equipment control to test execution, result analysis, and test artifact management.

Designed for flexible application across a wide range of industries, including V2X, drones, defense, telecommunications, and embedded systems, S2X Tester 2.0 delivers outstanding stability and scalability through its proven OpenTAP®-based test engine and plugin architecture.

SAESOL Tech will continue to enhance the platform in response to evolving technologies and diverse customer requirements, providing a more efficient, reliable, and intelligent test automation environment.

Experience the new standard of test automation with S2X Tester 2.0 and discover a powerful solution designed to redefine test automation across various industries.

S2X Tester 2.0 Demo & Solution Inquiry

If you would like to learn more about the detailed specifications or practical applications of S2X Tester 2.0, please contact SAESOL Tech’s experts. We will be happy to provide further information and support.

saesoltech itsamerica v2x

That’s a wrap! Thank you for connecting with SAESOL Tech at ITS America 2026! 🎬

SAESOL Tech successfully wrapped up an incredible week at ITS America 2026 in Detroit!

It was an honor to showcase our latest intelligent transportation and mobility security innovations to a global audience. We were thrilled by the overwhelming interest and insightful conversations with industry leaders, partners, and innovators who visited Booth #7045.

During the event, our team had the pleasure of demonstrating how we are shaping the future of secure V2X ecosystems through our core technologies:

🔹 S2X RoadSigner – Empowering digital signing for TMC-generated traffic and environmental data.

🔹 S2X Secure Link – Delivering seamless mutual authentication and end-to-end encryption with existing ITS certificates.

🔹 S2X Mobile – Bringing robust V2X message signing and verification to emerging mobility participants.

🔹 S2X CMS – Providing a comprehensive certificate lifecycle management platform for the entire trust ecosystem.

The event may be over, but our journey toward safer, smarter, and more secure mobility is just getting started. If you missed the chance to connect with us in person or want to continue our discussion is always open to exploring how we can drive innovation together.

Thank you again to everyone who stopped by and made this event a huge success. See you at the next milestone! 🤝

#ITSAmerica2026 #SAESOLTech #V2X #MobilitySecurity #SmartTransportation #Detroit

saesoltech itsamerica v2x
saesoltech itsamerica v2x
saesoltech itsamerica v2x
saesoltech itsamerica v2x
its america saesol tech

SAESOL Tech will be exhibiting at ITS America 2026!

As pioneers in intelligent transportation solutions, we are excited to showcase our latest innovations and connect with industry leaders, partners, and innovators from around the world.

If you are attending, we would love to meet you in person, discuss the future of mobility, and explore how we can drive innovation together.

Come by Booth #7045 to meet our expert team and see our cutting-edge technologies in action. See you in Detroit!

its america saesol tech

Explore our latest innovations:

🔹 S2X RoadSigner
A digital signing solution for traffic and environmental data generated by TMCs.


🔹 S2X Secure Link
A mutual authentication and end-to-end encryption solution utilizing existing ITS certificates.


🔹 S2X Mobile
A V2X message signing and verification solution designed for emerging mobility participants and connected services.


🔹 S2X CMS
A comprehensive certificate issuance and lifecycle management platform supporting the entire trust ecosystem.

GO AUSTRIA, GO SAESOL TECH!

SAESOL Tech is thrilled to announce our participation in GO AUSTRIA Spring 2026 in Vienna! We are honored to join forces with visionary startups and global innovators bridging Asia and Europe.

At this premier event, we will showcase S2X, our next-generation security solution specifically designed for the European and global markets. SAESOL Tech is committed to accelerating a future of secure, reliable, and trusted connected mobility.

We look forward to connecting with new global partners and sharing our vision for the evolving mobility ecosystem. See you in Vienna!

#GOAUSTRIA2026#SAESOLTECH#S2X#V2X#CyberSecurity#ConnectedMobility#SmartMobility#ViennaUP#GlobalInnovation

saesoltech tester oqte

SAESOL Tech Achieves OmniAir® Qualified Test Equipment Status for S2X Tester, Sets New Standard for Global V2X Security

SAESOL Tech, a global innovator in mobility cybersecurity, is proud to announce that its S2X Tester has officially earned qualification as OmniAir Qualified Test Equipment (OQTE) from the OmniAir Consortium®. This achievement comes as the company continues to accelerate its U.S. expansion, following the recent opening of its strategic office in Menlo Park, California.

This qualification confirms the S2X Tester as a certified tool for V2X (Vehicle-to-Everything) standards compliance, providing a critical technical foundation for the deployment of secure connected vehicle technologies. With this achievement, SAESOL Tech is positioned to support the rigorous certification requirements of the world’s leading V2X markets.

https://apnews.com/press-release/ein-presswire-newsmatics/saesol-tech-achieves-omniair-qualified-test-equipment-status-for-s2x-tester-sets-new-standard-for-global-v2x-security-4874c4ea3410621aa0f4988297679e3d?utm_source=copy&utm_medium=share

Zero Trust, AI security, quantum security, robotic security, etc… Rapidly changing cybersecurity environment and response strategies

Zero Trust, AI security, quantum security, robotic security, etc… Rapidly changing cybersecurity environment and response strategies

During a meeting with Wall Street analysts after visiting CES 2025 in January, Jensen Huang was asked about the pace of development of early-stage quantum computers and stated, “It will take about 20 to 30 years to reach a useful level,” which led to a significant drop in the stock prices related to quantum computing. 

However, Sundar Pichai, the CEO of Alphabet, made a positive forecast at the World Government Summit held in Dubai on February 12, stating that “Quantum computing will be possible in 5 to 10 years”, overshadowing Jensen Huang’s outlook. 

The ‘Willow Chip’ from Google Quantum AI, announced on December 9, 2024, astonished experts by performing calculations that would take 10 trillion 700 billion years on a supercomputer in just 5 minutes, achieving a breakthrough in solving the random number generation problem, which is crucial for modern security infrastructure, using specific quantum algorithms. Sundar Pichai’s confidence undoubtedly stems from such empirical achievements. 

On January 19, Microsoft also announced the Majorana 1, a quantum chip using topological superconductors. According to Microsoft, Majorana 1 is a ‘topology core-based quantum processing unit’ (QPU) designed to scale up to one million qubits on a single chip, with the first product starting with 8 qubits. 

Topological superconductors implemented with indium arsenide and aluminum are praised for preventing damage to quantum information, and for enabling error detection and correction to be digitized and automatically controlled, bringing commercialization one step closer. The powerful capabilities of quantum computers are now within reach. 

Image: Microsoft Majorana 1 chip 

Source: https://azure.microsoft.com/en-us/blog/quantum/2025/02/19/microsoft-unveils-majorana-1-the-worlds-first-quantum-processor-powered-by-topological-qubits/ 

In this rapidly changing security technology environment, we examined three key technological advancements that the C-ITS and automotive industries must prepare for. 


C-ITS/Automotive Industry Perspective on Zero Trust 

C-ITS (Cooperative Intelligent Transport Systems) is a core technology that can dramatically enhance traffic efficiency and safety, but it also faces the challenge of being exposed to various security threats. C-ITS is a complex system where various components such as vehicles, road infrastructure, and central systems are interconnected and exchange information, making it difficult to ensure effective security with traditional perimeter-based security methods. Data tampering, unauthorized access and control, denial-of-service attacks, and privacy violations are major security threats to C-ITS, which not only increase the risk of malfunctions and accidents but can also lead to social disruption and various side effects due to personal information leaks. 

Zero Trust is a security paradigm based on the principle of ‘never trust, always verify,’ which considers all access and communication as security threats. It enhances security through measures such as least privilege access, micro-segmentation, and continuous verification. Applying Zero Trust in the C-ITS environment can overcome the limitations of existing security methods and build a safer and more reliable future transportation system. 

✅ Least Privilege Access: Only the minimum necessary permissions are granted to C-ITS components and users. Role-Based Access Control (RBAC) and Attribute-Based Access Control (ABAC) are applied to refine permissions, and permissions are dynamically adjusted as needed. 

✅ Micro-Segmentation: The C-ITS network is divided into small areas (segments) based on criteria such as functionality, security level, and data importance. Strict access controls are applied between each segment to minimize damage in the event of an attack. 

✅ Continuous Verification: All access and communication attempts involving C-ITS components, users, and network traffic are continuously verified. The level of security verification is enhanced through multi-factor authentication (MFA), behavior-based analysis, and the use of threat intelligence. 

The 5GAA (5G Automotive Association), which includes various global companies from the automotive, information and communication, and electrical and electronic industries, is researching a trust-building model centered on Dynamic Trust Assessment to address internal vehicle security threats, V2X communication vulnerabilities, and road infrastructure attacks. This approach aligns with the principles of zero trust and can further enhance the cybersecurity framework in the C-ITS environment. 

AI Security 

The emergence of generative AI is completely changing the mindset regarding security. Attackers use AI to perpetrate breaches, while companies use AI to defend against such attacks. Since AI serves as both a sword and a shield, it is not possible for one side to benefit exclusively. From a defensive perspective, AI helps strengthen defenses by improving vulnerabilities that had not been previously considered, identifying subtle attacks, and reducing response times. On the other hand, from an offensive perspective, it enables increasingly sophisticated attacks and assists in automatically generating code equipped with new attack techniques. Defenders and attackers are gradually escalating an arms race that will continue until one side becomes exhausted and gives up. 

In relation to automobiles, enhancing the security of autonomous driving assistance systems has emerged as the biggest issue. While AI is used as a core technology in autonomous driving systems, it can also become a target for hacking. In other words, a malicious attacker could manipulate AI algorithms or tamper with data to cause vehicle malfunctions, making it crucial to verify the integrity during the deployment of AI models and to develop technologies that defend AI models from external attacks. 

So, what strategies should be used to enhance AI security? Three main considerations can be made. 

✅ Adoption of AI-based Security Automation: The era of manual security monitoring is coming to an end, and it is time to consider AI-based security automation. It can operate 24×7 and reduce human intervention, thus helping with risk contribution and prioritization. 

✅ Development of a Zero Trust Strategy: Both external and insider threats are becoming increasingly significant risks. Therefore, the previously mentioned zero trust strategy must be expanded beyond existing boundaries. 

✅ Focus on Data Protection: It is necessary to thoroughly defend internal software and internal data by implementing existing security mechanisms and enhanced security mechanisms to prevent unauthorized access. 

Quantum Security 

According to Cloudflare’s <Year in Review 2024>(https://radar.cloudflare.com/year-in-review/2024) report, global internet traffic has increased by 17.2%, and due to the rapid response to new technologies, post-quantum encryption has reached 13% of TLS 1.3 secure traffic. This change is driven by the growing need for post-quantum encryption to prepare for quantum computing attacks, as powerful quantum computers like Google’s Willow quantum chip and Microsoft’s Mayonara continue to be developed. https://radar.cloudflare.com/year-in-review/2024 

To this end, both security companies and browser vendors are moving quickly. Google Chrome and Mozilla Firefox have already released versions with post-quantum encryption features that are quantum-resistant, while Apple Safari is also in testing, and security infrastructure companies like Cloudflare are fundamentally enabling post-quantum encryption for their customers. In quantum security, it is essential to examine three major technologies. 

✅ Post-Quantum Cryptography (PQC): The currently widely used public key cryptographic methods (such as RSA, ECC, etc.) have vulnerabilities that could be easily decrypted once quantum computers are developed. Therefore, encryption techniques that are secure against future quantum computer attacks are being researched. This technology can be applied in all areas where current encryption technologies are used, including blockchain, secure communication, data protection, and digital signatures. Following standardization efforts, implementations in various programming languages ​​are emerging (eg, the post-quantum cryptography standards JEP 496/497 in Java, https://www.infoq.com/news/2024/12/java-post-quantum/) https://www.infoq.com/news/2024/12/java-post-quantum/ 

✅ Quantum Key Distribution (QKD):   A technology that securely shares cryptographic keys between two users using the principles of quantum mechanics. Unlike traditional cryptographic methods, QKD is based on physical principles rather than mathematical computational complexity, theoretically providing secure communication that is impossible to eavesdrop. Until observed, it does not have a definite value, and the uncertainty principle, which states that the value is determined at the moment of observation, along with the no-cloning theorem that prevents perfect replication of quantum states, enhances its stability. 

✅Quantum Random Number Generator (QRNG):   True randomness is required to eliminate predictable factors in the encryption process. Traditional methods generate random numbers using deterministic algorithms that rely on unpredictable initial values. In fields where security is critical, there is a need to address situations where such methods do not guarantee perfect randomness. Quantum random number generators can produce truly random numbers by utilizing the uncertainty principle of quantum mechanics and the property of quantum superposition, thereby enhancing security. 

 Robot Security 

There is a trend of evolving from fixed robots, such as assembly robots or cooking robots, to mobile robots like unmanned vehicles, delivery robots, and combat robots. Therefore, to ensure smooth control of these mobile robots, it is necessary to utilize the mentioned C-ITS infrastructure to exchange information in real-time. Consequently, applying zero trust security to robots is essential. 

Of course, applying zero trust to robots can dramatically enhance security levels, but the characteristics of the robots themselves must not be overlooked. A few additional considerations are summarized as follows. 

✅ Minimizing the impact on robot performance: The application of zero trust security policies may lead to a decrease in robot system performance. It is essential to apply a zero trust architecture and technologies that minimize performance impacts, considering the real-time performance requirements of robots, such as real-time control and high-speed data processing. 

✅ Supporting various robot platforms and operating environments: A flexible and scalable zero trust architecture should be designed, taking into account various manufacturers, diverse functionalities, and different communication methods of robot platforms and operating environments. 

✅  Compliance with Standards and Regulations:  A Zero Trust system must be established in compliance with international standards related to robot security (such as ISO TR 23482-2, IEC 62443, etc.) and domestic regulations. 

✅  Anomaly Detection Based on Robot Abnormal Behavior:  The robot’s behavior patterns, movement paths, and API call patterns must be analyzed using machine learning to detect abnormal behaviors in advance. 

💡 Respond to Next-Generation Security Threats with SAESOL Tech ! 

In this rapidly changing cybersecurity environment, SAESOL Tech has completed preparations to meet advanced security requirements by meticulously establishing an overall security system in anticipation of Zero Trust 2.0 to respond to next-generation security threats. 

In addition, we are conducting research on next-generation encryption technologies and security architectures that closely analyze the latest technological trends in AI-based security and quantum security. Based on this, we actively participate in the establishment of global and industry standards, leading the migration of the C-ITS and V2X security market. 

SAESOL Tech prioritizes the protection of all users’ personal information beyond next-generation mobility security. We will take the lead in creating a safer future and a trustworthy communication environment through continuous technological innovation. 

saesol tech LOGO

SAESOL Tech and Unex Partner to Strengthen SCMS-V2X Security Interoperability for Global Deployments

SAESOL Tech Inc., a provider of connected vehicle security solutions, announced today that it has signed a Memorandum of Understanding (MOU) with UNEX Technology Corp. to establish a cooperative framework for validating, demonstrating, and advancing Security Credential Management System (SCMS) and V2X security interoperability in global markets.

SAESOL Tech to Unveil Next-Generation V2X Security Technology Protecting Vulnerable Road Users at CES 2026

CES (Consumer Electronics Show), taking place from January 6 to 9, 2026 is recognized as one of the world’s top three IT and electronics exhibitions alongside Mobile World Congress (MWC) and Internationale Funkausstellung (IFA). As of 2025, CES hosted over 4,500 companies from 158 countries and attracted more than 140,000 visitors. At Eureka Park, CES’s dedicated startup exhibition hall, SAESOL Tech will introduce its next-generation V2X security solution for VRU protection, the “S2X VRU Client,” for the first time.