# software artifact signing

A cryptographic security process that digitally signs software artifacts to verify their integrity, authenticity, and provenance before distribution or deployment.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Visual Attribution Limits and Graded Provenance Auditing in Commercial Video-Generation APIs

DevFeed: [Visual Attribution Limits and Graded Provenance Auditing in Commercial Video-Generation APIs](<https://devfeed.tech/articles/visual-attribution-limits-and-graded-provenance-auditing-in-commercial-video-generation-apis-146060.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.26508>)

Author: Haocheng Mei, Yuchuan Tian, Yingte Shu, Chao Xu, Kai Han, Hanting Chen, Yunhe Wang

Published: 2026-11-20T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [API Monetization](<https://devfeed.tech/topics/api-monetization.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-cv](<https://devfeed.tech/tags/cs-cv.md>), [generation](<https://devfeed.tech/tags/generation.md>), [limits](<https://devfeed.tech/tags/limits.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [video](<https://devfeed.tech/tags/video.md>), [video-generation](<https://devfeed.tech/tags/video-generation.md>)

### AI overview

The audit finds that delivered video files alone provide weak evidence of origin: six-model container and bitstream accuracy dropped from 83.9% on raw files to 45.3% after uniform re-encoding, while frame-rate subsampling from 24 to 3 fps raised pooled D3 AUROC from 0.845 to 0.988. The authors reserve accusations for authenticated provenance contradictions or duplicate signed instances under fresh-generation contracts, excluding retries and idempotent returns. Unverifiable deliveries from signed endpoints prompt requests for original files under pass-through clauses; archive-reuse and delivery-parameter screens support review only. Across 19 endpoints, only BytePlus authenticated tier claims under the pinned policy, covering 187 of 187 audited deliveries across three Seedance tiers. Processed Seedance files became unverifiable after tested remuxing and re-encoding. The audit flagged all 100 tested raw 720p signed tier swaps, with no observed false flags in the tested honest pools; these results are limited to the tested cases.

### Source excerpt

arXiv:2611.26508v1 Announce Type: new Abstract: Commercial video-generation APIs bill by model and tier, while intermediaries could substitute cheaper models, lower tiers, or cached clips. What can a delivered file establish about its origin? We combine measurements of passive attribution and cryptographic provenance into a graded audit. We test attribution probes and zero-shot detectors under re-encoding, downscaling, and frame-rate changes, and survey C2PA and GB 45438 metadata across 19 commercial endpoints. Only authenticated provenance supports accusations: tier contradictions or duplicate signed instances under fresh-generation contracts, excluding retries and idempotent returns. Unverifiable signed-endpoint deliveries trigger original-file demands under pass-through clauses; archive-reuse and delivery-parameter screens support review only. Six-model container and bitstream accuracy falls from 83.9% on raw files to 45.3% after uniform re-encoding, using different feature sets. Subsampling real references from 24 to 3 fps raises pooled D3 AUROC from 0.845 to 0.988. Only BytePlus authenticates tier claims under our pinned policy, including 187/187 audited deliveries across three Seedance tiers; tested remuxing and re-encoding leave processed Seedance files unverifiable. The audit identifies authenticated contradictions in 100/100 raw 720p signed tier-swap cases, with zero observed false flags on the tested honest pools.

## A-Tag: Cryptographic File Tagging with Enforced Live Human Presence

DevFeed: [A-Tag: Cryptographic File Tagging with Enforced Live Human Presence](<https://devfeed.tech/articles/a-tag-cryptographic-file-tagging-with-enforced-live-human-presence-143125.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.23602>)

Author: Mohammed Gharib, Sam Burns, Martin Zizi

Published: 2026-11-19T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-generated-content](<https://devfeed.tech/tags/ai-generated-content.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [automated](<https://devfeed.tech/tags/automated.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [control](<https://devfeed.tech/tags/control.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [digital](<https://devfeed.tech/tags/digital.md>), [digital-signatures](<https://devfeed.tech/tags/digital-signatures.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [event](<https://devfeed.tech/tags/event.md>), [file](<https://devfeed.tech/tags/file.md>), [framework](<https://devfeed.tech/tags/framework.md>), [human-in-the-loop](<https://devfeed.tech/tags/human-in-the-loop.md>), [identity](<https://devfeed.tech/tags/identity.md>), [live](<https://devfeed.tech/tags/live.md>), [presence](<https://devfeed.tech/tags/presence.md>), [tag](<https://devfeed.tech/tags/tag.md>)

### AI overview

A-Tag binds a digital file to a verified instance of live human presence at tagging time, addressing a gap left by signatures and authentication, which establish identity or integrity but not live presence. It combines micro-motion-based liveness checks, cryptographic binding to the artifact, and publicly verifiable logging. The transferable tag attests that a live human triggered the action; it does not establish the actor's identity, the file's origin, or its semantic content. The authors report implementation on commodity devices, over 99% recovery success for image artifacts after real-world transformations, deterministic verification, sub-second verification, and practical tagging latency. The abstract says the system's guarantees and limitations are analyzed but does not detail them.

### Source excerpt

arXiv:2611.23602v1 Announce Type: new Abstract: The increasing autonomy of software agents and the proliferation of AI-generated content have weakened the reliability of digital actions as evidence of human involvement. Existing mechanisms, such as digital signatures and authentication protocols, verify identity and integrity, but do not establish whether a live human was present at the time an action was performed. In this paper, we introduce A-Tag, a system for verifiable human-in-the-loop tagging of digital artifacts. A-Tag cryptographically binds a file to a verified instance of live human presence at the moment of tagging. The resulting tag serves as a persistent and transferable proof that the action was triggered by a live human, without making claims about the origin, identity of the actor, or semantic content of the file. A-Tag is a modular framework combining liveness verification based on micro-motion signals shaped by human motor control, a secure cryptographic binding between the verified event and the artifact, and a publicly verifiable logging mechanism enabling independent validation. We formalize security properties of human presence signals, define an adversarial model capturing automated and relay attacks, and analyze the system's guarantees and limitations. We implement A-Tag on commodity devices and evaluate it under realistic conditions. Our evaluation shows that A-Tag provides cryptographically sound artifact binding with deterministic verification, while enabling robust recovery under real-world transformations, achieving over 99 percent success for image-based artifacts, and maintaining sub-second verification and practical tagging latency.

## How AT&T Turns Signed Evidence into Deployment Decisions with Kyverno

DevFeed: [How AT&T Turns Signed Evidence into Deployment Decisions with Kyverno](<https://devfeed.tech/articles/how-at-t-turns-signed-evidence-into-deployment-decisions-with-kyverno-139209.md>)

Original publisher: [Read original article](<https://nirmata.com/2026/11/18/how-att-turns-signed-evidence-into-deployment-decisions-with-kyverno/>)

Author: Sagar Kundral

Published: 2026-11-18T01:14:41.413057Z

Content type: article

Language: en

Sources: [Nirmata](<https://devfeed.tech/sources/nirmata.md>)

Topics: [Kyverno](<https://devfeed.tech/topics/kyverno.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [audit](<https://devfeed.tech/topics/audit.md>)

Tags: [admission](<https://devfeed.tech/tags/admission.md>), [at-t](<https://devfeed.tech/tags/at-t.md>), [attestations](<https://devfeed.tech/tags/attestations.md>), [cel](<https://devfeed.tech/tags/cel.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [image-verification](<https://devfeed.tech/tags/image-verification.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [kyverno](<https://devfeed.tech/tags/kyverno.md>), [policy-as-code](<https://devfeed.tech/tags/policy-as-code.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [sigstore](<https://devfeed.tech/tags/sigstore.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

AT&T uses Kyverno ImageValidatingPolicy rules in CEL to turn verified image attestations into environment-specific admission decisions: a signed image can pass in development and fail in production if it lacks required evidence. The policy verifies signatures before reading claims, checks who built the image, then applies destination requirements; promotion checks do not replace admission because requests, policies and time-sensitive evidence can differ. AT&T uses one engine for internal and approved upstream or vendor images, with explicit trust roots; support for GitHub's private Sigstore root arrived in Kyverno 1.19, and the talk recommends 1.19.2 or later for Enforce mode. A single-laptop benchmark showed fewer registry calls and lower latency in newer versions, but these are not production figures and should be measured with local policies and registries. The talk also recommends planning failure behavior and narrow, expiring exceptions; retaining per-request decision evidence; and rolling out through audit, remediation, tiered enforcement and gradual expansion.

### Source excerpt

AT&T verifies signed provenance and SBOM attestations with a Kyverno ImageValidatingPolicy in CEL, then applies each environment's rules at admission.

## Beyond SHA pinning: Why immutability isn't provenance in GitHub Actions

DevFeed: [Beyond SHA pinning: Why immutability isn't provenance in GitHub Actions](<https://devfeed.tech/articles/beyond-sha-pinning-why-immutability-isn-t-provenance-in-github-actions-122069.md>)

Original publisher: [Read original article](<https://platformengineering.org/blog/beyond-sha-pinning-why-immutability-isnt-provenance-in-github-actions>)

Author: Erika Heidi

Published: 2026-11-06T20:11:44Z

Content type: article

Language: en

Sources: [Platform Engineering Blog](<https://devfeed.tech/sources/platform-engineering-blog.md>)

Topics: [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [chainguard actions](<https://devfeed.tech/topics/chainguard-actions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [GitHub](<https://devfeed.tech/topics/github.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [can](<https://devfeed.tech/tags/can.md>), [cd](<https://devfeed.tech/tags/cd.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [commits](<https://devfeed.tech/tags/commits.md>), [doesn-t](<https://devfeed.tech/tags/doesn-t.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [immutability](<https://devfeed.tech/tags/immutability.md>), [isn-t](<https://devfeed.tech/tags/isn-t.md>), [learn](<https://devfeed.tech/tags/learn.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-teams](<https://devfeed.tech/tags/platform-teams.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [take](<https://devfeed.tech/tags/take.md>), [teams](<https://devfeed.tech/tags/teams.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

SHA pinning prevents a GitHub Action's reference from following a moved tag, but it does not establish who authored the pinned commit, whether it belongs to the intended project, or what a container action downloads at runtime. The article describes "imposter commits" reachable through an upstream repository URL despite existing only in a fork, and says such a commit could pass SHA format enforcement. It recommends pinning every action and reviewing automated pin updates, while treating provenance as a separate requirement. GitHub's immutable releases lock tags and assets and include Sigstore attestations, but adoption is opt-in for action maintainers. Workflow lock files pin actions and transitive dependencies and require commits to exist on source branches; they were described as in public preview. Other approaches include internal mirrors, provenance verification, and curated catalogs, each requiring ongoing maintenance or trust-policy decisions. The article presents Chainguard Actions as a curated, rebuilt catalog, and advises shrinking the attack surface with minimal hardened images.

### Source excerpt

Learn why SHA pinning in GitHub Actions doesn't guarantee provenance, how imposter commits exploit CI/CD workflows, and key steps platform teams can take to secure their supply chain.

## ModelProof: Proving an AI Model Hasn't Been Tampered With, Stored Forever on Arweave

DevFeed: [ModelProof: Proving an AI Model Hasn't Been Tampered With, Stored Forever on Arweave](<https://devfeed.tech/articles/modelproof-proving-an-ai-model-hasn-t-been-tampered-with-stored-forever-on-arweave-106126.md>)

Original publisher: [Read original article](<https://hackernoon.com/modelproof-proving-an-ai-model-hasnt-been-tampered-with-stored-forever-on-arweave?source=rss>)

Author: Lawal Ridwan

Published: 2026-10-29T07:14:26Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [ML model versioning](<https://devfeed.tech/topics/ml-model-versioning.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [sha256](<https://devfeed.tech/topics/sha256.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [PWA](<https://devfeed.tech/topics/pwa.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-model-provenance](<https://devfeed.tech/tags/ai-model-provenance.md>), [ai-model-tampering](<https://devfeed.tech/tags/ai-model-tampering.md>), [arweave](<https://devfeed.tech/tags/arweave.md>), [cryptographic-signatures](<https://devfeed.tech/tags/cryptographic-signatures.md>), [decentralize-ai-hackathon](<https://devfeed.tech/tags/decentralize-ai-hackathon.md>), [model](<https://devfeed.tech/tags/model.md>), [modelproof](<https://devfeed.tech/tags/modelproof.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [web3](<https://devfeed.tech/tags/web3.md>)

### AI overview

ModelProof creates a signed, publicly verifiable record of AI model files without a backend. In a browser, it hashes files in 4 MiB chunks, builds a Merkle root and whole-file SHA-256, and signs a manifest with an Ed25519 key. It packages the manifest as an ANS-104 item and publishes it through ArDrive Turbo; uploads under 100 KiB are free. Verification checks the signature and hashes and identifies changed chunks by byte range. The article demonstrates this with a modified model weight that is flagged in the corresponding chunk. The signature links a manifest to a key but does not establish that the publisher or model is trustworthy, nor that training claims are true or the model is safe. Free manifests cover about 6 GB at the default chunk size; larger models need larger chunks or a funded wallet. Keys stored in IndexedDB should be backed up, and Arweave gateway indexing can take minutes.

### Source excerpt

ModelProof hashes AI models in your browser, signs a provenance manifest and stores it free and forever on Arweave, so anyone can verify the weights.

## One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images

DevFeed: [One Signed Answer: SLSA Verification Summaries for registry.k8s.io Images](<https://devfeed.tech/articles/one-signed-answer-slsa-verification-summaries-for-registry-k8s-io-images-104466.md>)

Original publisher: [Read original article](<https://www.kubernetes.dev/blog/2026/10/28/registry-k8s-io-verification-summaries/>)

Author: The Kubernetes Authors

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Kubernetes Contributors Blog](<https://devfeed.tech/sources/kubernetes-contributors-blog.md>)

Topics: [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [build](<https://devfeed.tech/tags/build.md>), [builder](<https://devfeed.tech/tags/builder.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [identity](<https://devfeed.tech/tags/identity.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [k8s](<https://devfeed.tech/tags/k8s.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [manifest](<https://devfeed.tech/tags/manifest.md>), [policy](<https://devfeed.tech/tags/policy.md>), [promotion](<https://devfeed.tech/tags/promotion.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [registry](<https://devfeed.tech/tags/registry.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [repository](<https://devfeed.tech/tags/repository.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

The Kubernetes image promoter now evaluates staging-image provenance against each project's policy in kubernetes/k8s.io, copies accepted attestations to registry.k8s.io, and publishes a signed SLSA verification summary (VSA) for each promoted image. Consumers can check the summary signer, verifier ID, result, and required build level with cosign and jq, or download it and run slsa-verifier with crane. Pin both signer and level: PASSED alone may mean only that promotion used a reviewed manifest, and an image without a policy can receive SLSA_BUILD_LEVEL_UNEVALUATED. SPO's v1.1.1 operator images, binaries, and Helm chart reach level 3; its bundle reaches only level 1 in that release, so a level 3 check fails. Projects need signed staging provenance, a manifest policy, and a test run. Cloud Build can provide level 1; level 3 requires provenance from an isolated GitHub workflow, then verification and attachment to the matching staging digest. Roll out policies in warn mode, test with kpromo cip, verify summaries, then use require to block violations. Summaries are created once at promotion, and most images promoted before October 2026 lack them; multi-architecture platform images need,

### Source excerpt

The Kubernetes community has been signing its container images since v1.24, and the images that kpromo, the Kubernetes image promoter (rewritten earlier this year), copies to registry.k8s.io get a signature. A signature answers one question: did this image go through the official promotion process? It does not answer the more interesting one: how was this image built, and from which source? Projects can attach signed SLSA provenance to their images to answer that. But to check it yourself, you have to know who builds each image, which identity signs its provenance, which builder it claims and which repository it comes from, for every project you pull from. That is a lot to ask, and in practice few people do it. Since October 2026, the image promoter does this work for you, once, at promotion time, and publishes the answer as a signed SLSA verification summary (VSA) for every image it promotes. In this blog post, I'd like to explain how it works, how you can verify it, and how your project can get its images verified at SLSA build level 1 or 3. How does it work? A project declares a provenance policy in its promoter manifest in kubernetes/k8s.io: who may sign its build attestations, which builders it trusts and at which level, and which source repositories its images come from. When a reviewed pull request promotes an image, the promoter evaluates the attestations of the staging image against that policy with the SLSA verifier, copies the accepted attestations to registry.k8s.io and writes the summary: flowchart LR build["Project build"] staging[("Staging registry")] policy["Provenance policy
in kubernetes/k8s.io"] promoter["Image promoter"] prod[("registry.k8s.io")] users["Users and clusters"] build -- "image and
signed provenance" --> staging staging --> promoter policy --> promoter promoter -- "image, attestations,
verification summary" --> prod prod -- "verify one summary" --> users The summaries are signed by a dedicated identity, promoter-summaries@

## How Anchorage Digital and Turnkey verify code with AWS Nitro Enclaves

DevFeed: [How Anchorage Digital and Turnkey verify code with AWS Nitro Enclaves](<https://devfeed.tech/articles/how-anchorage-digital-and-turnkey-verify-code-with-aws-nitro-enclaves-102661.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-anchorage-digital-and-turnkey-verify-code-with-aws-nitro-enclaves/>)

Author: Alexander Qin

Published: 2026-10-27T17:10:35Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [Nitro Isolation Engine](<https://devfeed.tech/topics/nitro-isolation-engine.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Blockchain](<https://devfeed.tech/topics/blockchain.md>), [Cryptocurrency](<https://devfeed.tech/topics/cryptocurrency.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [anchorage-digital](<https://devfeed.tech/tags/anchorage-digital.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [aws](<https://devfeed.tech/tags/aws.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [can](<https://devfeed.tech/tags/can.md>), [code](<https://devfeed.tech/tags/code.md>), [crypto](<https://devfeed.tech/tags/crypto.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [digital](<https://devfeed.tech/tags/digital.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [nitro](<https://devfeed.tech/tags/nitro.md>), [pattern](<https://devfeed.tech/tags/pattern.md>), [post](<https://devfeed.tech/tags/post.md>), [this](<https://devfeed.tech/tags/this.md>), [transaction](<https://devfeed.tech/tags/transaction.md>), [trust](<https://devfeed.tech/tags/trust.md>), [verify](<https://devfeed.tech/tags/verify.md>), [with](<https://devfeed.tech/tags/with.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Anchorage Digital and Turnkey run the open source VisualSign transaction parser in AWS Nitro Enclaves so wallets can verify which code produced a parsed transaction. The parser turns raw blockchain transactions into human readable output; clients check a signed response and Nitro attestation against expected PCR measurements derived from reproducible builds. Nitro Enclaves isolate compute and lack persistent storage and external networking. Anchorage Digital also released awsnitroverifier, a Go library for attestation and certificate chain validation, and visualsign-turnkeyclient, which offers progressively stronger checks: response signature, boot attestation with PCR validation, and full QuorumOS manifest verification including the application hash. The article presents attestation gated access as a broader pattern for sensitive workflows, while noting TVC was in private beta at publication.

### Source excerpt

Anchorage Digital and Turnkey built verifiable infrastructure on AWS Nitro Enclaves so crypto wallets can cryptographically verify which code parsed a transaction. This post covers the architecture, the attestation-gated access pattern, and how it extends to any high-trust workflow beyond blockchain.

## Tracekit: Tamper-Evident Intent-Reasoning-Action Auditing for AI Agents

DevFeed: [Tracekit: Tamper-Evident Intent-Reasoning-Action Auditing for AI Agents](<https://devfeed.tech/articles/tracekit-tamper-evident-intent-reasoning-action-auditing-for-ai-agents-94512.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2609.35659>)

Author: Bravish Ghosh (Cygnux Labs)

Published: 2026-10-22T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>)

Topics: [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [alert triage](<https://devfeed.tech/topics/alert-triage.md>)

Tags: [1-4](<https://devfeed.tech/tags/1-4.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [attack](<https://devfeed.tech/tags/attack.md>), [auditing](<https://devfeed.tech/tags/auditing.md>), [browser](<https://devfeed.tech/tags/browser.md>), [commands](<https://devfeed.tech/tags/commands.md>), [cosign](<https://devfeed.tech/tags/cosign.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cs-ce](<https://devfeed.tech/tags/cs-ce.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [ed25519](<https://devfeed.tech/tags/ed25519.md>), [email](<https://devfeed.tech/tags/email.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [exports](<https://devfeed.tech/tags/exports.md>), [hash](<https://devfeed.tech/tags/hash.md>), [hash-chain](<https://devfeed.tech/tags/hash-chain.md>), [independent](<https://devfeed.tech/tags/independent.md>), [input](<https://devfeed.tech/tags/input.md>), [reasoning](<https://devfeed.tech/tags/reasoning.md>)

### AI overview

Tracekit turns each AI agent run into an offline-verifiable audit bundle. A signer the agent cannot reach outside dev mode evaluates calls against separate policy before execution and signs calls, decisions, and results into a hash chain and Merkle tree; independent witnesses can cosign checkpoints. Python and TypeScript verifiers check exported .tkb bundles against pinned keys and report integrity separately from assurance. The system also records requests and model statements, holds calls that violate stated limits, reconciles capture layers, and replays inputs to trace causes. In the reported experiments, signed logs detected 6 of 8 tamper classes, with witnesses detecting the other two; verifiers rejected all 33 forgeries. Policy rules stopped all 570 harmful calls in the test corpus, but only 211 of 420 harmful calls written without regard to those rules, underscoring that the authors identify inaccessible signer and credentials as the protection boundary. On a held-out pool, failed tests falsely claimed as passing were detected in 86% of sessions, with 5 false findings across 1,812 honest calls. These are reported experimental results, not evidence of performance beyond theâ

### Source excerpt

arXiv:2609.35659v2 Announce Type: replace-cross Abstract: AI agents run shell commands, edit repositories, send email and move money with their operators' credentials, yet the record of what they did is usually a log the agent, or whoever runs it, can edit. We present Tracekit (open source, MIT, version 1.4.1), which turns each agent run into evidence a third party can check offline. A signer that the agent cannot reach outside dev mode decides every tool call against its own policy before it runs, and signs the call, decision and result as Ed25519 records in a per-run hash chain inside an RFC 6962 Merkle tree whose checkpoints independent witnesses can cosign. A run exports as one .tkb bundle that two independent verifiers (Python, and TypeScript, also as a browser page) check against keys the verifier pins, reporting integrity and assurance separately. Disagreements between capture layers become signed records. Tracekit also records the person's request and what the model said before each call, holds calls that break a limit the request stated, compares what was asked, said and done, and finds which input caused an action by replay. Of 21 experiments: a signed log alone detects 6 of 8 tamper classes and a witness the other two; every insider attack in two suites is caught; the signer round trip is 0.45 ms median; no acknowledged record was lost in 60 kill -9 rounds; reconciliation flags 12 of 12 seeded discrepancies; the verifiers reject all 33 forgeries. Policy rules are a tripwire, not the boundary: they stop 570 of 570 harmful calls in our corpus but 211 of 420 (50.2%) written blind to them; the protection is a signer and credentials the agent cannot reach. On a held-out pool, a failed test claimed as passing is found in 86% of sessions with 5 false findings in 1,812 honest calls, and replay names the planted cause in 6 of 6 confirmed harmful runs with a 7B model.

## Red Hat and HP: Empowering physical AI from bench to fleet

DevFeed: [Red Hat and HP: Empowering physical AI from bench to fleet](<https://devfeed.tech/articles/red-hat-and-hp-empowering-physical-ai-from-bench-to-fleet-92782.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/red-hat-and-hp-empowering-physical-ai-bench-fleet>)

Author: Jeremy Ary

Published: 2026-10-21T00:00:00Z

Content type: article

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [Physical AI](<https://devfeed.tech/topics/physical-ai.md>), [Robotics](<https://devfeed.tech/topics/robotics.md>), [Robotics Simulation](<https://devfeed.tech/topics/robotics-simulation.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [observability](<https://devfeed.tech/topics/observability.md>), [redhat](<https://devfeed.tech/topics/redhat.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [accessible](<https://devfeed.tech/tags/accessible.md>), [ai](<https://devfeed.tech/tags/ai.md>), [based](<https://devfeed.tech/tags/based.md>), [bench](<https://devfeed.tech/tags/bench.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [communities](<https://devfeed.tech/tags/communities.md>), [contributing](<https://devfeed.tech/tags/contributing.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [first](<https://devfeed.tech/tags/first.md>), [fleet](<https://devfeed.tech/tags/fleet.md>), [good](<https://devfeed.tech/tags/good.md>), [hat](<https://devfeed.tech/tags/hat.md>), [hp](<https://devfeed.tech/tags/hp.md>), [physical-ai](<https://devfeed.tech/tags/physical-ai.md>), [red](<https://devfeed.tech/tags/red.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>)

### AI overview

Red Hat and HP describe a ROS2 robot-training loop that automates evaluation, artifact signing, model registration, human-reviewed promotion, and fleet delivery. In a Gazebo simulation, the system perturbs cube positions and collects successful episodes for retraining while retaining failures for traceability. OpenShift AI trains and compares candidates on identical scenes; undertrained candidates regressed and failed evaluation, while a later candidate improved success from 81.9% to 92.5% across 360 seeded scenes. The workflow ran on one HP ZGX Fury AI station with NVIDIA GB300 architecture and 748 GB of coherent memory, with resources left available for other workloads. The authors say this avoids separate training and validation clusters and keeps proprietary data local. They also describe a planned HP and Red Hat enterprise AI platform and an open source Podman Desktop extension intended to support ROS2 builds, simulations, topic monitoring, registry tasks, and deployment.

### Source excerpt

Teaching a robot to perform its first task is thrilling, but turning that initial win into a repeatable, self-improving process capable of backing production fleets is a challenge. Communities like the one behind Robot Operating System 2 (ROS2) have made the record-train-deploy loop more accessible than ever, but challenges remain:How can we assess policy quality across iterations?Does the policy improve or is it a fluke based on a series of fortunate episodes?Can we quantify good and bad episodes contributing to successes and failures?Can we trace lineage and verify the authenticity of our ar

## Beyond container image signing: How we enforce software supply chain policies at Datadog

DevFeed: [Beyond container image signing: How we enforce software supply chain policies at Datadog](<https://devfeed.tech/articles/beyond-container-image-signing-how-we-enforce-software-supply-chain-policies-at-datadog-91078.md>)

Original publisher: [Read original article](<https://www.datadoghq.com/blog/engineering/software-supply-chain-policy-enforcement/>)

Author: Callan Lamb; Brianna Heffernen

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [Datadog](<https://devfeed.tech/sources/datadog-the-monitor-blog.md>), [Datadog](<https://devfeed.tech/sources/datadog.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [software bill of materials](<https://devfeed.tech/topics/software-bill-of-materials.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [datadog](<https://devfeed.tech/topics/datadog.md>)

Tags: [code-security](<https://devfeed.tech/tags/code-security.md>), [container](<https://devfeed.tech/tags/container.md>), [datadog](<https://devfeed.tech/tags/datadog.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [policies](<https://devfeed.tech/tags/policies.md>), [security](<https://devfeed.tech/tags/security.md>), [signing](<https://devfeed.tech/tags/signing.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [turnstile](<https://devfeed.tech/tags/turnstile.md>)

### AI overview

Container image signatures show that an image is unchanged since signing, but cannot reveal risks introduced earlier in the build or source process. Datadog's Turnstile extends verification by collecting identity-bound, signed attestations across an artifact's life cycle and evaluating them against environment-specific policies at deployment. Its dd-attest library uses ephemeral keys tied to workload identities; policy-core retrieves and verifies attestations from the DynamoDB-backed Attestation Metadata Store, evaluates Rego policies with OPA, and records a signed Verification Summary Attestation that downstream systems can verify. Policies and related libraries are distributed as OCI artifacts and verified with TUF. Turnstile supports audit, warning, and blocking modes for progressive rollout. Across about 1 million evaluation traces in August 2026, the article reports a 92.8% policy cache hit rate, 75% per-artifact cache hit rate, and evaluation latency of 36 ms at P50 and 481 ms at P99.

### Source excerpt

Datadog built Turnstile to evaluate signed attestations and enforce software supply chain policies before container images are deployed.

## Package managers have an integrity problem

DevFeed: [Package managers have an integrity problem](<https://devfeed.tech/articles/package-managers-have-an-integrity-problem-87158.md>)

Original publisher: [Read original article](<https://blog.trailofbits.com/2026/10/14/package-managers-have-an-integrity-problem/>)

Author: "Keegan Ryan"

Published: 2026-10-14T11:00:00Z

Content type: article

Language: en

Sources: [The Trail of Bits Blog](<https://devfeed.tech/sources/the-trail-of-bits-blog-2.md>), [Trail of Bits](<https://devfeed.tech/sources/the-trail-of-bits-blog.md>)

Topics: [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [sigstore policy controller](<https://devfeed.tech/topics/sigstore-policy-controller.md>), [npm-workspaces](<https://devfeed.tech/topics/npm-workspaces.md>), [Conan](<https://devfeed.tech/topics/conan.md>), [pnpm](<https://devfeed.tech/topics/pnpm.md>), [Yarn](<https://devfeed.tech/topics/yarn.md>)

Tags: [cryptography](<https://devfeed.tech/tags/cryptography.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [ecosystem-security](<https://devfeed.tech/tags/ecosystem-security.md>), [hash](<https://devfeed.tech/tags/hash.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [security](<https://devfeed.tech/tags/security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>)

### AI overview

A test of 25 popular source-code package managers found uneven protection against malicious package repositories. Fewer than half checked lockfile hashes for tampering by default, and only two verified every downloaded package. The article examines how lockfiles, signatures, and transparency logs affect package integrity, and proposes recording signer identity in lockfiles as one possible design.

### Source excerpt

I tested 25 of the most popular package managers to check whether they detect a compromised package repository injecting malicious code into legitimate packages. This code integrity problem could be solved using cryptographic hashes or signatures, but many package managers are still vulnerable to this threat. Of the 25 package managers reviewed1, fewer than half used lockfiles that checked for tampering by default, and only two verified the integrity of every package they downloaded. Supply-chain attacks caused by developer compromise are a common story, but imagine what happens if ongoing mitigation attempts, including work by Trail of Bits2, are successful. If developers of popular packages are no longer the easiest targets, attackers will shift their focus to the next weakest link in the system: the package repositories that serve the code. The cryptographic answers to this problem are more subtle than they appear, and many implementations fall short due to deliberate design choices, resource prioritization, or the complexity of developer-friendly solutions. One natural answer is to include a cryptographic hash of a package's contents in a lockfile and compare hashes after downloading the package. This automatic verification was the default behavior in about half of the package managers I tested, but others required extra configuration to include or verify these hashes, used hashes in a cryptographically insecure way, or lacked hashes entirely. This is summarized in the following table. Verifies integrity Go, vcpkg Verifies if lockfile is present Bun, Bundler, Cargo, npm, pnpm, Poetry, SwiftPM, uv, Yarn Verifies with lockfile + extra steps Conda, Gradle, Pip, NuGet, Pub Does not verify with lockfile or N/A CocoaPods, Composer, Conan, cpanminus, Gem, Maven, PowerShellGet, PSResourceGet, R Table 1: Lockfile-based security of a package manager fetching dependencies from a malicious repository, categorized by how much work it takes a developer to achieve integrity. E

## DoW Instruction 8430.01 makes software evidence a condition to operate

DevFeed: [DoW Instruction 8430.01 makes software evidence a condition to operate](<https://devfeed.tech/articles/dow-instruction-8430-01-makes-software-evidence-a-condition-to-operate-90839.md>)

Original publisher: [Read original article](<https://anchore.com/blog/dow-instruction-8430-01-makes-software-evidence-a-condition-to-operate/>)

Author: Chadd Owen

Published: 2026-10-13T12:00:00Z

Content type: article

Language: en

Sources: [Anchore](<https://devfeed.tech/sources/anchore.md>)

Topics: [authority to operate](<https://devfeed.tech/topics/authority-to-operate.md>), [anchore](<https://devfeed.tech/topics/anchore.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>), [qualitygates](<https://devfeed.tech/topics/qualitygates.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [Self-hosted](<https://devfeed.tech/topics/self-hosted.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [all](<https://devfeed.tech/tags/all.md>), [anchore](<https://devfeed.tech/tags/anchore.md>), [application](<https://devfeed.tech/tags/application.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [blog](<https://devfeed.tech/tags/blog.md>), [build](<https://devfeed.tech/tags/build.md>), [component](<https://devfeed.tech/tags/component.md>), [composition](<https://devfeed.tech/tags/composition.md>), [condition](<https://devfeed.tech/tags/condition.md>), [department](<https://devfeed.tech/tags/department.md>), [dow](<https://devfeed.tech/tags/dow.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [it](<https://devfeed.tech/tags/it.md>), [machine](<https://devfeed.tech/tags/machine.md>), [networks](<https://devfeed.tech/tags/networks.md>), [security](<https://devfeed.tech/tags/security.md>), [software](<https://devfeed.tech/tags/software.md>), [systems](<https://devfeed.tech/tags/systems.md>), [war](<https://devfeed.tech/tags/war.md>)

### AI overview

Effective September 8, 2026, DoWI 8430.01 makes machine-readable evidence of software composition, build integrity, and application security a condition for operating covered software on DoW networks. It covers DoW Components and software used by or for the DoW, with a research-stage carve-out that ends at transition to acquisition or operational use. Requirements described include SBOMs for custom and commercial software, secure automated builds with provenance, continuous CI/CD scanning and monitoring, third-party component risk review, and security testing and records for AI-generated code. The post says Anchore Enterprise can generate or import SBOMs, enforce pipeline policies, monitor stored SBOMs against updated vulnerability feeds, and expose evidence through APIs and tools; it also describes self-hosted and air-gapped deployment. Planned features have no stated delivery timing. Anchore verifies signatures and provenance but does not generate them or replace SAST, DAST, fuzzing, or penetration testing; authorization remains with the authorizing official.

### Source excerpt

The post DoW Instruction 8430.01 makes software evidence a condition to operate appeared first on Anchore.If you build or deliver software for the Department of War (DoW), your next authorization conversation just changed. As of September 8, 2026, all software operated on DoW networks and systems must be supported by machine-readable evidence of its component composition, build integrity, and application security (§3.5.a(1)). That's no longer a best practice. It is [...]

## Quantum-resistant signing on AWS, Part 1: Build a software supply chain with ML-DSA

DevFeed: [Quantum-resistant signing on AWS, Part 1: Build a software supply chain with ML-DSA](<https://devfeed.tech/articles/quantum-resistant-signing-on-aws-part-1-build-a-software-supply-chain-with-ml-dsa-85603.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/security/quantum-resistant-signing-on-aws-part-1-build-a-software-supply-chain-with-ml-dsa/>)

Author: Harshvardhan Chunawala

Published: 2026-10-12T20:12:53Z

Content type: tutorial

Language: en

Sources: [AWS Security Blog](<https://devfeed.tech/sources/aws-security-blog.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [software bill of materials](<https://devfeed.tech/topics/software-bill-of-materials.md>), [cyber resilience act](<https://devfeed.tech/topics/cyber-resilience-act.md>), [reproducible builds](<https://devfeed.tech/topics/reproducible-builds.md>)

Tags: [amazon-elastic-container-registry](<https://devfeed.tech/tags/amazon-elastic-container-registry.md>), [amazon-elastic-kubernetes-service](<https://devfeed.tech/tags/amazon-elastic-kubernetes-service.md>), [amazon-inspector](<https://devfeed.tech/tags/amazon-inspector.md>), [amazon-simple-storage-service-s3](<https://devfeed.tech/tags/amazon-simple-storage-service-s3.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cli](<https://devfeed.tech/tags/aws-cli.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [aws-key-management-service](<https://devfeed.tech/tags/aws-key-management-service.md>), [aws-key-management-service-kms](<https://devfeed.tech/tags/aws-key-management-service-kms.md>), [aws-organizations](<https://devfeed.tech/tags/aws-organizations.md>), [aws-private-certificate-authority](<https://devfeed.tech/tags/aws-private-certificate-authority.md>), [aws-secrets-manager](<https://devfeed.tech/tags/aws-secrets-manager.md>), [aws-security-token-service](<https://devfeed.tech/tags/aws-security-token-service.md>), [aws-systems-manager](<https://devfeed.tech/tags/aws-systems-manager.md>), [best-practices](<https://devfeed.tech/tags/best-practices.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [configuration-compliance-and-auditing](<https://devfeed.tech/tags/configuration-compliance-and-auditing.md>), [expert-400](<https://devfeed.tech/tags/expert-400.md>), [ml-dsa](<https://devfeed.tech/tags/ml-dsa.md>), [quantum-technologies](<https://devfeed.tech/tags/quantum-technologies.md>), [security](<https://devfeed.tech/tags/security.md>), [security-blog](<https://devfeed.tech/tags/security-blog.md>), [security-identity-compliance](<https://devfeed.tech/tags/security-identity-compliance.md>), [signing](<https://devfeed.tech/tags/signing.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

This tutorial explains how to build a quantum-resistant software supply chain on AWS using ML-DSA keys, certificates, and workload identity. It walks through signing binaries, container images, and SBOMs, then verifying signatures and enforcing deployment policies.

### Source excerpt

Software supply chain attacks have grown in both frequency and sophistication. Recent high-profile compromises of build systems and open source dependencies demonstrate that attackers increasingly target the trust mechanisms that verify software integrity. Those trust mechanisms rely on digital signature algorithms, and today many use traditional algorithms such as Rivest-Shamir-Adleman (RSA) and the Elliptic Curve [...]

## Inspecting Multi-Platform Docker Images, SBOMs, and SLSA Provenance With Buildx

DevFeed: [Inspecting Multi-Platform Docker Images, SBOMs, and SLSA Provenance With Buildx](<https://devfeed.tech/articles/inspecting-multi-platform-docker-images-sboms-and-slsa-provenance-with-buildx-84158.md>)

Original publisher: [Read original article](<https://hackernoon.com/inspecting-multi-platform-docker-images-sboms-and-slsa-provenance-with-buildx?source=rss>)

Author: Sangharsh Agarwal

Published: 2026-10-09T08:27:05Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Docker](<https://devfeed.tech/topics/docker.md>), [grype](<https://devfeed.tech/topics/grype.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Docker Hub](<https://devfeed.tech/topics/docker-hub.md>)

Tags: [container-security](<https://devfeed.tech/tags/container-security.md>), [docker-bake](<https://devfeed.tech/tags/docker-bake.md>), [docker-buildx](<https://devfeed.tech/tags/docker-buildx.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [go](<https://devfeed.tech/tags/go.md>), [oci-image-index](<https://devfeed.tech/tags/oci-image-index.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [sbom](<https://devfeed.tech/tags/sbom.md>), [sboms](<https://devfeed.tech/tags/sboms.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [slsa-provenance](<https://devfeed.tech/tags/slsa-provenance.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [software-supply-chain-security](<https://devfeed.tech/tags/software-supply-chain-security.md>)

### AI overview

A hands-on example uses Docker Buildx to publish amd64 and arm64 images with SBOMs and provenance, then inspects the registry artifacts. The two platform SBOMs list the same 19 package names and versions, while the provenance records resolved dependencies for amd64. The article cautions that these observations do not verify the builder's identity, establish a SLSA level, or prove the images are safe.

### Source excerpt

Build and inspect multi-platform Docker images with Buildx, SBOMs, and SLSA provenance. See what published attestations reveal and what they don't prove.

## Apple's Verified Photography System

DevFeed: [Apple's Verified Photography System](<https://devfeed.tech/articles/apple-s-verified-photography-system-66709.md>)

Original publisher: [Read original article](<https://www.schneier.com/blog/archives/2026/10/apples-verified-photography-system.html>)

Author: Bruce Schneier

Published: 2026-10-07T11:07:36Z

Content type: news

Language: en

Sources: [Schneier on Security](<https://devfeed.tech/sources/schneier-on-security.md>)

Topics: [ai security](<https://devfeed.tech/topics/ai-security.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [apple-reference-image](<https://devfeed.tech/tags/apple-reference-image.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [cameras](<https://devfeed.tech/tags/cameras.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [reports](<https://devfeed.tech/tags/reports.md>), [signing](<https://devfeed.tech/tags/signing.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

### AI overview

Apple's Reference Image system verifies that images are unchanged from capture on supported iPhones while avoiding public identification of the photographer or device. Apple says its signing and validation process protects image data from access, including by Apple, and that revocation checks use on-device lists.

### Source excerpt

Apple just released a system called "Reference Image." It can verify the image is exactly as taken by an iPhone--new models only--without tying it to a specific iPhone or photographer. It can also verify that multiple images came from the same iPhone. Other industry solutions require a photographer or institution to vouch for an image using their own credentials. We are concerned this puts some photographers, such as those operating in conflict zones, in a difficult position; it should not be necessary to forgo anonymity in order to prove image authenticity. We built Apple Reference Image to avoid using an explicit, public credential for photographers, and to avoid even implicit public association between different photos taken by the same sensor. The final reference image is instead signed by Apple's signing service, after validation by PCC. That signature is backed by Apple's strongest technical guarantees...

## Model Integrity Is Not Model Provenance: Understanding the Limits of OMS

DevFeed: [Model Integrity Is Not Model Provenance: Understanding the Limits of OMS](<https://devfeed.tech/articles/model-integrity-is-not-model-provenance-understanding-the-limits-of-oms-62274.md>)

Original publisher: [Read original article](<https://hackernoon.com/model-integrity-is-not-model-provenance-understanding-the-limits-of-oms?source=rss>)

Author: Kenneth Onyebuchi

Published: 2026-09-29T16:36:47Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>)

Tags: [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-supply-chain-security](<https://devfeed.tech/tags/ai-supply-chain-security.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [mlops-security](<https://devfeed.tech/tags/mlops-security.md>), [model-attestation](<https://devfeed.tech/tags/model-attestation.md>), [openssf-model-signing](<https://devfeed.tech/tags/openssf-model-signing.md>), [pki](<https://devfeed.tech/tags/pki.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [sigstore](<https://devfeed.tech/tags/sigstore.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>)

### AI overview

The OpenSSF Model Signing specification uses cryptographic signatures and manifests to verify that a model's files match what was signed and to trace the signature to a key. It does not independently establish who was authorized to train or release the model, what data or pipeline produced it, or whether optional metadata is accurate.

### Source excerpt

AI model signing proves a model wasn't tampered with. Here's why it still can't tell you who trained it or whether they were allowed to.

## Eight ProveKit Use Cases for Privacy-Preserving Identity Checks

DevFeed: [Eight ProveKit Use Cases for Privacy-Preserving Identity Checks](<https://devfeed.tech/articles/world-s-provekit-can-verify-citizens-hotel-guests-and-ai-agents-without-taking-their-id-61151.md>)

Original publisher: [Read original article](<https://hackernoon.com/worlds-provekit-can-verify-citizens-hotel-guests-and-ai-agents-without-taking-their-id?source=rss>)

Author: Ishan Pandey

Published: 2026-09-28T10:40:59Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [UI/UX Design](<https://devfeed.tech/topics/ui-ux-design.md>)

Tags: [ai-and-ml](<https://devfeed.tech/tags/ai-and-ml.md>), [blockchain](<https://devfeed.tech/tags/blockchain.md>), [business](<https://devfeed.tech/tags/business.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [developer](<https://devfeed.tech/tags/developer.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [identity](<https://devfeed.tech/tags/identity.md>), [nfc](<https://devfeed.tech/tags/nfc.md>), [provekit](<https://devfeed.tech/tags/provekit.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [web3](<https://devfeed.tech/tags/web3.md>), [world](<https://devfeed.tech/tags/world.md>)

### AI overview

ProveKit lets a phone verify a specific fact from an identity document, passkey, anonymous credential, or developer-defined rule, then share a compact proof without revealing the underlying identity data. The article outlines eight possible uses, including citizen-only petitions, verified reviews, age-restricted spaces, AI agent limits, and account recovery. It also describes the developer inputs, verification process, and reported proving times on two iPhones.

### Source excerpt

Eight creative ProveKit use cases: citizen-only petitions, verified reviews, kids-only spaces, AI agent limits and account recovery with no stored ID.

## The Provenance Gap in Agent-Written Code

DevFeed: [The Provenance Gap in Agent-Written Code](<https://devfeed.tech/articles/the-provenance-gap-in-agent-written-code-55875.md>)

Original publisher: [Read original article](<https://swamp-club.com/feed/p/759986b0-a1e1-4a31-a029-bebac3ee394e/go>)

Author: stack72

Published: 2026-09-17T21:22:09Z

Content type: article

Language: en

Sources: [Swamp Club Feed](<https://devfeed.tech/sources/swamp-club-feed.md>)

Topics: [AI software supply chain security](<https://devfeed.tech/topics/ai-software-supply-chain-security.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [Code review](<https://devfeed.tech/topics/code-review.md>), [Post Mortem](<https://devfeed.tech/topics/post-mortem.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>)

Tags: [accountability](<https://devfeed.tech/tags/accountability.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-verification](<https://devfeed.tech/tags/agent-verification.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [attestation](<https://devfeed.tech/tags/attestation.md>), [audit](<https://devfeed.tech/tags/audit.md>), [authoring](<https://devfeed.tech/tags/authoring.md>), [behaviour](<https://devfeed.tech/tags/behaviour.md>), [build](<https://devfeed.tech/tags/build.md>), [building-with-ai](<https://devfeed.tech/tags/building-with-ai.md>), [code](<https://devfeed.tech/tags/code.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [content](<https://devfeed.tech/tags/content.md>), [control](<https://devfeed.tech/tags/control.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [gap](<https://devfeed.tech/tags/gap.md>), [process](<https://devfeed.tech/tags/process.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [repair](<https://devfeed.tech/tags/repair.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

A final attestation records which controls passed for a commit, but it does not show the failed attempts, fixes, or diagnostic path that led an agent to a green result. That gap can leave the person accountable for agent-written code unable to investigate an incident. The article proposes retaining a structured iteration record tied to the final attestation: each attempt's input and output commit or diff, checks and failures, governing model and configuration, and a link to the next attempt. Keep the actual prompts and rules durably recoverable; checksums establish configuration integrity but do not preserve their content. Record evidence tracing rather than full conversation transcripts, and treat agent explanations as investigative input, not proof of root cause. Verification coverage and review provenance can clarify what checks and review examined. Signing records can make tampering detectable, while hardened execution environments provide stronger assurance; neither replaces retaining the history. Iteration provenance makes the process auditable but does not prove the run was honest or the agent's interpretation correct.

### Source excerpt

When an agent owns the verification-and-repair loop, what record of that process survives? The attestation captures the terminal state. The iterations that preceded it -- the failures, the fixes, the diagnostic path -- vanish the moment verification succeeds.

## Top 12 Software Supply Chain Security Tools in 2026

DevFeed: [Top 12 Software Supply Chain Security Tools in 2026](<https://devfeed.tech/articles/top-12-software-supply-chain-security-tools-in-2026-103423.md>)

Original publisher: [Read original article](<https://www.aikido.dev/blog/top-software-supply-chain-security-tools>)

Author: Ruben Camerlynck

Published: 2026-08-14T14:13:00Z

Content type: comparison

Language: en

Sources: [Aikido Security's Blog](<https://devfeed.tech/sources/aikido-security-s-blog.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [software composition analysis](<https://devfeed.tech/topics/software-composition-analysis.md>), [software bill of materials](<https://devfeed.tech/topics/software-bill-of-materials.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [malware protection](<https://devfeed.tech/topics/malware-protection.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [jfrog xray](<https://devfeed.tech/topics/jfrog-xray.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [sonatype](<https://devfeed.tech/topics/sonatype.md>), [Jfrog](<https://devfeed.tech/topics/jfrog.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [aikido-intel](<https://devfeed.tech/tags/aikido-intel.md>), [aikido-security](<https://devfeed.tech/tags/aikido-security.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [risks](<https://devfeed.tech/tags/risks.md>), [security](<https://devfeed.tech/tags/security.md>), [security-tools](<https://devfeed.tech/tags/security-tools.md>), [software](<https://devfeed.tech/tags/software.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>), [software-supply-chain-security](<https://devfeed.tech/tags/software-supply-chain-security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [supply-chain-security](<https://devfeed.tech/tags/supply-chain-security.md>), [third-party](<https://devfeed.tech/tags/third-party.md>), [tools](<https://devfeed.tech/tags/tools.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

The article presents software supply chain security as protection for code, dependencies, build pipelines, containers, and release artifacts, using early checks to catch malware, known vulnerabilities, tampering, and compliance issues. Its comparison spans tools with different scopes: Dependabot and GitLab Dependency Scanning focus on dependency scanning and workflow integration; Sigstore/Cosign signs and verifies artifacts but is not a full security platform; Chainguard specializes in hardened container images; ReversingLabs emphasizes binary analysis; and Aikido, Snyk, and others combine several scanning or remediation functions. The article favors Aikido for broad coverage, install-time package blocking, developer workflow feedback, and reported noise reduction, while noting tradeoffs across alternatives such as narrow scope, integration or configuration complexity, alert volume, and enterprise focus. Its use-case lists map tools to developer, enterprise, startup, SBOM, dependency-risk, and CI/CD needs, but several promised comparison sections contain headings without detailed comparisons.

### Source excerpt

See which supply chain security tools are dominating 2026. Protect your builds from third-party risks, tampering, and dependency-based vulnerabilities. Category: DevSec Tools & Comparisons

## setup-java v5.5.0: signature verification, Kona JDK, and Maven fixes

DevFeed: [setup-java v5.5.0: signature verification, Kona JDK, and Maven fixes](<https://devfeed.tech/articles/setup-java-v5-5-0-signature-verification-kona-jdk-and-maven-fixes-71617.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-07-08-setup-java-v5-5-0-signature-verification-kona-jdk-and-maven-fixes>)

Author: Allison

Published: 2026-07-08T17:05:06Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Maven](<https://devfeed.tech/topics/maven.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>)

Tags: [actions](<https://devfeed.tech/tags/actions.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [distribution](<https://devfeed.tech/tags/distribution.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [java](<https://devfeed.tech/tags/java.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [maven](<https://devfeed.tech/tags/maven.md>), [setup](<https://devfeed.tech/tags/setup.md>), [v5](<https://devfeed.tech/tags/v5.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

actions/setup-java v5.5.0 adds optional detached GPG signature verification for Temurin and Microsoft JDK downloads; unsupported distributions fail fast, and users can provide a trusted public key. It adds Tencent Kona, plus `set-default: false` to expose a JDK to a step and Maven toolchains without changing `JAVA_HOME` or `PATH`. The action can infer a distribution from `.sdkmanrc`, quiets Maven 3.9+ and wrapper transfer logs while preserving existing `MAVEN_ARGS` (progress can be restored), and disables interactive Maven prompts. Repeated runs now deduplicate generated JDK toolchains while preserving root attributes and non-JDK entries. The excerpt also notes v5.4.0 additions: GraalVM Community, a `javac` problem matcher, and Maven Wrapper caching. For stronger pinning, it recommends the exact release tag or full commit SHA over floating `v5`.

### Source excerpt

The actions/setup-java v5.5.0 release adds cryptographic signature verification for downloaded JDKs, support for a new distribution, and several quality-of-life improvements for Maven users. Here's what changed since v5.4.0. Verify JDK...

## Subresource Integrity (SRI)

DevFeed: [Subresource Integrity (SRI)](<https://devfeed.tech/articles/subresource-integrity-sri-89182.md>)

Original publisher: [Read original article](<https://specification.website/spec/security/subresource-integrity/>)

Author: Joost de Valk

Published: 2026-07-02T00:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [cURL](<https://devfeed.tech/topics/curl.md>), [openssl](<https://devfeed.tech/topics/openssl.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [cryptographic](<https://devfeed.tech/tags/cryptographic.md>), [csp](<https://devfeed.tech/tags/csp.md>), [integrity](<https://devfeed.tech/tags/integrity.md>), [recommended](<https://devfeed.tech/tags/recommended.md>), [security](<https://devfeed.tech/tags/security.md>), [third-party](<https://devfeed.tech/tags/third-party.md>)

### AI overview

The article explains how Subresource Integrity (SRI) uses cryptographic hashes and browser checks to prevent modified external scripts and stylesheets from running. It covers generating and applying hashes, pairing SRI with Content Security Policy, using Integrity-Policy headers, and common implementation and verification steps.

### Source excerpt

SRI adds a cryptographic hash to every third-party script and stylesheet so the browser refuses to run modified files. Essential for any external JS or CSS you depend on.

## GitHub CLI 2.93.0

DevFeed: [GitHub CLI 2.93.0](<https://devfeed.tech/articles/github-cli-2-93-0-67192.md>)

Original publisher: [Read original article](<https://github.com/cli/cli/releases/tag/v2.93.0>)

Author: github-actions\[bot\]

Published: 2026-05-27T18:33:54Z

Content type: release

Language: en

Sources: [GitHub CLI](<https://devfeed.tech/sources/github-cli.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [GitHub Copilot CLI](<https://devfeed.tech/topics/github-copilot-cli.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [github](<https://devfeed.tech/tags/github.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

GitHub CLI 2.93.0 fixes a vulnerability that could expose authorization headers in requests to TUF repository mirrors made by several verification commands. The release also adds support for setting agent secrets with `gh secret` and includes other fixes and maintenance updates.

### Source excerpt

Security A security vulnerability has been identified, and fixed, that would incorrectly include authorization header in API requests to TUF repository mirrors via gh attestation, gh release verify, and gh release verify-asset commands. Users are advised to update gh to version v2.93.0 as soon as possible. For more information see: GHSA-8xvp-7hj6-mcj9 Support agents in gh secret command set The gh secret command set can now set agent secrets. For more information, see "Configuring secrets and variables for Copilot cloud agent". What's Changed ✨ Features Allow agents as application for secrets by @tenjaa in #13421 🐛 Fixes fix(pr): remove numberFieldOnly optimization that skips API validation by @williammartin in #13327 Print gh auth refresh for 401 returns by @333fred in #13068 Derive digest algorithm from ref length in release verify commands by @bdehamer in #13430 📚 Docs & Chores Add missing //go:build integration tag to verify_integration_test.go by @pdostal in #13303 Fix flaky accessible prompter Password test timeout by @pdostal in #13304 Enable extended PR screening for external PRs by @tidy-dev in #13312 Grammar fixes by @scop in #13326 Bump gh copilot telemetry sampling to 100% by @williammartin in #13362 Record accessibility feature state in telemetry by @williammartin in #13363 Poll TTY echo mode instead of sleeping in password tests by @pdostal in #13305 Switch from actions/attest-build-provenance to actions/attest by @scop in #13325 Fix skills acceptance tests by @williammartin in #13365 Bump Go toolchain to 1.26.3 by @Copilot in #13367 Trigger triage check-requirements on ready_for_review by @BagToad in #13383 fix(copilot): hint to run copilot directly when exec fails by @babakks in #13393 Update installation commands for GitHub CLI by @sassdawe in #13126 Update CODEOWNERS for skills directory ownership by @williammartin in #13416 fix(telemetry): prevent tzutil console flash on Windows by @adehad in #13353 Fix bump-go.sh to tolerate missing toolchain dir

## Copilot cloud agent signs its commits

DevFeed: [Copilot cloud agent signs its commits](<https://devfeed.tech/articles/copilot-cloud-agent-signs-its-commits-71893.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-04-03-copilot-cloud-agent-signs-its-commits>)

Author: Allison

Published: 2026-04-03T12:05:23Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [branch protection rules](<https://devfeed.tech/topics/branch-protection-rules.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [branch](<https://devfeed.tech/tags/branch.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-agent](<https://devfeed.tech/tags/cloud-agent.md>), [commit](<https://devfeed.tech/tags/commit.md>), [commits](<https://devfeed.tech/tags/commits.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [github](<https://devfeed.tech/tags/github.md>), [protection](<https://devfeed.tech/tags/protection.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [rules](<https://devfeed.tech/tags/rules.md>)

### AI overview

Copilot cloud agent now signs every commit it makes, and GitHub displays those commits as `Verified`. This lets the agent work in repositories whose branch protection rules or rulesets require signed commits, a requirement that previously blocked its use there.

### Source excerpt

Copilot cloud agent now signs every commit it makes. Signed commits appear as Verified on GitHub, giving you confidence that the commit was genuinely made by the agent and hasn't...

## Securing the Kubernetes software supply chain - Spectro Cloud

DevFeed: [Securing the Kubernetes software supply chain - Spectro Cloud](<https://devfeed.tech/articles/securing-the-kubernetes-software-supply-chain-spectro-cloud-79796.md>)

Original publisher: [Read original article](<https://www.spectrocloud.com/blog/securing-the-kubernetes-software-supply-chain>)

Author: Ant Newman

Published: 2026-03-13T14:14:00Z

Content type: tutorial

Language: en

Sources: [Spectro Cloud Feed](<https://devfeed.tech/sources/spectro-cloud-feed.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [sigstore](<https://devfeed.tech/topics/sigstore.md>), [software artifact signing](<https://devfeed.tech/topics/software-artifact-signing.md>), [slsa levels](<https://devfeed.tech/topics/slsa-levels.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Kyverno](<https://devfeed.tech/topics/kyverno.md>)

Tags: [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cosign](<https://devfeed.tech/tags/cosign.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [provenance](<https://devfeed.tech/tags/provenance.md>), [slsa](<https://devfeed.tech/tags/slsa.md>), [software-supply-chain](<https://devfeed.tech/tags/software-supply-chain.md>)

### AI overview

This tutorial explains how Sigstore and Cosign sign software artifacts, how SLSA provenance adds evidence about how they were built, and how Kubernetes teams can enforce verification across cloud and edge deployments. It also describes Spectro Cloud's signed content bundles, Artifact Studio, and admission policies.

### Source excerpt

Learn how to secure the Kubernetes software supply chain using Sigstore, Cosign, and SLSA to enforce signed artifacts, verifiable provenance, and trusted edge deployments.

[Next page](<https://devfeed.tech/topics/software-artifact-signing.md?cursor=WyIyMDI2LTAzLTEzVDE0OjE0OjAwKzAwOjAwIiwgImE3ZWE5MDM3LTE5ZjUtNGE2Ny1hOTlhLTgwOGVmZWYwMjZlYyJd>)