No events on this day.
This complimentary webcast is designed for payments security leaders who need a clear, no‑nonsense view of the quantum threat - and what to do about it now, without fluff. Co‑hosted by QSECDEF and Applied Quantum, this session cuts through generic PQC talk and focuses on what makes payments different: crypto everywhere, many independent parties, and millisecond operational envelopes that you can’t break. We focus on the real blockers in payments: interdependencies, performance budgets, and vendor/partner sequencing. Payments are unusually crypto‑dense and time‑dense: a single authorization spans parties that don’t share one change calendar, and the chain must complete inside strict timeout/retry behavior. We’ll use an interbank cryptography stack mapping as a concrete illustration of how many trust boundaries exist before you even introduce PQC - and why “just upgrade the algorithm” is not a plan.
No events on this day.
This complimentary webcast is designed for security leaders who need a clear, no-nonsense understanding of the quantum threat - and what to do about it now. Co-hosted by SANS Institute and Applied Quantum, the session explains what's changing in the cryptographic landscape, why the migration to quantum-safe standards is far larger than most organizations expect, and what practical steps you can take today. Quantum risk is not a future-only problem. Adversaries can harvest encrypted data today for later decryption, while regulators and customers increasingly expect demonstrable progress now - not just plans for 2030 or 2035.
This complimentary webcast is designed for banking security leaders who need a clear, no‑nonsense understanding of the quantum threat - and what to do about it now. The session avoids generic “PQC 101” and goes straight to what makes banking different: institutional identity and long‑lived evidence are the real blast radius. In a bank, cryptography isn’t just protecting data in transit - it is the foundation of trust at scale: CA hierarchies, enterprise PKI, service‑to‑service mTLS, customer and workforce authentication, signed tokens (e.g., OAuth/JWT ecosystems), document and transaction signing, code‑signing in CI/CD, and the regulated archives that prove what happened, when, and under which authorization. The uncomfortable banking‑specific reality is that “confidentiality later” is only half the story: if signatures and PKI trust anchors become forgeable in the future, the bank’s ability to prove integrity, provenance, and non‑repudiation comes under pressure.
No events on this day.
No events on this day.