Technical Whitepaper
DPSM — Distributed PUF Sealing Module Next Generation HSM
DPSM distributes a PUF (Physical Unclonable Function) hardware root of trust across chip, server, and region tiers, combining pre-commit authorization checks with post-commit sealing into a next-generation security module. It resolves the structural limits of traditional HSMs through distribution, self-verification, silicon sealing, and IRON-grade sealing .
Common Misconceptions
Three things people often get wrong about Axowl
Before the technical deep-dive, three patterns of confusion we hear most often — corrected up front so the rest of the whitepaper reads cleanly.
"Online" and "on-prem" are not different products.
Many readers assume RO-PUF security requires on-premise hardware shipping. It does not. The same RO-PUF + BCH ECC + HKDF circuit synthesizes onto AWS F2 (FPGA) in the cloud and onto a closed-network ASIC with identical security primitives. Online deployment is not a weaker cousin of on-prem — it is the same silicon-grade trust anchor, delivered Day-1 on a cloud account .
Small startups already get nation-state-grade hardware.
The Nitro tier is often dismissed as "the cheap option for startups." In practice, a 5-person team running on AWS Nitro Enclaves with the IRON sealed chain receives cryptographic guarantees that match or exceed every legacy HSM on the market — hardware isolation, KMS attestation, sealed audit chain, and pre-commit conflict detection, all available at the General tier without buying a single appliance. Enterprise security is no longer reserved for companies that can afford a $100K HSM cluster.
Homomorphic encryption sounds great — but cannot ship in production.
Homomorphic Encryption (HE) is the most-hyped cryptography of the moment, yet its 100×–1,000× compute overhead , inability to mutate encrypted records, and catastrophic SaaS cost destroy the very workloads it promises to protect. Axowl reaches the same privacy goal — and adds integrity, mutability, and zero-latency processing — by anchoring trust in the silicon instead of in lattice math.
Read the full Axowl vs Homomorphic Encryption comparison
The Promise
Why data theft yields zero, and insider tampering becomes impossible
Stolen data is worth zero to the attacker
Every piece of DPSM data is encrypted with a key derived from the PUF. The PUF key is derived only inside the silicon and is never stored anywhere . Database dumps, exposed backups, cloud breaches — in every case the intruder walks away with nothing but ciphertext that has no decryption key.
Insider tampering is blocked too
Not even Axowl's own staff or administrators can extract the PUF key. Every audit event is sealed at IRON grade and chained, so any modification after sealing is mathematically detected on the spot . Authorization itself is checked by a pre-commit LLM gate — bad permissions are blocked before they are ever granted.
01 · Patents Filed
Three Core Patents
The core technologies behind DPSM are filed and are progressing through rights-protection stages in major markets worldwide. The portfolio comprises an extensive set of claims, and each patent combines into a unified trust system that covers the entire timeline rather than a single isolated tool. What is protected is the sealed transition itself — the hash chain across every state change — not the hardware beneath it. The protection attaches to that transition regardless of the substrate on which it runs, and the claims reach the method together with its software, SDK, and service embodiments.
Hierarchical Distributed Trust Fabric
Trust is distributed from a hardware root through odd-numbered quorums at the chip (L1), server (L2), and region (L3) tiers. No single node holds a complete system key.
Transition-Sealed Integrity System
At every state transition, IRON-grade sealing combined with logic watermarking detects tampering instantly. The transition hash chain preserves both the moment and the actor of any tampering.
Pre-grant LLM Conflict Verification
Before a permission is granted (pre-commit), an LLM detects semantic conflicts in the permission combination and blocks the grant itself. No equivalent solution exists on the market.
Filing numbers, claims, drawings, and algorithm details are provided separately under NDA. Please use the technical inquiry channel to request technical materials.
02 · PUF Limitations Solved · FIPS 140-2 Compliant
Known PUF Weaknesses, Solved by DPSM
A PUF (Physical Unclonable Function) is a powerful hardware root of trust, but on its own it has limits. DPSM resolves these weaknesses with multi-layer defenses — ECC, KDF, k-of-n quorum, drift tracking, AXI isolation — all designed to comply with FIPS 140-2 (IG D.K · 14.5), NIST SP 800-90B, and SP 800-108 .
PUF Weakness
Noise (BER)
Silicon variation flips 5-10% of response bits each read. The same chip risks producing different keys.
DPSM Solution
BCH ECC + majority voting
BCH(127, 64, T=10) encoder plus 8-sample majority voting (≥5/8) extracts stable bits. RTL implementation complete.
PUF Weakness
Aging · Drift
PUF responses gradually shift over the chip's lifetime, eroding reproducibility.
DPSM Solution
Drift-rate tracking
The time-series drift rate of PUF responses is monitored and re-enrollment is triggered at threshold. Covered by patent claims.
PUF Weakness
Modeling Attacks
ML can learn many challenge-response pairs to predict PUF behavior (Strong PUFs).
DPSM Solution
Weak PUF only
The challenge interface is never exposed externally (RO-PUF). Used only for key derivation — training samples cannot be collected at all.
PUF Weakness
Single-Chip Dependence
If the chip is damaged or lost, the key is gone forever. Backups are equally risky — a backup is a key disclosure.
DPSM Solution
k-of-n quorum + Hot-Shard
Odd-numbered quorum consensus across L1/L2/L3 tiers. The system runs through the loss of up to k-1 chips, with zero-downtime PUF replacement.
PUF Weakness
Side-Channel Attacks
Power or electromagnetic analysis can extract the PUF response. Physical access becomes a real risk.
DPSM Solution
No AXI exposure · internal-only
The PUF response register is used strictly inside the silicon. With no exposure on the external bus (AXI), it cannot be extracted.
PUF Weakness
Helper-data Entropy Leak
The helper data of a fuzzy extractor can leak part of the PUF entropy.
DPSM Solution
HKDF-Extract + Salt
HKDF-SHA256 (RFC 5869) separates entropy extraction from key derivation, with a salt for domain separation.
FIPS 140-2 Compliance
Every mechanism above is designed to comply with FIPS 140-2 IG D.K · IG 14.5 (PUF-based entropy source), NIST SP 800-90B (entropy-source validation — startup health and continuous health tests), and SP 800-108 / RFC 5869 (HKDF). In online (AWS F2) environments the software domain is fully implemented in virtualization. For closed-network deployments or formal Level 3 certification, please request a separate consultation .
03 · Why DPSM
Seven Structural Limits of Traditional HSMs
HSMs (Hardware Security Modules) were designed for ATM security in the 1980s, and their essence has not changed since. They carry structural limits that no longer match the threat models of the distributed era, the cloud era, or the LLM era.
Centralized Single Appliance
Keys live in a single device — theft or damage puts the entire system at risk.
Administrator Bypass
Vendor firmware updates and administrator privileges open paths to extract keys or bypass controls.
Local Audit Logs
An HSM's own logs can be modified by administrators — insider tampering goes undetected.
Vendor Lock-in
Incomplete PKCS#11 compatibility and vendor-specific quirks make replacement costs explode once you adopt one.
High Cost
$25k–$100k+ per appliance, multiplied by clustering, with separate operations headcount on top.
No Pre-commit Verification
Operates only after permissions are already granted — it cannot verify conflicts in the grant itself.
Slow Algorithm Updates
Adding a new algorithm (e.g. post-quantum) requires firmware updates and re-certification, taking years.
03 · Comparison
HSM vs DPSM — Superiority at a Glance
A visual comparison showing how DPSM outperforms HSMs across seven core evaluation axes. Scores (0-100) represent relative performance on each axis.
Insider Threat Defense
HSM
DPSM
HSM · admin firmware bypass possible
DPSM · admins cannot extract the PUF · silicon-internal
Distributed Consensus (k-of-n quorum)
HSM
DPSM
HSM · active-passive cluster only
DPSM · native L1/L2/L3 chip quorum
Audit-log Integrity
HSM
DPSM
HSM · local logs · admin-modifiable
DPSM · IRON sealed chain · instant detection
Pre-commit Verification
HSM
DPSM
HSM · feature absent
DPSM · LLM semantic-conflict detection + HW gate
Cloud Deployment Speed
HSM
DPSM
HSM · hardware shipping · weeks to months
DPSM · Day-1 instant deploy on AWS F2
Algorithm Update Speed
HSM
DPSM
HSM · firmware + re-certification, years
DPSM · RTL re-synthesis + new AGFI, days
Freedom from Vendor Lock-in
HSM
DPSM
HSM · partial PKCS#11 · vendor lock-in
DPSM · open SDK · HMAC/HKDF/BCH standards
Maintenance · Replacement Cycle
HSM
DPSM
HSM · 5-7 year wholesale replacement · downtime
DPSM · partial hot-swap · zero-downtime quorum
Server Cost (TCO)
HSM
DPSM
HSM · $25k-$100k+ per appliance · multiplied by cluster
DPSM · 50% or less operating cost vs. legacy HSM
Scores are relative assessments per axis and may vary depending on the demonstration environment and the threat model. For closed-network deployments requiring formal FIPS 140-2 Level 3 certification, please request a separate consultation.
04 · Deployment
Deployment Options
Online · Standard Tier
AWS Nitro — Available Immediately
Designed for startups and cost-sensitive environments. Built on AWS Nitro Standard and Nitro Enclaves , it is available immediately for Day-1 deployment without setup wait time.
The Nitro tier still preserves enough security to match or exceed legacy HSMs — Nitro Enclaves' hardware isolation, KMS attestation, and the IRON sealed chain are applied identically, preserving the core values of audit, tamper-proofing, and tamper detection.
Available immediately (Day-0)
Suited for startups and cost-sensitive environments
BYOA (Bring Your Own AWS) supported
Identical IRON sealed chain
Online · IRON Tier
AWS F2 (FPGA) — Available Within 72 Hours
For environments that require top-tier IRON sealing. The PUF + ECC stabilization + KDF circuit is synthesized into an AGFI deployed on AWS F2 instances (Xilinx Virtex UltraScale+ VU47P). Synthesis, AFI registration, and F2 lifecycle setup mean deployment completes within 72 hours .
The software domain of FIPS 140-2 (SHA-256, HMAC, KDF) is fully implemented in virtualization. The hardware domain is provided by AWS F2 silicon.
Deployed within 72 hours
Per-chip independent keys + k-of-n quorum demonstrated
BYOA + top-tier IRON sealing
Closed Network
FIPS 140-2 Certification — Separate Consultation
For closed-network (on-premise) environments in banking, government, defense, and healthcare that require FIPS 140-2 certification, we proceed via a separate consultation.
Deployment paths include SRAM-PUF-based ASIC mass production (e.g. Intrinsic ID Quiddikey) or a combined form integrated with a certified HSM.
Industrial ASIC · Custom Manufacturing
Robotics · Mobility · IoT Chips — MPW & Mass Production
For industrial domains such as robotics, mobility, IoT, medical devices, and defense, we offer ASIC chip manufacturing on a custom-order basis (OEM / Foundry-as-a-Service) . 8-inch wafer fabrication is the default , with 12-inch available on request.
Prototypes are validated at the MPW (Multi-Project Wafer) stage, then transitioned into commercial mass production .
12-inch
Three major Korean foundries · seven processes (SF4, SF5, 8LPU, 14LPU, etc. — Samsung Electronics, SK keyfoundry, and others)
8-inch
One foundry · four processes (LV BCD, HV BCD, etc. — DB HiTek)
Design House
We partner with Korean design houses to support the full RTL → GDS flow.
05 · Licensing & Partnership
Licensing & Partnership
DPSM is available for licensing as an OEM license, a technology-transfer agreement, or joint development. All three core patents are licensable, and split licensing by country, industry, or domain is open to discussion.
OEM License
Embed DPSM technology in your product and ship under your own brand.
Joint Development
Build industry- or country-specific solutions together on the core technology.
Regional / Industry License
Region-specific or industry-specific split licensing.