Cross-sector · Platforms & Architecture

Across sectors: platforms and architecture

What to know now

Each number links to the point's source. Points checked unless the point shows another date.

  • NIST released its first three finalized post-quantum standards on August 13, 2024: FIPS 203 for general encryption and FIPS 204 and 205 for digital signatures. NIST urged system administrators to start integrating them immediately.1
  • On March 11, 2025, NIST chose HQC as a backup to ML-KEM for general encryption. It planned a draft standard in about a year and a final standard in 2027.2
  • NIST released the final NIST IR 8547, Transition to Post-Quantum Cryptography Standards, on October 27, 2026. NIST says it identifies existing quantum-vulnerable cryptographic standards and the quantum-resistant standards designed to replace them, and outlines NIST's approach and timelines for the transition. NIST's release notes that National Security Memorandum 10 set 2035 as the primary target for completing migration across federal systems.3
  • Executive Order 14412 of June 22, 2026 directs OMB to issue guidance, within 90 days, requiring agencies to move high value assets and high impact systems (excluding National Security Systems) to post-quantum cryptography for key establishment by December 31, 2030 and for digital signatures by December 31, 2031. Sector Risk Management Agencies must work with CISA to help critical infrastructure owners and operators develop their migration plans.4
  • Executive Order 14306 of June 6, 2025 amended Executive Order 14144. It directed NSA (for National Security Systems) and OMB (for other systems) to issue requirements, by December 1, 2025, for agencies to support TLS 1.3 or a successor as soon as practicable and no later than January 2, 2030, and directed NIST to publish a preliminary update to its Secure Software Development Framework by December 1, 2025.5

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Sources

  1. National Institute of Standards and Technology. NIST releases first 3 finalized post-quantum encryption standards. Checked .
  2. National Institute of Standards and Technology. NIST selects HQC as fifth algorithm for post-quantum encryption. Checked .
  3. National Institute of Standards and Technology. NIST report provides guidelines for transition to post-quantum cryptography standards (NIST IR 8547). Checked .
  4. Office of the Federal Register (Executive Office of the President). Executive Order 14412: Securing the Nation Against Advanced Cryptographic Attacks. Checked .
  5. Office of the Federal Register (Executive Office of the President). Executive Order 14306: Sustaining Select Efforts To Strengthen the Nation's Cybersecurity and Amending Executive Order 13694 and Executive Order 14144. Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the page where needed.

Looking Back

  1. Week of August 10, 2026

    Post-quantum signatures are still being chosen, so build PKI to switch twice

    Digital signatures had moved up the post-quantum to-do list, yet two years after NIST’s first standards the choice of signature scheme was still open. Sort signatures by how long they must stay trustworthy, and design each group to change twice.

    • Cross-sector
    • Platforms & Architecture
    • 13 min read
  2. Week of June 15, 2026

    The client-certificate deadline that moved, and the certificate authorities that didn’t wait

    Chrome pushed back its deadline for using public web certificates to prove a client’s identity, to March 2027. Certificate authorities kept their own, earlier schedules. For any system-to-system link that relies on one, the real deadline belongs to whoever issues the certificate.

    • Cross-sector
    • Platforms & Architecture
    • 13 min read
  3. Week of August 25, 2025

    OAuth integrations make their vendors custodians of your credentials

    The Salesloft Drift data theft began inside a vendor, not inside any customer’s Salesforce. Approving an integration hands that vendor a standing key to your data, and vendor reviews may never have asked how the key was kept.

    • Cross-sector
    • Platforms & Architecture
    • 13 min read
  4. Week of April 14, 2025

    How the CVE contract scare exposed the public plumbing under every patching policy

    For one day in April 2025, the program that gives every software flaw its name looked set to switch off. The scare showed that patching policies and audit evidence rest on three public layers, each with its own way of failing.

    • Cross-sector
    • Platforms & Architecture
    • 28 min read
  5. Week of January 27, 2025

    DeepSeek arrived in three forms in one week, and each needed a different control

    Within days, the same DeepSeek model reached organizations as a phone app, a developer service and freely downloadable files running on U.S. clouds. Blanket bans treated them as one risk. They were three, each owned by a different team.

    • Cross-sector
    • Platforms & Architecture
    • 29 min read
  6. Week of August 12, 2024

    Post-quantum priority starts in the records retention schedule

    NIST’s first post-quantum standards settled what to move to. Deciding what to move first is harder, and for banks, health systems and agencies the answer sits in a surprising place: the records retention schedule.

    • Cross-sector
    • Platforms & Architecture
    • 28 min read
  7. Week of January 22, 2024

    Test tenants are production when their apps can reach production

    Russian state hackers read Microsoft executives’ email by way of a forgotten test account and an old app with too much power. Any “non-production” identity deserves three tests: who can log in to it, what it can reach and who would notice.

    • Cross-sector
    • Platforms & Architecture
    • 28 min read
  8. Week of September 18, 2023

    Cisco’s Splunk deal and the case for owning your security logs outside the SIEM

    A major security logging platform changing hands exposed where the real lock-in sits: years of logs the rules require you to keep, detection rules written in one vendor’s language, and the wiring around them. Each can be freed before the next deal.

    • Cross-sector
    • Platforms & Architecture
    • 27 min read
  9. Week of December 5, 2022

    Rackspace kept running old Exchange for clients, and kept its old risks

    Ransomware at Rackspace’s hosted Exchange email showed customers that paying someone to run aging software hands over the work, not the risk. They needed three things their contracts rarely spelled out: a way to patch, a way out and a way back.

    • Cross-sector
    • Platforms & Architecture
    • 26 min read
  10. Week of June 6, 2022

    Your carrier’s routers belong in your threat model

    A joint US advisory described state hackers getting inside the telecom companies that carry everyone’s traffic. For the businesses that buy those services, the message was blunt: treat the carrier’s network as untrusted, its engineers as privileged users, and its silence as a blind spot.

    • Cross-sector
    • Platforms & Architecture
    • 27 min read

All 17 Looking Back articles in Cross-sector and Platforms & Architecture

Explainers, checklists and data

  1. Explainer · November 14, 2026

    Zero trust architecture: NIST SP 800-207, SP 800-207A, SP 1800-35 and CISA’s maturity model, explained

    NIST SP 800-207 (August 2020) still defines zero trust as a set of tenets and three logical components, not a product. SP 800-207A, CISA’s five-pillar maturity model and the 2025 SP 1800-35 practice guide build on it, and CISA’s own dates for its model conflict.

    • Cross-sector
    • Platforms & Architecture
    • 5 min read
  2. Explainer · November 14, 2026

    Post-quantum cryptography: FIPS 203, 204 and 205, NIST IR 8547 and the federal deadlines, explained

    NIST’s three post-quantum standards took effect on August 14, 2024. NIST IR 8547, final in October 2026, deprecates today’s public-key algorithms after 2030 and disallows them after 2035, and Executive Order 14412 sets earlier dates for the most sensitive federal systems.

    • Cross-sector
    • Platforms & Architecture
    • 5 min read
  3. Checklist · November 14, 2026

    Checklist: a federal agency’s post-quantum migration under EO 14412, OMB M-26-15 and NIST IR 8547

    Fourteen steps for agency CIOs and CISOs: naming the migration lead, building the cryptographic inventory, ranking systems by risk, submitting the plan, and meeting the 2030 and 2031 deadlines for high value assets and high impact systems, with NIST’s 2030 and 2035 algorithm dates.

    • Cross-sector
    • Platforms & Architecture
    • 5 min read