CuraSec

tag: Post-Quantum · 4 items

  • Engineer — Learn: Academic research proposing a combined data-provenance watermarking and post-quantum secure aggregation scheme for federated learning; no exploitation signals or patch action required, but relevant if you are designing or hardening an FL pipeline.
  • SOC/IR — Skip
  • Leader — Skip
2026-08-17 · arXiv cs.CR · source ↗ #post-quantum#cryptography#ml-kem
  • Engineer — Learn: Useful methodology for teams validating ML-KEM library choices (noble/post-quantum, liboqs, Go stdlib) against NIST ACVP corpora; no running-system changes required today, but informs how to structure PQC migration testing.
  • SOC/IR — Skip
  • Leader — Skip
2026-08-10 · arXiv cs.CR · source ↗ #post-quantum#cryptography#pqc
  • Engineer — Learn: Useful background for engineers tracking isogeny-based PQC alternatives post-SIDH break; POKE-based KEM shows significant performance gains over terSIDH and CSIDH, but no NIST standardization yet — no migration action warranted today.
  • SOC/IR — Skip
  • Leader — Skip
2026-07-16 · HN (security) · source ↗ #post-quantum#cryptography#roadmap
  • Engineer — Learn: Cloudflare’s 2029 PQC roadmap signals the industry timeline for deprecating classical key exchange; useful context for planning when to prioritize PQC migration in your own TLS and key management stack, but no action required today.
  • SOC/IR — Skip
  • Leader — Plan: A major infrastructure provider’s 2029 PQC deadline is a useful benchmark for your own cryptographic agility roadmap; use it to set a planning horizon and ask whether your encryption-dependent vendors have comparable commitments.