EvolextQuantum
Navigation

Knowledge

Understand the decisions behind post-quantum migration.

Explore practical guides to cryptographic discovery, migration priorities, supported options, and validation. Start with the foundations or follow a path matched to the decision in front of you.

For SaaS companies and SMEs, from fundamentals to inventory, validation, and rollout planning.

Educational guidance, supported by primary sources. Standards references do not establish compatibility, certification, or production readiness for a particular system.

Start with the question in front of you. ↓Browse all topics ↓
Illustrative interface concept · not a live product or customer system

Start with the question in front of you.

Discovery

Build an inventory you can review

Connect observations to owners, systems, and explicitly recorded unknowns.

Unsure where cryptography is used? Build a bounded inventory with evidence and owners.

For decision-makers and engineers
Last reviewed:

Read guide ↗

Engineering

Plan an application migration increment

Choose a narrow change with explicit dependencies, data formats, and acceptance criteria.

Planning a change? Define a narrow increment, dependencies, and acceptance criteria.

For engineers and technical owners
Last reviewed:

Read guide ↗

Last-reviewed dates refer to the recorded technical review, not publication dates or routine visual edits. A date is not a guarantee that every provider capability remains unchanged.

Choose a reading path, or browse freely.

Suggested sequences, not prerequisites or a mandatory course. You can start with the guide that answers your current question.

Browse all topics

Foundations

Understand the threat, cryptographic roles, and standards before considering changes.

Discovery and prioritization

Connect observations to owners, priorities, and vendor questions.

Engineering and operations

Plan bounded changes, test behavior, and prepare operational decisions.

Understand what each source can establish.

Published standards
Define mechanisms and requirements within a stated scope. They do not certify an application or establish vendor support.
Implementation and vendor documentation
Describe version-specific features and constraints. Check the exact platform, protocol, configuration, and current support status.
Educational guidance
Explains concepts and decision points. It is not an assessment of your system or a deployment instruction.
Laboratory observations
Show behavior under specified test conditions. They do not automatically establish production readiness.

Sources, review, and corrections

We prefer primary publications, separate finalized standards from drafts and implementation evidence, and record review dates on each guide. Check linked sources and environment-specific documentation before acting. Report corrections with the guide URL and supporting source; do not include confidential system details.

Suggest a correction ↗

A few terms worth knowing

KEM ↗
A key-encapsulation mechanism helps establish a shared secret; it is not bulk-data encryption.
Digital signature ↗
A mechanism for checking data integrity and the signatory’s authenticity within its trust model.
Crypto-agility ↗
The ability to change cryptographic mechanisms through planned architecture, configuration, and operational processes.
Hybrid approach ↗
A specified combination of classical and post-quantum mechanisms. Its properties depend on the actual protocol and implementation.
Cryptographic inventory ↗
A scoped record of cryptographic uses, dependencies, owners, evidence, and unresolved gaps.

Apply what you learn.

Questions before you start.

Do I need cryptography expertise to begin?

No. Start with the fundamentals and data-lifetime guides. Detailed engineering decisions still need appropriate technical expertise and environment-specific review.

Is PQC the same as quantum key distribution?

No. PQC uses mathematical algorithms on conventional computing platforms. QKD uses physical quantum communication mechanisms with different equipment and operational requirements.

Does following these guides make a system quantum-safe?

No. Reading guidance is not system validation, certification, or assurance. A real change requires verified support, testing, operational planning, and authorized decisions.

How should I check vendor or protocol support?

Check official documentation for the exact product, version, protocol profile, and configuration. Separate roadmap statements from available support and tested interoperability.

What should I do when a source or recommendation changes?

Revisit affected assumptions and decision records with the system owner. Verify current sources and consider whether inventory, priorities, or testing must be updated.