wolfSSL has introduced an optimization for its wolfHSM product that targets performance bottlenecks in post-quantum digital signatures. The company is implementing an "External-Mu" approach for ML-DSA, a post-quantum cryptographic algorithm, to improve signing efficiency when using hardware security modules (HSMs).
What the optimization does
ML-DSA, a post-quantum signature scheme, requires computing a hash value called Mu as the first step in both signing and verification. This hash combines a truncated public key hash, a context string, and the message itself using the SHAKE-256 algorithm. While the Mu value is fixed at 64 bytes, the message being signed can be arbitrarily large, creating potential performance issues when the computation occurs on an HSM with limited processing power or slow transport interfaces.
The External-Mu optimization moves the Mu hash computation from the HSM to the client application. Since Mu depends only on public data—the public key, context string, and message—this shift does not compromise security. By performing this step on the client side, wolfSSL aims to reduce the data volume sent to the HSM and minimize processing delays, particularly for large messages or in environments with constrained HSM performance.
Implementation context
wolfSSL's wolfHSM product provides cryptographic acceleration and secure key storage for embedded systems and enterprise environments. The company notes that while this optimization is specific to ML-DSA, wolfSSL also supports HashML-DSA, a related but distinct algorithm with different identifiers. Interoperability considerations may limit the applicability of External-Mu in some deployments, though wolfSSL has not detailed specific compatibility constraints.
Background: ML-DSA (Module-Lattice Digital Signature Algorithm) is a post-quantum cryptographic standard selected by NIST for its resistance to attacks from both classical and quantum computers. Hardware security modules (HSMs) are physical devices that manage cryptographic keys and perform encryption operations, often used in high-security environments like financial services and government systems.
Potential impact and adoption
The optimization is currently in development, with wolfSSL indicating that its priority may increase based on customer demand. Organizations using wolfHSM for ML-DSA signing could see reduced latency, particularly in scenarios involving large messages or performance-constrained HSMs. However, the company has not released benchmarks or specific performance metrics for the External-Mu approach.
For deployments where interoperability with other ML-DSA implementations is critical, the optimization may require additional validation to ensure compatibility. wolfSSL has invited users to contact them to express interest or request further details about the feature.
What to watch
The success of this optimization will likely depend on two factors: customer adoption of ML-DSA in HSM environments and the performance gains achieved in real-world deployments. If wolfSSL releases benchmark data or case studies, these could provide clearer guidance on the practical benefits of External-Mu. Additionally, broader industry trends toward post-quantum cryptography may influence demand for such optimizations as organizations prepare for quantum-resistant security standards.
Companies mentioned
Automated pipeline · Security
Synthesized from 1 industry feed on 9 Oct 2026. Passed independent editor verification (score 92/100) before publication. Style guide v1.4.
Sources
Decision trail
- Checking for duplicates — New story No recent or in-pipeline article covers wolfHSM's ML-DSA optimization (External-Mu).
- Checking for duplicates — New story pre_write:; No recent or in-pipeline article covers wolfHSM ML-DSA optimization or External-Mu.
- Writing the article — Draft created article_id=677 slug=wolfssl-optimizes-ml-dsa-signing-for-hsm-performance
-
Editor review — Approved
- Score: 92/100
- Style compliance: Headline exceeds 90-character limit (92 characters). Shorten to meet style guide requirements.
- Factual grounding: Source does not provide a specific timeline for the optimization's development status (e.g., 'currently in development'). While the implication is clear, the phrasing in the draft could be interpreted as a definitive statement. Clarify as 'under consideration' or 'in early development' if no explicit timeline is given.
- Audience relevance and notability: The story is narrowly focused on a single vendor's optimization for a niche use case (ML-DSA in HSMs). While technically sound, the broader relevance to hosting/domains/DNS/email professionals is limited. Consider adding a sentence on how this might impact TLS termination or certificate issuance workflows if applicable.
- Generating reader Q&A — Generated 4 items
- Assigning hero image — Reused library image reused image #269
- Linking related stories — Linked 5 relations from 340 candidates
- Publishing — Published wolfssl-optimizes-ml-dsa-signing-for-hsm-performance
- Mastodon — Posted https://mstdn.social/@hostingpaper/117411989509475421




Discussion · coming soon
Be the first to join the thread when community discussion launches.