POST-QUANTUM CRYPTOGRAPHY / ADVISORY
Post-quantum cryptography migration
From threat models and cryptographic inventories to architecture and pilot validation. Turn post-quantum standards into actionable migration decisions.
Content reviewed: 2026-10-04
01 / EXPERT TEAM
Meet the people through their expertise, academic backgrounds, and public research.
PQC projects & engineering research
EudTech project lead / technical contact
FPGA · Cryptographic migration planning · Audio steganography research
Research interests also include formal logic and abductive reasoning (IBE), connecting assumptions and inference to testable technical judgments.
EudTech team profile
Cryptography & algorithms
Ph.D. in Electrical Engineering, National Taiwan University
Assistant Professor, Computer Science and Information Engineering, National Taipei University
Research covers cryptography, algorithms, steganography, and multimedia security, including a principal-investigator role in ML-DSA implementation research.
University research profileSELECTED RESEARCH / HUNG-JR SHIU
2026 · Principal investigator · Pipelined HLS implementation
Connect algorithm standards to implementation research, including performance and engineering constraints.
View the university research projectAcademic and research information links to original sources. University affiliations are individual credentials, not institutional endorsement of this service.
Algorithm references, not service certification
02 / SERVICES & DELIVERABLES
Start with one business service or agreed asset scope. Identify cryptographic use, confidentiality needs, and vendor dependencies.
Your deliverables
AcceptanceEach asset has a traceable source, owner, and status. Uncovered areas remain explicit.
Start with one business service or agreed asset scope. Identify cryptographic use, confidentiality needs, and vendor dependencies.
AcceptanceEach asset has a traceable source, owner, and status. Uncovered areas remain explicit.
Compare architecture options for a connection or signing use case. Define product support, tests, acceptance criteria, and rollback.
AcceptanceUse agreed performance and compatibility criteria, with repeatable success and failure tests.
Use pilot evidence to plan migration batches and review changes, while maintaining assets, dependencies, and exceptions.
AcceptanceRecommendations trace back to evidence. The customer owns approval and cutover, with open items and owners recorded.
Advisory covers analysis, design, and evidence review. Authorized customer teams and vendors execute production changes; implementation, licenses, and support require an agreed scope.
03 / A FOCUSED PILOT
Check client, proxy, and server versions before evaluating suitable PQC or hybrid key establishment.
Check client, proxy, and server versions before evaluating suitable PQC or hybrid key establishment.
Map signing, verification, and update dependencies, and confirm ML-DSA or SLH-DSA support in specific products.
Inventory device, PKI, HSM, and library versions and lifecycles. Confirm implementation scope and upgrade paths.
04 / YOUR NEXT MOVE
Answer three questions to prepare a scope for your next internal discussion.
No contact details required. Answers are processed on this page and are not submitted by this questionnaire.
Book a discovery meeting05 / QUESTIONS
Begin with inventory, prioritization, and vendor checks. Stage replacements with compatibility, performance, and rollback validation.
Check edge-to-origin traffic, internal services, key management, and signing separately. PQC key establishment does not imply migrated certificate signatures.
Algorithm standards, implementation correctness, and cryptographic module validation are separate. Check the product, version, and validation scope.
PQC uses algorithms on conventional computers to resist known quantum attacks. Steganography hides the presence of information; QKD requires quantum channels and equipment. This service focuses on PQC migration.
Confirm assets, applications, test environments, and vendor support, then agree the assessment, pilot, migration, and support scope.