ChainSight
Sign in

Supply-chain security on Azure AI Foundry

From advisory to a verified fix.

Foundry agents learn every component in the estate, rank the risk that can actually reach production, repair the build, and ship a signed change with the evidence attached.

Sign inStart the guided demo
  • Azure DevOps and AKS
  • Foundry agents on the estate
  • Reachability before the ticket
  • Notation signatures at the cluster door

Three readings from the guided demo

Demo Lab estate. Twelve services, one open advisory. These are the numbers the console already measures.

Exposure window on the open advisory

14min

Reachable findings fixed within policy

92%

Services shipping a current SBOM

100%

What the agents are for

  1. 01

    Know every component

    Packages, images, pipelines and deployments sit on one graph, each tied to the service and the person who owns it. A version is recorded when the build resolves it.

  2. 02

    Rank real risk

    An advisory names a package. ChainSight names the services that call the vulnerable code, and writes VEX for the ones that never do. The queue is the blast radius.

  3. 03

    Ship a verified fix

    A Foundry agent opens the pull request, repairs the build that fails on upgrade, and attaches the signature with the evidence. The merge is a verified fix.

The estate, in three diagrams

The same chain the agents read: what resolved, where the work clustered, and the notes a fix has to carry.

Sync graphpkgbuildservice

Sync graph

Resolution stays one picture, from the package that landed to the service that runs it.

Activity heat

Builds and agent runs, read across the period, with quiet and active both labeled.

Stacked notes

The change carries its SBOM, its reachability verdict, and its signature.