• Quantum Security Awareness (Electricity Edition): Quantum-Safe Grid Operations – OT Trust Anchors, Safety, and Decades-Long Lifecycles

    Quantum Security Awareness – Industry Editions
    Virtual Event

    This complimentary webcast is designed for utility and grid security leaders who need a clear, no‑nonsense understanding of the quantum threat - and what to do about it now, without hand‑waving. The session is built around the operational reality of electricity: safety and stability are non‑negotiable, outage windows are precious, and many OT assets are expected to run for decades. That combination makes “we’ll upgrade the crypto later” an unsafe assumption. Electricity providers face a quantum readiness problem that is OT‑dominant and integrity‑dominant. Confidentiality matters - but for grid operations, the sharper edge is often Trust Now, Forge Later (TNFL): if signatures and certificates that underpin trusted firmware, trusted configs, and trusted device identities become forgeable in the future, attackers don’t just read traffic - they can introduce changes that look legitimate in environments where patching is slow, device refresh is rare, and “roll back” may not exist. This is why electricity quantum readiness tends to start with trust anchors (signing roots, identity, remote access control points) rather than a generic “PQC everywhere” plan.

  • Quantum Security Awareness (Banking Edition): Trust Anchors at Bank Scale – PKI, Signing, and Long‑Lived Evidence

    Quantum Security Awareness – Industry Editions
    Virtual Event

    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.

Privacy Preference Center