# attestation Published articles for attestation. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AMD Sends Out Linux Patches For Enabling SEV-TIO TDISP With PCIe 6.0 DevFeed: [AMD Sends Out Linux Patches For Enabling SEV-TIO TDISP With PCIe 6.0]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T13:02:52Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux Kernel](), [pcie](), [trusted-execution-environment](), [Confidential Computing](), [virtualization](), [Security](), [Encryption](), [MERN]() Tags: [amd](), [arm](), [attestation](), [confidential-computing](), [cpu](), [desktop-linux](), [encryption](), [intel](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-kernel](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [pcie](), [phoronix](), [phoronix-test-suite](), [processors](), [risc-v](), [security](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview AMD submitted 17 Linux kernel patches to enable SEV-TIO TDISP for PCIe 6.0 and newer. The work is intended to secure direct I/O device assignment for confidential-computing environments, including AMD Secure Encrypted Virtualization guest VMs, and includes a common TEE Security Manager developed with Intel, Arm, and RISC-V. ### Source excerpt The newest Linux kernel patches out of AMD for enhancing the upstream support with the new AMD EPYC 9006 "Venice" processors is for enabling SEV-TIO TDISP that is supported with PCI Express 6.0 and beyond... ## Securing a retail AI endpoint from abuse for virtual try on DevFeed: [Securing a retail AI endpoint from abuse for virtual try on]() Original publisher: [Read original article]() Author: Alexander Nohe Published: 2025-11-11T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Artificial Intelligence](), [Firebase](), [Authentication](), [Back end](), [Code](), [cURL]() Tags: [ai](), [app-check](), [attestation](), [authentication](), [backend](), [code](), [curl](), [devices](), [firebase](), [generation](), [genkit](), [how-to](), [image](), [model](), [rate-limiting](), [retail](), [server](), [token]() ### AI overview A tutorial on protecting a Firebase AI endpoint for a virtual try-on application. It explains using App Check, replay-protected tokens, authentication, and rate limiting to reduce unauthorized access, replayed requests, and excessive generation costs. ### Source excerpt Learn how to protect expensive AI features from abuse using Firebase App Check, Authentication, and rate limiting to ensure only legitimate users can access them. ## Building Hardware-Enforced Trust into Matter Devices with ESP-TEE DevFeed: [Building Hardware-Enforced Trust into Matter Devices with ESP-TEE]() Original publisher: [Read original article]() Author: John Lee Published: 2025-09-12T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [Matter](), [trusted-execution-environment](), [ESP32-C6](), [RISC-V](), [Internet of things](), [Security]() Tags: [attestation](), [blog](), [esp-tee](), [esp32-c6](), [iot](), [matter](), [risc-v](), [security](), [verification]() ### AI overview This article explains how Espressif's ESP-TEE framework integrates with Matter on ESP32-C6 RISC-V SoCs. It describes hardware-isolated protection for device credentials, cryptographic operations, secure storage, OTA updates, attestation, and Matter DAC and NOC keys. ### Source excerpt As security expectations rise globally - driven by region-specific cybersecurity regulations - safeguarding device credentials has become critical for IoT manufacturers. This article explains how the ESP-TEE framework integrates with Matter and demonstrates building secure products using the Espressif RISC-V SoCs, showcasing hardware-enforced security that can resist scalable remote software attacks. ## Laravel Cloud Achieves SOC 2 Type 2 Certification, Nightwatch and Forge Next DevFeed: [Laravel Cloud Achieves SOC 2 Type 2 Certification, Nightwatch and Forge Next]() Original publisher: [Read original article]() Author: André Valentin Published: 2025-09-05T09:54:10Z Content type: news Language: en Sources: [Laravel Blog]() Topics: [SOC](), [Cloud](), [Security](), [Availability](), [Laravel]() Tags: [2025](), [attestation](), [audits](), [availability](), [cloud](), [compliance](), [data-protection](), [enterprise](), [monitoring](), [reports](), [security](), [soc](), [soc-2](), [standards](), [trust](), [verification]() ### AI overview Laravel Cloud achieved SOC 2 Type 2 certification for Security, Confidentiality, and Availability after completing its audit on July 31, 2025. The article explains the significance of SOC 2, contrasts Type 1 and Type 2 reports, and outlines planned SOC 2 audits for Nightwatch and Forge. ### Source excerpt Laravel Cloud achieves SOC 2 Type 2 certification for Security, Confidentiality, and Availability. Read how Laravel's compliance roadmap includes Nightwatch and Forge SOC 2 audits. ## Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration DevFeed: [Workload Identity Meets Supply Chain Security: Teleport's Sigstore Integration]() Original publisher: [Read original article]() Author: daniel.upton@goteleport.com (Dan Upton) Published: 2025-06-05T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [sigstore](), [supply-chain-security](), [Security](), [OpenID connect (OIDC)](), [GitHub Actions]() Tags: [attestation](), [github-actions](), [oidc](), [provenance](), [security](), [signing](), [sigstore](), [supply-chain](), [supply-chain-security]() ### AI overview This article explains how Teleport integrates with Sigstore to strengthen software supply chain security for workload identity. It describes signing software artifacts and attestations, and explains Sigstore's keyless approach using single-use certificates tied to OIDC identities. ### Source excerpt Learn how to use Teleport's integration with Sigstore to build supply chain security into your workload identity. ## Trusted Computing: The Role of Infrastructure IAM DevFeed: [Trusted Computing: The Role of Infrastructure IAM]() Original publisher: [Read original article]() Author: info@thecyberhut.com (Simon Moffatt) Published: 2025-02-26T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [trust](), [IAM](), [Security](), [Zero Trust](), [Server]() Tags: [attestation](), [authentication](), [cryptographic](), [frameworks](), [iam](), [identity](), [identity-management](), [infrastructure](), [kubernetes](), [network](), [security](), [tools](), [trust](), [vulnerability](), [zero-trust]() ### AI overview This article examines how Infrastructure IAM and trusted computing extend trust beyond data and applications to the infrastructure that delivers services. It discusses zero trust, software attestation, cryptographic challenge-response authentication, and trusted platform modules, while noting the complexity and security risks of modern infrastructure. ### Source excerpt Discover how Infrastructure IAM enhances trust in modern computing with zero trust principles and identity management for people, machines, and workloads. ## Announcing ESP-TEE Framework for ESP32-C6 DevFeed: [Announcing ESP-TEE Framework for ESP32-C6]() Original publisher: [Read original article]() Author: John Lee Published: 2025-02-18T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [trusted-execution-environment](), [Security](), [Internet of things](), [ESP-IDF](), [RISC-V](), [Embedded Software Dev]() Tags: [architecture](), [attestation](), [blog](), [esp-idf](), [esp-tee](), [esp32](), [esp32-c6](), [espressif](), [firmware](), [freertos](), [iot](), [ota](), [risc-v](), [security](), [standards](), [trust]() ### AI overview Espressif announces the availability of the ESP-TEE framework for ESP32-C6. The framework provides a hardware-enforced trusted execution environment that isolates sensitive computations and data from the main application, with features including secure storage, secure OTA updates, and attestation. ### Source excerpt We are thrilled to announce the availability of the ESP-TEE (Trusted Execution Environment) framework for the ESP32-C6! Designed to enhance security on Espressif's SoCs, ESP-TEE enables a protected execution environment to safeguard sensitive information and operations. The Importance of the ESP-TEE# Security is paramount in the IoT landscape, where billions of devices exchange sensitive information daily. ## Matter: Improvements to Espressif DAC Provisioning Service DevFeed: [Matter: Improvements to Espressif DAC Provisioning Service]() Original publisher: [Read original article]() Author: John Lee Published: 2024-10-01T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [Matter](), [Espressif](), [Provisioning](), [Cloud]() Tags: [attestation](), [blog](), [certificates](), [cloud](), [devices](), [esp32](), [espressif](), [firmware](), [iot](), [matter](), [private-key](), [provisioning](), [security](), [signing](), [trust](), [update]() ### AI overview Espressif describes updates to its Matter DAC provisioning service, including support for customer-factory manufacturing and secure delivery of Device Attestation Certificates for in-field devices upgrading to Matter. ### Source excerpt Espressif's Secure Manufacturing Service, which was launched last year, has assisted many customers in simplifying their manufacturing. Since a year from launch, we worked with hundreds of customers and served millions of modules that were manufactured with this service. ## Apple already shipped attestation on the web, and we barely noticed DevFeed: [Apple already shipped attestation on the web, and we barely noticed]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2023-07-25T14:00:00Z Content type: opinion Language: en Sources: [HTTP Toolkit]() Topics: [Web](), [browser](), [HTTP](), [iOS](), [macOS](), [Cloudflare]() Tags: [apple](), [attestation](), [browser](), [browsers](), [chromium](), [cloudflare](), [http](), [ios](), [macos](), [public-key](), [server](), [web]() ### AI overview This opinion article examines Apple's Private Access Tokens, an attestation system integrated into macOS 13, iOS 16, and Safari. It explains how browsers, operating systems, attesters, and token issuers use HTTP challenges and signed tokens to verify that requests come from legitimate devices without disclosing the user's identity, while comparing the system with the proposed Web Environment Integrity model. ### Source excerpt There's been a lot of concern recently about the Web Environment Integrity proposal, developed by a selection of authors from Google, and apparently being prototyped in Chromium. There's good reason for anger here (though I'm not sure yelling at people on GitHub is necessarily the best outlet). This proposal amounts to attestation on the web, limiting access to features or entire sites based on whether the client is approved by a trusted issuer. In practice, that will mean Apple, Microsoft & Google. Of course, Google isn't the first to think of this, but in fact they're not even the first to ship it. Apple already developed & deployed an extremely similar system last year, now integrated into MacOS 13, iOS 16 & Safari, called "Private Access Tokens": Private Access Tokens are powerful tools that prove when HTTP requests are coming from legitimate devices without disclosing someone's identity. The focus here is primarily on removing captchas, and as such it's been integrated into Cloudflare (discussed here) and Fastly (here) as a mechanism for recognizing 'real' clients without needing other captcha mechanisms. Fundamentally though, it's exactly the same concept: a way that web servers can demand your device prove it is a sufficiently 'legitimate' device before browsing the web. How do Private Access Tokens work? The mechanism is a fairly simple exchange over HTTP, handled by built-in browser APIs, which in turn integrate with operating system components to confirm that the browser & OS are 'legitimate' (the exact definition of that is left to the attester - i.e. Apple). The flow looks like this: A browser makes an HTTP request from a web server. The web server refuses the request, and returns an HTTP 401 response with a PrivateToken challenge: HTTP/1.1 401 Unauthorized WWW-Authenticate: PrivateToken challenge=, token-key= (Newlines added for readability) The browser recognizes this, and sends parts of the challenge, in addit ## Reproducing Chainguard's reproducible image builds DevFeed: [Reproducing Chainguard's reproducible image builds]() Original publisher: [Read original article]() Published: 2023-07-05T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [supply-chain-security](), [configuration](), [Tooling]() Tags: [apko](), [attestation](), [build](), [chainguard](), [chainguard-images](), [configuration](), [cosign](), [hardened-images](), [locks](), [reproducibility](), [reproducible-builds](), [secure-image](), [security](), [software-supply-chain](), [supply-chain-security](), [wolfi]() ### AI overview A tutorial explaining how to reproduce a Chainguard Images build using cosign and apko. It describes locking image configurations and notes caveats involving tooling changes and withdrawn packages. ### Source excerpt Learn how to reproduce a Chainguard Images build using cosign and apko. ## How to explain the CISA software attestation requirements to your board DevFeed: [How to explain the CISA software attestation requirements to your board]() Original publisher: [Read original article]() Published: 2023-05-05T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [cisa](), [cybersecurity and infrastructure security agency](), [software bill of materials](), [Security]() Tags: [attestation](), [chainguard](), [cisa](), [container-security](), [government](), [national-cybersecurity-strategy](), [nist](), [policy](), [sbom](), [sboms](), [secure-container-image](), [secure-software](), [self-attestation](), [signing-artifacts](), [sigstore](), [software-artifact-signing](), [software-bill-of-materials](), [software-supply-chain-security](), [ssdf]() ### AI overview This article explains how software companies can brief their boards on CISA software attestation requirements and the broader federal software supply chain security policy landscape. It discusses Executive Order 14028, SBOMs, secure software development, CISA's Secure Software Development Attestation Form, and the requirements in OMB Memorandum M-22-18, including alignment with NIST guidance. ### Source excerpt CISA's draft self-attestation form clarifies the minimum requirements that software developers must meet to comply with OMB Memorandum M-22-18. ## The role of attestations in a secure software supply chain DevFeed: [The role of attestations in a secure software supply chain]() Original publisher: [Read original article]() Published: 2023-04-04T00:00:00Z Content type: tutorial Language: en Sources: [Chainguard: Unchained]() Topics: [supply-chain-security](), [chainguard enforce](), [Docker Verified Publisher]() Tags: [attestation](), [chainguard](), [chainguard-enforce](), [digital-signatures](), [integrity](), [policy](), [secure-software](), [secure-software-supply-chain](), [security-policies](), [slsa](), [software-attestations](), [supply-chain]() ### AI overview This article explains how attestations support software supply-chain policy enforcement. It describes attestations as signed claims from identified speakers about code or build results, allowing deployment systems to verify policy requirements without repeating expensive or impractical checks. ### Source excerpt Chainguard Enforce enables policy enforcement using attestations. Learn how to use these principles to create and enforce secure supply chain policies. ## Matter Security Model DevFeed: [Matter Security Model]() Original publisher: [Read original article]() Author: John Lee Published: 2022-02-24T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [Matter](), [Security](), [Cryptography](), [Protocol (disambiguation)]() Tags: [attestation](), [blog](), [certificates](), [controllers](), [cryptographic](), [cryptography](), [devices](), [esp32](), [infrastructure](), [integrity](), [iot](), [ledger](), [manufacturing](), [matter](), [privacy](), [process](), [protocol](), [public-key](), [security](), [storage](), [trust](), [verify]() ### AI overview An overview of Matter's security model, explaining how PKI, certificates, cryptography, and session establishment support trusted devices, trusted controllers, private communication, and data integrity. It also describes Matter's Device Attestation Certificate chain and the role of the Distributed Compliance Ledger. ### Source excerpt Matter is a protocol designed with security and privacy in mind. Cryptography is widely adopted in Matter to ensure: - Trusted devices - Trusted controllers - Private communication In this post we will go through the Matter security model and investigate how these targets are accomplished in Matter. Introduction to Public Key Infrastructure# The Matter security model is based on Public Key Infrastructure(PKI), a cryptographic mechanism widely adopted in the Internet. ## New features in App Check beta DevFeed: [New features in App Check beta]() Original publisher: [Read original article]() Author: Tyler Crowe Published: 2021-08-03T00:00:00Z Content type: news Language: en Sources: [Firebase Blog]() Topics: [Firebase](), [Security](), [iOS](), [API](), [Cloud Functions](), [Realtime Database](), [Cloud Run](), [Node.js]() Tags: [admin-sdk](), [api-security](), [app-attestation](), [app-check](), [apple](), [attestation](), [cloud](), [cloud-functions](), [cloud-run](), [firebase](), [launch](), [news](), [node-js](), [realtime-database](), [updates]() ### AI overview Firebase announces three additions to the App Check beta: iOS App Attest support, configurable token time-to-live values, and protection for non-Firebase backends. The article also explains how these features affect security, responsiveness, quota usage, and supported providers. ### Source excerpt News, tutorials, and updates from the Firebase team. ## How Shopify Governs Containers at Scale with Grafeas and Kritis DevFeed: [How Shopify Governs Containers at Scale with Grafeas and Kritis]() Original publisher: [Read original article]() Author: Jonathan jonathan pulsifer com Published: 2017-10-12T15:02:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Containers](), [Shopify](), [supply-chain-security](), [Google](), [Kubernetes](), [ci](), [Open Source](), [Security]() Tags: [attestation](), [audits](), [ci](), [container-registry](), [containers](), [deployment](), [google](), [identity](), [images](), [kubernetes](), [open-source](), [operations](), [packages](), [pipelines](), [policy](), [production](), [registry](), [security](), [shopify](), [software-supply-chain]() ### AI overview Shopify describes using Google's open source Grafeas to centralize metadata about container builds, images, packages, origins, deployments, and vulnerabilities. It also uses Kritis with Kubernetes to enforce real-time deployment policies based on signed attestations generated during CI. ### Source excerpt Today, Google and its contributors launched Grafeas, an open source initiative to define a uniform way for auditing and governing the modern software supply chain. At Shopify, we're excited to be part of this announcement. Grafeas, or "scribe" in Greek, enables us to store critical software component metadata during our build and integration pipelines.