Blog Post

Microsoft Security Community Blog
4 MIN READ

Microsoft Leads a New Era of Software Supply Chain Transparency

ShubhraS's avatar
ShubhraS
Icon for Microsoft rankMicrosoft
Jun 15, 2026

Microsoft has launched the general availability of Microsoft’s Signing Transparency (MST), a pioneering solution for software supply chain integrity based on the SCITT standard. This initiative enhances trust by logging every critical software build in an open, tamper-evident blockchain based ledger. This advancement exemplifies Microsoft's commitment to Zero Trust principles and industry-wide transparency. This service is currently providing transparency for Microsoft services like Microsoft Azure Attestation, Managed HSM, Azure confidential ledger, and Microsoft Signing Transparency.

Today, Microsoft announces the general availability of Microsoft’s Signing Transparency (MST) – a first-of-its-kind capability that brings unprecedented visibility and trust to our software supply chain. With this release, Microsoft is leading the industry by recording the build of critical cloud services into a publicly readable and verifiable SCITT standard (Supply Chain Integrity, Transparency, and Trust) compliant blockchain ledger. This means every production software build for in scope services like Azure Attestation and Azure Managed HSM (Hardware Security Module), Azure confidential ledger, Microsoft Signing Transparency itself (and others over time) – is now logged in an immutable, tamper-evident record. Only builds that are in the MST ledger are deployed to production; this gives customers confidence that the supply chain for these critical services can be audited at anytime. 

Notably, the MST ledger is fully open source and built to align with the emerging IETF SCITT standard. By embracing SCITT’s principles and open protocols, Microsoft ensures that MST not only secures our own ecosystem but also contributes to a broader industry movement toward standardized supply chain transparency. The open-source MST ledger serves as a verifiable trust anchor that any organization or researcher can inspect, audit, or even integrate with their own tooling. MST itself meets the highest levels of transparency, backed by a tamper-proof confidential ledger, open-source, and independently verified. Specifically, we are making the foundation of our trust model transparent and accessible to everyone – reinforcing that trust must be earned through proof, not just promises. 

This launch marks a major milestone in our commitment to Zero Trust principles, extending “never trust, always verify” all the way into the build itself. Building on a public preview introduced late last year, MST’s general availability delivers verifiable transparency at the software level. It transforms traditional code signing with an additive trust layer that is accessible via an open verification model. Every new software update is accompanied by a publicly auditable proof of integrity, enabling security teams to proactively confirm that each update is authentic and unaltered. 

To help organizations get the most out of this capability, we are also introducing a free tool to explore the contents – Ledger Explorer – an offline tool that allows security teams to examine MST ledger entries, verify cryptographic proofs, and even validate the ledger’s integrity independently. This tool, combined with MST’s open design, ensures that every Microsoft customer – and the broader community – can hold us accountable in real time for the software we run on their behalf. 

Key Benefits of Microsoft’s Signing Transparency (MST)

  • Verified Code Integrity – Every software release is cryptographically logged in MST’s ledgers. This makes each build tamper-evident and traceable. If an attacker attempts to inject malicious code or sign an unauthorized update, it will be evident through the well-defined validation step built into the SCITT standard. Organizations gain the assurance that code integrity can be independently confirmed at any time. 
  • Independent Verification & Zero Trust – MST enables customers and auditors to verify software authenticity on their own, without having to solely rely on vendor attestations. For each update, Microsoft provides a transparency “receipt” (proof of logging) that you can use to prove the update was officially published and unaltered. This fosters a “don’t just trust, verify” approach, empowering security teams to double-check everything running in their environment aligns with what Microsoft intended. 
  • Audit-Trail & Compliance – The transparency ledger creates a permanent, auditable timeline of code deployments. Every entry is a record of what was released and when, backed by cryptographic proofs. This simplifies compliance reporting and accelerates forensic analysis. In the event of an incident, you can quickly audit the ledger to see if any unexpected code was introduced. For highly regulated industries, MST offers concrete evidence of software integrity and policy compliance over time. 
  • Leadership & Open Standards – We are delivering real transparency now, encouraging a future where all critical software is released with verifiable integrity. MST’s open source implementation and SCITT-compliant design exemplify our commitment to openness and collaboration. We believe widespread adoption of these standards will strengthen supply chain security for everyone, making trust verification a universal practice. 

Next Steps

Microsoft’s Signing Transparency is more than a new security feature and shapes the advances in trust technology. As threats grow more sophisticated, we must evolve the way we assure our customers about the software they depend on. With MST now generally available, we are leading by example: proving that it is possible to open up the traditionally opaque process of software deployment and turn it into a source of strength and trust, i.e., empowering each person with verifiable transparency. 

We invite the industry to join us on this journey and get started by reading the documentation and exploring Ledger Explorer today! Together, by embracing transparency and open standards, we can turn “trust but verify” from a slogan into an everyday reality for digital infrastructure. 

Updated Jun 22, 2026
Version 4.0

3 Comments

  • imran-siddique's avatar
    imran-siddique
    Copper Contributor

    On https://github.com/microsoft/agent-governance-toolkit - The Merkle-chained audit chain shipped in AGT is architecturally the same model as SCITT, self-hosted today, SCITT is the externalized standardized version. AGT's SBOM output (SPDX + CycloneDX) + Ed25519 signing maps directly to MST's artifact transparency use case. AGT's ADR-0009 cites RFC 9334 RATS Architecture, the exact framework SCITT integrates with for hardware attestation.

  • MST is essentially Certificate Transparency for code signing, and the post is refreshingly honest about why that matters. The value isn't stopping a stolen key from producing a valid signature. It's that the misuse can't happen quietly anymore. Web PKI made that same trade a decade ago and it held up well.

    From (my) detection and IR side, the signing event interests me less than the question of who is watching the ledger afterwards. The receipt proves inclusion at signing time, fine. But that only buys you something if someone is checking the log for entries under their own signing identity that nobody authorized. Same discipline as watching CT logs for certs issued against your domains. Skip that and you have great forensics for after an incident and not much of a control during one.

    Worth naming what it doesn't cover, too. A SolarWinds-style compromise, where the build is tampered with before a legitimate signer signs it, still produces a valid and logged signature. MST won't flag that on its own. What it does is move the question from "was this signed" to "did we expect this signing event", and answering that is a baselining problem. You need to know what normal signing activity looks like before an unexpected entry means anything.

    Two things I'd want answered. Is there consumer-side guidance or tooling for subscribing to ledger entries for a given identity and alerting on the ones you didn't expect? And does GA mean customers can sign their own artifacts through MST, or is this Microsoft attesting its own releases with the ledger open for inspection? The monitoring approach changes a lot depending on which one it is.

    • ShubhraS's avatar
      ShubhraS
      Icon for Microsoft rankMicrosoft

      Hi Marcel_Graewer​  - Thanks for your insights and feedback! In regard to the questions at the end, 1. we have alerting on ledger entries on our roadmap 2. this GA allows for inspection of MST for the Microsoft services named in the blog. We have been looking at customer interest in signing their own artifacts and making it transparent via MST ledger. If you'd like to join a feedback panel, please contact me directly.