QUECWA FACT FILE · Original structured learning resource
Developing: Algorithms, standards and trust
OBA outcome — Distinguish: Distinguish key establishment from digital signatures and explain the roles of ML-KEM, ML-DSA and SLH-DSA.
← Full pathwayAlgorithms, standards and trust
Two different jobs
Key establishment helps parties derive shared secret material. Digital signatures support authenticity and integrity. A PQC migration must consider both functions rather than treating all cryptography as encryption.
NIST's initial standards
FIPS 203 standardises ML-KEM for key encapsulation. FIPS 204 standardises ML-DSA for signatures. FIPS 205 standardises SLH-DSA, a hash-based signature alternative with different engineering trade-offs.
A transition, not a switch
Real systems include TLS, certificates, software signing, VPNs, device firmware and vendor platforms. Different protocols and products will adopt PQC at different speeds.
Australian context
ASD's Information Security Manual and associated transition guidance provide an Australian planning context. NIST standards define algorithms; implementation profiles and applicability must be checked for each system.
Founder video: Algorithms, standards and trust
This is a timed production outline, not a recorded video. The finished video will be no longer than five minutes.
- 0:00–1:00 — Contrast establishing a secret with signing a message.
- 1:00–2:30 — Explain ML-KEM, ML-DSA and SLH-DSA.
- 2:30–3:40 — Show where these functions occur in enterprise systems.
- 3:40–4:35 — Introduce implementation constraints and Australian guidance.
Three things worth remembering
- Two different jobs: Key establishment helps parties derive shared secret material. Digital signatures support authenticity and integrity. A PQC migration must consid
- NIST's initial standards: FIPS 203 standardises ML-KEM for key encapsulation. FIPS 204 standardises ML-DSA for signatures. FIPS 205 standardises SLH-DSA, a hash-based sign
- A transition, not a switch: Real systems include TLS, certificates, software signing, VPNs, device firmware and vendor platforms. Different protocols and products will adopt
Explain, don't guess
Show what you can do
Map five organisational uses of cryptography to key establishment, signatures or symmetric protection; identify one unknown dependency.
Show evaluation criteria
A good response classifies each use correctly and flags uncertainty instead of assuming all cryptography has the same migration path.
Self-assessment only. A score or completion here is not a professional certification.
Authoritative references: ASD / ACSC (including the ISM and PQC transition guidance) · NIST PQC project · FIPS 203 · FIPS 204 · FIPS 205. Check current versions and applicability before acting.
Source foundation: founder-authored educational course material, adapted and independently revised for QUECWA. Content is educational and subject to continuing technical review.