<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Muse Notes</title>
    <description>The latest articles on DEV Community by Muse Notes (@musenotes).</description>
    <link>https://dev.to/musenotes</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4203575%2F536e1d2f-64ff-4060-b9d1-baa082c2cfbb.png</url>
      <title>DEV Community: Muse Notes</title>
      <link>https://dev.to/musenotes</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/musenotes"/>
    <language>en</language>
    <item>
      <title>Post-Quantum Cryptography Audit as a Service: CBOM, Mosca's Theorem, and a Roadmap to NIST PQC Standards</title>
      <dc:creator>Muse Notes</dc:creator>
      <pubDate>Wed, 11 Nov 2026 18:54:55 +0000</pubDate>
      <link>https://dev.to/musenotes/post-quantum-cryptography-audit-as-a-service-cbom-moscas-theorem-and-a-roadmap-to-nist-pqc-49bb</link>
      <guid>https://dev.to/musenotes/post-quantum-cryptography-audit-as-a-service-cbom-moscas-theorem-and-a-roadmap-to-nist-pqc-49bb</guid>
      <description>&lt;p&gt;Quantum computers will not break your encryption tomorrow. But the migration deadline is already set: NIST's final IR 8547 (October 2026) deprecates all quantum-vulnerable public-key algorithms after 2030 and disallows them after 2035. Google and Cloudflare both target their own migrations by 2029. The question is no longer whether to migrate — it is whether your cryptography inventory is ready.&lt;/p&gt;

&lt;p&gt;I offer a structured post-quantum cryptography audit for organisations that need to know where they stand and what to migrate first.&lt;/p&gt;

&lt;h2&gt;
  
  
  What you get
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CBOM cryptographic inventory&lt;/strong&gt; — a complete bill of materials for your cryptography: algorithms, keys, certificates, libraries, and protocols in scope.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shor/Grover risk analysis&lt;/strong&gt; — which assets a quantum adversary can break, and which only lose security margin.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mosca's theorem (X+Y&amp;gt;Z)&lt;/strong&gt; — shelf life of your data, plus migration time, versus time to a cryptographically relevant quantum computer, to prioritise what moves first.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Migration roadmap&lt;/strong&gt; — prioritised steps to NIST FIPS 203/204/205 (ML-KEM, ML-DSA, SLH-DSA), including hybrid migration where appropriate.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Written client report&lt;/strong&gt; — findings, priorities, and next actions, based on a 29-point methodology across 6 phases.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Tooling
&lt;/h2&gt;

&lt;p&gt;liboqs, oqs-provider, CBOMkit, PQCscan — plus a purpose-built audit parser with a 140-record knowledge base covering tools, standards, national programs, and published audit cases.&lt;/p&gt;

&lt;h2&gt;
  
  
  Timeline
&lt;/h2&gt;

&lt;p&gt;Six weeks: weeks 1–2 inventory, week 3 risk analysis, weeks 4–5 roadmap, week 6 report and review.&lt;/p&gt;

&lt;h2&gt;
  
  
  Hire me
&lt;/h2&gt;

&lt;p&gt;Find me on LaborX — freelancer profile Muse Notes (Writing and Translation).&lt;/p&gt;

&lt;p&gt;You can also leave a comment here and I will reply.&lt;/p&gt;

</description>
      <category>postquantum</category>
      <category>cryptography</category>
      <category>security</category>
      <category>audit</category>
    </item>
  </channel>
</rss>
