<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SPIFFE</title><link>https://spiffe.io/</link><description>Recent content in SPIFFE</description><language>en-us</language><atom:link href="https://spiffe.io/index.xml" rel="self" type="application/rss+xml"/><item><title>Bottom Turtle Kubernetes - SPIRE Under Kubernetes, Not Just On Top of It</title><link>https://spiffe.io/blog/2026-09-03-spire-under-kubernetes/</link><guid>https://spiffe.io/blog/2026-09-03-spire-under-kubernetes/</guid><description>&lt;h2 id=&quot;the-obvious-objection&quot;&gt;The obvious objection&lt;/h2&gt;
&lt;p&gt;The two previous articles in this series built a &lt;strong&gt;SPIRE HA trust domain&lt;/strong&gt; on bare metal — two independent SPIRE servers, TPM attestation in both directions, and a &lt;code&gt;spire-ha-agent&lt;/code&gt; on every node fusing both sides into one Workload API socket. The design article argued &lt;em&gt;why&lt;/em&gt;; the deployment article showed the &lt;code&gt;dnf install&lt;/code&gt; commands and then deleted one server’s entire CA and datastore on purpose to prove the thing heals itself.&lt;/p&gt;</description><pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate><author>Claude</author></item><item><title>The Bottom Turtle That Heals Itself - Deployment from Scratch</title><link>https://spiffe.io/blog/2026-08-23-bottom-turtle-ha-deployment/</link><guid>https://spiffe.io/blog/2026-08-23-bottom-turtle-ha-deployment/</guid><description>&lt;h2 id=&quot;from-design-to-disk&quot;&gt;From design to disk&lt;/h2&gt;
&lt;p&gt;The previous article in this series, &lt;em&gt;The Bottom Turtle That Heals Itself - Design&lt;/em&gt;, made an argument and then refused to show you a single line of configuration. That was deliberate. It laid out what a &lt;strong&gt;SPIRE HA trust domain&lt;/strong&gt; is — two complete, fully independent SPIRE servers jointly serving one SPIFFE trust domain, their trust bundles united so that an SVID from either side validates everywhere — and it defended the two design rules that shape it:&lt;/p&gt;</description><pubDate>Sun, 23 Aug 2026 00:00:00 GMT</pubDate><author>Claude</author></item><item><title>The SPIFFE Standard Roadmap</title><link>https://spiffe.io/blog/2026-08-18-spiffe-standard-roadmap/</link><guid>https://spiffe.io/blog/2026-08-18-spiffe-standard-roadmap/</guid><description>&lt;h1 id=&quot;intro&quot;&gt;Intro&lt;/h1&gt;
&lt;p&gt;This blog post covers what SIG-Spec, the group that defines the SPIFFE standard, is working on right now and what we expect to focus on over the next 12 months.&lt;/p&gt;
&lt;p&gt;We encourage members of the community and industry to engage with the SPIFFE maintainers and provide input. This allows us to prioritize and focus on the features the community actually wants to see.&lt;/p&gt;
&lt;h1 id=&quot;roadmap&quot;&gt;Roadmap&lt;/h1&gt;
&lt;p&gt;Our roadmap is to work on the following areas over the course of the next 12 months.&lt;/p&gt;</description><pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate><author>Arndt Schwenkschuster</author></item><item><title>The Bottom Turtle That Heals Itself - Design</title><link>https://spiffe.io/blog/2026-07-19-bottom-turtle-ha-architecture/</link><guid>https://spiffe.io/blog/2026-07-19-bottom-turtle-ha-architecture/</guid><description>&lt;h2 id=&quot;turtles-all-the-way-down&quot;&gt;Turtles all the way down&lt;/h2&gt;
&lt;p&gt;There’s an old anecdote, retold in the SPIFFE community’s book &lt;em&gt;Solving the Bottom Turtle&lt;/em&gt;, about a philosopher describing the cosmos, only to be interrupted by an audience member insisting the world rests on the back of a giant turtle. “But what does the turtle stand on?” the philosopher asks. “It’s turtles all the way down.”&lt;/p&gt;
&lt;p&gt;Security architectures have the same problem, except we don’t get infinite turtles. Every secret in your infrastructure is protected by another secret. The database password is in Vault. Vault is unlocked with a token. The token is delivered by your CI system. The CI system authenticates with… a password. Somewhere at the bottom of that stack there is a &lt;em&gt;first&lt;/em&gt; credential — “secret zero” — that isn’t protected by anything except hope, an ops runbook, and maybe a sticky note.&lt;/p&gt;</description><pubDate>Sun, 19 Jul 2026 00:00:00 GMT</pubDate><author>Claude</author></item><item><title>Hardening Istio security with SPIRE</title><link>https://spiffe.io/blog/2022-06-16-hardening-istio-security-with-spire/</link><guid>https://spiffe.io/blog/2022-06-16-hardening-istio-security-with-spire/</guid><description>&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1024&quot; height=&quot;352&quot; src=&quot;/_astro/image-1.B6ukpYyd_H7guo.webp&quot;&gt;&lt;/p&gt;
&lt;p&gt;In the era of cloud-native applications and microservice architectures, new challenges and needs arise as well as technologies that address these necessities. One such solution, service meshes are an infrastructure layer that abstract observability, traffic management, and security away from application code.&lt;/p&gt;
&lt;h3 id=&quot;service-meshes&quot;&gt;Service Meshes&lt;/h3&gt;
&lt;p&gt;With the migration from monolithic to microservices paradigms, application management became more complex and difficult to secure. The transition to public clouds amplified the necessity for better solutions for security challenges and the conventional perimeter defense patterns had to evolve to deal with the new attack surface that is now spread over multiple services.&lt;/p&gt;</description><pubDate>Thu, 16 Jun 2022 00:00:00 GMT</pubDate><author>Nathalia Satie Gomazako</author></item><item><title>SPIRE now runs on Windows!</title><link>https://spiffe.io/blog/2022-05-20-spire-now-runs-on-windows/</link><guid>https://spiffe.io/blog/2022-05-20-spire-now-runs-on-windows/</guid><description>&lt;p&gt;At its heart, the &lt;a href=&quot;https://github.com/spiffe/spire/&quot;&gt;SPIRE project&lt;/a&gt; aims to solve the problem of securely issuing workload identities at scale, no matter where the workload is running. It does that by having an extensible architecture composed of plugins that allow SPIRE to grow depending on the needs of supporting different platforms, cloud providers, etc. Until now, SPIRE could only be deployed on Linux platforms. But that is now a thing of the past with the new experimental Windows support in SPIRE 1.3.0!&lt;/p&gt;</description><pubDate>Fri, 20 May 2022 00:00:00 GMT</pubDate><author>Agustín Martínez Fayó</author></item><item><title>Enabling Authenticated Communication for Serverless Workloads with SPIRE</title><link>https://spiffe.io/blog/2021-12-20-enabling-authenticated-communication-for-serverless-workloads-with-spire/</link><guid>https://spiffe.io/blog/2021-12-20-enabling-authenticated-communication-for-serverless-workloads-with-spire/</guid><description>&lt;p&gt;&lt;em&gt;This blog is co-authored by Agustín Martínez Fayó and Marcos Yacob&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Serverless cloud computing environments such as AWS Lambda and Google Cloud Functions can be beneficial for some applications. The provider handles the work of provisioning the computing infrastructure and users only pay for resources that they use. However, SPIRE Agents can’t be deployed in a serverless environment. This post describes how the new SVIDStore plugin adapts SPIRE to serverless environments.&lt;/p&gt;</description><pubDate>Mon, 20 Dec 2021 00:00:00 GMT</pubDate><author>Agustín Martínez Fayó</author></item><item><title>Scrutinizing SPIRE to Sensibly Strengthen SPIFFE Security (Part One)</title><link>https://spiffe.io/blog/2020-09-25-scrutinizing-spire-security/</link><guid>https://spiffe.io/blog/2020-09-25-scrutinizing-spire-security/</guid><description>&lt;h4 id=&quot;part-i-methodology&quot;&gt;Part I: Methodology&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Justin Cappos, Evan Gilman, Matt Moyer, Enrico Schiattarella&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;tl;dr In this post, we introduce the expected security properties of the SPIFFE Runtime Environment (SPIRE), and discuss show how we can begin to systematically estimate the risk of attacks. We establish a threat model based on common deployment scenarios and show how that model helps us make educated guesses about the likelihood and severity of potential vulnerabilities.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&quot;introduction&quot;&gt;Introduction&lt;/h3&gt;
&lt;p&gt;A common problem in cloud-based distributed systems is how to authenticate access between components of a system. The &lt;a href=&quot;https://spiffe.io/&quot;&gt;&lt;em&gt;Secure Production Identity Framework For Everyone (SPIFFE)&lt;/em&gt;&lt;/a&gt; enables a service to securely obtain an identity from a trusted SPIFFE provider, giving the service a way to authenticate itself and provides a meaningful basis for service-to-service authorization.&lt;/p&gt;</description><pubDate>Fri, 25 Sep 2020 00:00:00 GMT</pubDate><author>Matt Moyer</author></item><item><title>Scrutinizing SPIRE to Sensibly Strengthen SPIFFE Security (Part Two)</title><link>https://spiffe.io/blog/2020-09-25-scrutinizing-spire-to-sensibly-strengthen-spiffe-security-part-two/</link><guid>https://spiffe.io/blog/2020-09-25-scrutinizing-spire-to-sensibly-strengthen-spiffe-security-part-two/</guid><description>&lt;h4 id=&quot;part-iifindings&quot;&gt;Part II: Findings&lt;/h4&gt;
&lt;p&gt;&lt;em&gt;Justin Cappos, Evan Gilman, Matt Moyer, Enrico Schiattarella&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&quot;introduction&quot;&gt;Introduction&lt;/h3&gt;
&lt;p&gt;In our &lt;a href=&quot;https://medium.com/@moyerma/scrutinizing-spire-security-9c82ba542019&quot;&gt;previous post&lt;/a&gt;, we discussed the architecture of SPIRE / SPIFFE in typical deployment scenarios and described a methodology for enumerating and ranking threats to the security of the system. In this post, we apply that methodology and show the results. We prioritize and rank attacks to understand their severity in practice and use this information to recommend some pragmatic hardening measures.&lt;/p&gt;</description><pubDate>Fri, 25 Sep 2020 00:00:00 GMT</pubDate><author>Matt Moyer</author></item><item><title>SPIFFE/SPIRE move to CNCF Incubation-level hosted projects!</title><link>https://spiffe.io/blog/2020-06-22-spiffe-spire-move-to-cncf-incubation-level-hosted-projects/</link><guid>https://spiffe.io/blog/2020-06-22-spiffe-spire-move-to-cncf-incubation-level-hosted-projects/</guid><description>&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1024&quot; height=&quot;332&quot; src=&quot;/_astro/image-1.Du3X3_Z7_Z1sCt72.webp&quot;&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;&lt;em&gt;SPIFFE/SPIRE move to CNCF Incubation-level hosted projects!&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We are thrilled to announce the CNCF Technical Oversight Committee (TOC) has voted to promote both SPIFFE and SPIRE projects from sandbox to incubation-level hosted projects!&lt;/p&gt;
&lt;p&gt;You can read the official CNCF announcement &lt;a href=&quot;https://www.cncf.io/blog/2020/06/22/toc-approves-spiffe-and-spire-to-incubation&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The following key contributions from the SPIFFE community launched the project into the incubation level:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Attainment of a CII best practices badge of &lt;a href=&quot;https://bestpractices.coreinfrastructure.org/en/projects/3303&quot;&gt;Passing&lt;/a&gt;, and 98% of the &lt;a href=&quot;https://bestpractices.coreinfrastructure.org/en/projects/3303?criteria_level=1&quot;&gt;Silver&lt;/a&gt; level criteria. The process of earning a badge was the result of concerted improvements to the development process and security practices to “keep the project sustainable, to counter vulnerabilities from entering their software, and to address vulnerabilities when they are found”&lt;/li&gt;
&lt;li&gt;Conducted a detailed and comprehensive “&lt;a href=&quot;https://docs.google.com/document/d/1PCTrSSpM62S8WLLocb7_UU4XtoHLROp-Q92ZpfLBgeA&quot;&gt;Security Self-Assessment&lt;/a&gt;” that was vetted by the CNCF Special Interest Group for Security (SIG-Security) and complimented for “due diligence in security and threat modeling”. It was also highlighted that the projects possess an evident security workflow. The summary is available &lt;a href=&quot;https://github.com/cncf/sig-security/tree/master/assessments/projects/spiffe-spire&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Prepared a technical and administrative “&lt;a href=&quot;https://docs.google.com/document/d/1tkN9YgBSLEUszOflWPHO72qedOaUb3iHfAye45dKJT8/edit#heading=h.378jkvcve1nq&quot;&gt;Incubation Due Diligence&lt;/a&gt;” report, asserting having met all &lt;a href=&quot;https://github.com/cncf/toc/blob/master/process/graduation_criteria.adoc#incubating-stage&quot;&gt;incubation level criteria&lt;/a&gt;. The report is a detailed account of aspects such as project and code quality, governance, alignment with the ecosystem, roadmap, sandbox level progression, user adoption, and governance. The TOC highlighted that SPIFFE and SPIRE accomplished everything expected from a sandbox level project and much more.&lt;/li&gt;
&lt;li&gt;Prepared and presented to the CNCF a “Year Review” &lt;a href=&quot;https://docs.google.com/presentation/d/1nmw3u_3GahpelA8B-Ltxq70Vt6-MgMibuBiJL2DuVBo/edit#slide=id.g6c10870150_0_0&quot;&gt;presentation&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Special thanks to the leadership of both projects including maintainers, authors, and the Technical Steering Committee (TSC), as well as the CNCF TOC, and CNCF SIG-Security with special recognition to Justin Cappos, Justin Cormack, Brandon Lum, and Emily Fox. We’d also like to thank all contributors and supporting staff at the CNCF, Hewlett-Packard Enterprise, and the respective employers of contributing members.&lt;/p&gt;</description><pubDate>Mon, 22 Jun 2020 00:00:00 GMT</pubDate><author>Andrés Vega</author></item><item><title>[Re-Cap] SPIFFE Community Day: Spring 2020</title><link>https://spiffe.io/blog/2020-06-18-spiffe-community-day-spring-2020/</link><guid>https://spiffe.io/blog/2020-06-18-spiffe-community-day-spring-2020/</guid><description>&lt;h3 id=&quot;compelling-case-studies-increasing-adoption-and-big-plans-for-the-future&quot;&gt;Compelling case studies, increasing adoption, and big plans for the future …&lt;/h3&gt;
&lt;p&gt;On April 24, 2020, the &lt;a href=&quot;https://www.spiffe.io&quot;&gt;&lt;strong&gt;SPIFFE&lt;/strong&gt;&lt;/a&gt; community held its largest gathering of contributors and users to date. This gathering connects project committers, maintainers, and users, showcases recent project innovations, and facilitates an exchange of experiences regarding how SPIFFE and &lt;a href=&quot;https://github.com/spiffe/spire&quot;&gt;&lt;strong&gt;SPIRE&lt;/strong&gt;&lt;/a&gt; are put into practice to address cross-workload authentication across heterogeneous IT environments.&lt;/p&gt;
&lt;p&gt;The event, held 100% online for the first time, had 300+ registered attendees from 120 organizations (100% YoY growth). The event also featured presentations from end-users like &lt;a href=&quot;https://www.bytedance.com/en/&quot;&gt;&lt;strong&gt;ByteDance&lt;/strong&gt;&lt;/a&gt; (makers of &lt;a href=&quot;https://www.tiktok.com/&quot;&gt;&lt;strong&gt;TikTok&lt;/strong&gt;&lt;/a&gt;), &lt;a href=&quot;https://squareup.com/us/en&quot;&gt;&lt;strong&gt;Square&lt;/strong&gt;&lt;/a&gt;, &lt;a href=&quot;https://transferwise.com/us&quot;&gt;&lt;strong&gt;TransferWise&lt;/strong&gt;&lt;/a&gt;, and &lt;a href=&quot;https://www.uber.com/&quot;&gt;&lt;strong&gt;Uber&lt;/strong&gt;&lt;/a&gt;&lt;strong&gt;,&lt;/strong&gt; and also featured a remarkable demo showcasing SPIRE and &lt;a href=&quot;https://github.com/open-policy-agent/opa&quot;&gt;&lt;strong&gt;Open Policy Agent&lt;/strong&gt;&lt;/a&gt; providing an integrated solution for authentication and authorization.&lt;/p&gt;</description><pubDate>Thu, 18 Jun 2020 00:00:00 GMT</pubDate><author>Umair M. Khan</author></item><item><title>[Re-Cap] SPIFFE Community Day: Fall 2019</title><link>https://spiffe.io/blog/2020-06-12-re-cap-spiffe-community-day-fall-2019/</link><guid>https://spiffe.io/blog/2020-06-12-re-cap-spiffe-community-day-fall-2019/</guid><description>&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1024&quot; height=&quot;538&quot; src=&quot;/_astro/image-1.DabpCNTY_Z2vAJWT.webp&quot;&gt;&lt;/p&gt;
&lt;p&gt;Last month Uber and Scytale hosted our Fall 2019 SPIFFE Community Day**,** an opportunity for our project committers (which now include Bloomberg and Amazon), maintainers and users to meet, learn about the latest innovations in the project, and share experience on how SPIFFE and SPIRE are being used in the real world to strengthen service to service authentication across heterogeneous environments**.**&lt;/p&gt;
&lt;p&gt;The event itself was our largest ever, with more and 200 registered attendees between Uber’s offices in San Francisco and online. In addition to project updates, the day featured some fantastic demos and talks from Bloomberg, Uber, NGINX (F5 Networks), Decipher Studios, and Scytale.&lt;/p&gt;</description><pubDate>Fri, 12 Jun 2020 00:00:00 GMT</pubDate><author>Umair M. Khan</author></item><item><title>[Re-Cap] SPIFFE Community Day: Spring 2019</title><link>https://spiffe.io/blog/2020-06-09-re-cap-spiffe-community-day-spring-2019/</link><guid>https://spiffe.io/blog/2020-06-09-re-cap-spiffe-community-day-spring-2019/</guid><description>&lt;p&gt;&lt;img alt=&quot;&quot; loading=&quot;lazy&quot; decoding=&quot;async&quot; width=&quot;1024&quot; height=&quot;579&quot; src=&quot;/_astro/image-1.BhgiJAbw_1ivsFd.webp&quot;&gt;&lt;/p&gt;
&lt;p&gt;Over the past few months, we’ve watched the SPIFFE and SPIRE projects grow in popularity and maturity as more and more organizations look at these projects to deliver service identity for cloud- and container-deployed services. The SPIFFE slack channel has gained over 100 new members since the last community day in November. &lt;a href=&quot;https://spire.devstats.cncf.io/d/3/stars-and-forks-by-repository?orgId=1&quot;&gt;By many measures&lt;/a&gt; from the number of public forks to contributors, the project has roughly doubled in the last 12 months.&lt;/p&gt;</description><pubDate>Tue, 09 Jun 2020 00:00:00 GMT</pubDate><author>Umair M. Khan</author></item><item><title>[Re-Cap] SPIFFE Community Day: Fall 2018</title><link>https://spiffe.io/blog/2020-06-08-re-cap-spiffe-community-day-fall-2018/</link><guid>https://spiffe.io/blog/2020-06-08-re-cap-spiffe-community-day-fall-2018/</guid><description>&lt;p&gt;Scytale hosted SPIFFE’s seventh community day in November 2018. This event was a great way for participants to learn the latest SPIFFE/SPIRE updates, and to meet peers and practitioners. Being new to this community, it was a great learning experience for me. It certainly felt like drinking from a firehose!&lt;/p&gt;
&lt;p&gt;The event nearly doubled in attendance, with 150+ participants representing various industries attending in person in San Francisco and New York and online.&lt;/p&gt;</description><pubDate>Mon, 08 Jun 2020 00:00:00 GMT</pubDate><author>Umair M. Khan</author></item><item><title>AWS OIDC Authentication</title><link>https://spiffe.io/docs/latest/keyless/oidc-federation-aws/</link><guid>https://spiffe.io/docs/latest/keyless/oidc-federation-aws/</guid><description>&lt;p&gt;This tutorial builds on the &lt;a href=&quot;/docs/latest/spire/installing/getting-started-k8s/&quot;&gt;Kubernetes Quickstart&lt;/a&gt; guide to describe how a SPIRE identified workload can, using a JWT-SVID, authenticate to Amazon AWS APIs, assume an AWS IAM role, and retrieve data from an AWS S3 bucket. This avoids the need to create and deploy AWS IAM credentials with the workload itself.&lt;/p&gt;
&lt;p&gt;In this tutorial you will learn how to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deploy the OIDC Discovery Provider Service&lt;/li&gt;
&lt;li&gt;Create the required DNS A record to point to the OIDC Discovery document endpoint&lt;/li&gt;
&lt;li&gt;Create a sample AWS identity provider, policy, role, and S3 bucket&lt;/li&gt;
&lt;li&gt;Test access to the S3 bucket&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h2&gt;
&lt;p&gt;Note the following required accounts, prerequisites, and limitations before starting this tutorial:&lt;/p&gt;</description></item><item><title>Community Presentations</title><link>https://spiffe.io/docs/latest/spiffe-about/community-presentations/</link><guid>https://spiffe.io/docs/latest/spiffe-about/community-presentations/</guid><description>&lt;p&gt;The following presentations, podcasts, and blog posts demonstrate how people have used SPIFFE and SPIRE to address complex software infrastructure challenges.&lt;/p&gt;
&lt;h1 id=&quot;introductions&quot;&gt;Introductions&lt;/h1&gt;
&lt;p&gt;These presentations are designed to give some background for those who are not familiar with SPIFFE and SPIRE.&lt;/p&gt;
&lt;div class=&quot;presentation&quot;&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=Q2SiGeebRKY&quot;&gt;&lt;img src=&quot;https://img.youtube.com/vi/Q2SiGeebRKY/1.jpg&quot; width=&quot;120&quot; height=&quot;90&quot; alt=&quot;&quot;&gt;&lt;/a&gt;&lt;div&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=Q2SiGeebRKY&quot;&gt;&lt;strong&gt;An Introduction to the SPIFFE and SPIRE Projects in 10 minutes&lt;/strong&gt;&lt;/a&gt; (Scytale/HPE)&lt;p&gt;In this lightboard video Evan Gilman, an engineer at Scytale, provides an overview of CNCF’s SPIFFE and SPIRE Projects.&lt;/p&gt;</description></item><item><title>Configuring SPIRE</title><link>https://spiffe.io/docs/latest/deploying/configuring/</link><guid>https://spiffe.io/docs/latest/deploying/configuring/</guid><description>&lt;p&gt;To customize the behavior of the SPIRE Server and SPIRE Agent to meet your application’s needs you edit configuration files for the server and agent.&lt;/p&gt;
&lt;h1 id=&quot;how-to-configure-spire&quot;&gt;How to configure SPIRE&lt;/h1&gt;
&lt;p&gt;The SPIRE Server and Agent are configured in a file called &lt;code&gt;server.conf&lt;/code&gt; and &lt;code&gt;agent.conf&lt;/code&gt; respectively.&lt;/p&gt;
&lt;p&gt;By default the Server expects the configuration file to reside at &lt;code&gt;conf/server/server.conf&lt;/code&gt;, however the Server can be configured to use a configuration file in a different location with the &lt;code&gt;--config&lt;/code&gt; flag. See the &lt;a href=&quot;/docs/latest/deploying/spire_server/&quot;&gt;SPIRE Server reference&lt;/a&gt; for more information.&lt;/p&gt;</description></item><item><title>Deploying a Federated SPIRE Architecture</title><link>https://spiffe.io/docs/latest/architecture/federation/readme/</link><guid>https://spiffe.io/docs/latest/architecture/federation/readme/</guid><description>&lt;p&gt;This tutorial shows how to authenticate two SPIFFE-identified workloads that are identified by two different SPIRE Servers.&lt;/p&gt;
&lt;p&gt;The first part of this document demonstrates how to configure SPIFFE federation by showing the SPIRE configuration file changes and &lt;code&gt;spire-server&lt;/code&gt; commands used to set up a stock quote webapp frontend and service backend. The second part of this document lists the steps you run to show the scenario in action using the Docker Compose files included in this tutorial’s directory.&lt;/p&gt;</description></item><item><title>Deploying a Nested SPIRE Architecture</title><link>https://spiffe.io/docs/latest/architecture/nested/readme/</link><guid>https://spiffe.io/docs/latest/architecture/nested/readme/</guid><description>&lt;p&gt;Nested SPIRE allows SPIRE Servers to be “chained” together, and for all SPIRE Servers to issue identities in the same trust domain, meaning all workloads identified in the same trust domain are issued identity documents that can be verified against the root keys of the trust domain.&lt;/p&gt;
&lt;p&gt;Nested topologies work by co-locating a SPIRE Agent with every downstream SPIRE Server being “chained”. The downstream SPIRE Server obtains credentials over the Workload API that it uses to directly authenticate with the upstream SPIRE Server to obtain an intermediate CA.&lt;/p&gt;</description></item><item><title>Exposing Services</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/exposing/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/exposing/</guid><description>&lt;h1 id=&quot;default&quot;&gt;Default&lt;/h1&gt;
&lt;p&gt;By default no SPIRE services are exposed outside the Kubernetes cluster. The below sections cover how to expose them.&lt;/p&gt;
&lt;h1 id=&quot;exposable-services&quot;&gt;Exposable Services&lt;/h1&gt;
&lt;h2 id=&quot;production-services&quot;&gt;Production Services&lt;/h2&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Service Name&lt;/th&gt;&lt;th&gt;Section Value&lt;/th&gt;&lt;th&gt;Default DNS Name&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;SPIRE Server&lt;/td&gt;&lt;td&gt;spire-server.ingress&lt;/td&gt;&lt;td&gt;spire-server.$trustDomain&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SPIRE Federation Bundle Endpoint&lt;/td&gt;&lt;td&gt;spire-server.federation.ingress&lt;/td&gt;&lt;td&gt;spire-server-federation.$trustDomain&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SPIFFE OIDC Discovery Provider&lt;/td&gt;&lt;td&gt;spiffe-oidc-discovery-provider.ingress&lt;/td&gt;&lt;td&gt;oidc-discovery.$trustDomain&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;experimental-services&quot;&gt;Experimental Services&lt;/h2&gt;




















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Service Name&lt;/th&gt;&lt;th&gt;Value&lt;/th&gt;&lt;th&gt;Default DNS Name&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Tornjak Frontend&lt;/td&gt;&lt;td&gt;tornjak-frontend.ingress&lt;/td&gt;&lt;td&gt;tornjak-backend.$trustDomain&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Tornjak Backend&lt;/td&gt;&lt;td&gt;spire-server.tornjak.ingress&lt;/td&gt;&lt;td&gt;tornjak-frontend.$trustDomain&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h1 id=&quot;ingress-controller-support&quot;&gt;Ingress Controller Support&lt;/h1&gt;
&lt;p&gt;We have tests for ingress-nginx based Ingress Controllers and the Ingress Controller built into OpenShift.&lt;/p&gt;
&lt;p&gt;For ingress-nginx, set &lt;code&gt;global.spire.ingressControllerType=ingress-nginx&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;For OpenShift, set &lt;code&gt;global.openshift=true&lt;/code&gt;&lt;/p&gt;</description></item><item><title>Extend SPIRE</title><link>https://spiffe.io/docs/latest/planning/extending/</link><guid>https://spiffe.io/docs/latest/planning/extending/</guid><description>&lt;p&gt;SPIRE is highly extensible via a plugin framework that allows many core operations to be added and customized. This page describes the types of plugins available, how to integrate plugins while deploying SPIRE, and has a link to the SPIRE Plugin SDK for those interested in authoring a plugin.&lt;/p&gt;
&lt;h1 id=&quot;authoring-spire-plugins&quot;&gt;Authoring SPIRE plugins&lt;/h1&gt;
&lt;p&gt;Refer to the &lt;a href=&quot;https://github.com/spiffe/spire-plugin-sdk&quot;&gt;SPIRE Plugin SDK&lt;/a&gt; GitHub page for documentation and templates that you can use to code your own SPIRE plugins.&lt;/p&gt;</description></item><item><title>Federation</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-advanced/federation/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-advanced/federation/</guid><description>&lt;p&gt;The typical architecture for Federated SPIRE using the Helm charts uses a 1:1 relationship between SPIRE instances and Kubernetes Clusters, as well as multiple Kubernetes clusters.&lt;/p&gt;
&lt;h1 id=&quot;federation-configuration&quot;&gt;Federation Configuration&lt;/h1&gt;
&lt;p&gt;There are 4 pieces of configuration related to Federation.&lt;/p&gt;
&lt;h2 id=&quot;enabling-federation&quot;&gt;Enabling Federation&lt;/h2&gt;
&lt;p&gt;Set &lt;code&gt;spire-server.federation.enabled=true&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;your-values.yaml snippet:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;spire-server&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  federation&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;exposing-federation-bundle-endpoint-outside-the-kubernetes-cluster&quot;&gt;Exposing Federation Bundle Endpoint outside the Kubernetes Cluster&lt;/h2&gt;
&lt;p&gt;Set &lt;code&gt;spire-server.federation.ingress.enabled=true&lt;/code&gt;. Futher customization can be made as described in
&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/exposing/#generic-ingress-config&quot;&gt;Exposing Services&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;your-values.yaml snippet:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;spire-server&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  federation&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    ingress&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;configure-local-spire-to-talk-to-and-trust-other-spire-instances&quot;&gt;Configure local SPIRE to talk to and trust other SPIRE Instances&lt;/h2&gt;
&lt;p&gt;your-values.yaml snippet:&lt;/p&gt;</description></item><item><title>Get Involved</title><link>https://spiffe.io/docs/latest/spiffe-about/get-involved/</link><guid>https://spiffe.io/docs/latest/spiffe-about/get-involved/</guid><description>&lt;p&gt;SPIFFE is guided by a small but very active community of passionate software engineers with empathy for the problems that the project is tackling.&lt;/p&gt;
&lt;h2 id=&quot;join-the-community&quot;&gt;Join the Community&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Slack&lt;/strong&gt; — Most real-time discussions happen on SPIFFE’s Slack channels at &lt;a href=&quot;https://spiffe.slack.com&quot;&gt;https://spiffe.slack.com&lt;/a&gt;. You can join &lt;a href=&quot;https://slack.spiffe.io/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mailing lists&lt;/strong&gt; — Announcements occur in the SPIFFE &lt;a href=&quot;https://groups.google.com/a/spiffe.io/forum/#!forum/announce&quot;&gt;Google Group&lt;/a&gt;. There is also a &lt;a href=&quot;https://groups.google.com/a/spiffe.io/forum/#!forum/user-discussion&quot;&gt;users&lt;/a&gt; and &lt;a href=&quot;https://groups.google.com/a/spiffe.io/forum/#!forum/dev-discussion&quot;&gt;developers&lt;/a&gt; list.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Special Interest Groups and Working Groups&lt;/strong&gt; — The broader SPIFFE community is self-organized into Special Interest Groups (SIGs) that coordinate to manage specific aspects of SPIFFE’s design, and Working Groups (WGs) that focus on short-term cross-SIG initiatives. A list of active SIGs and WGs can be found &lt;a href=&quot;https://github.com/spiffe/spiffe/tree/main/community&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Getting SPIRE</title><link>https://spiffe.io/docs/latest/deploying/using_spire/</link><guid>https://spiffe.io/docs/latest/deploying/using_spire/</guid><description>&lt;p&gt;This page describes some options to get started with SPIRE.&lt;/p&gt;
&lt;h2 id=&quot;docker-compose&quot;&gt;Docker Compose&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href=&quot;/docs/latest/try/spire101/&quot;&gt;SPIRE 101&lt;/a&gt; is an introduction to SPIRE that runs on Docker Compose&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Additional Docker Compose demos are available in the &lt;a href=&quot;https://github.com/spiffe/spire-tutorials&quot;&gt;spire-tutorials&lt;/a&gt; repo&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;kubernetes&quot;&gt;Kubernetes&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;No official Helm chart, Kustomize file, or custom resource operator is available for SPIRE but &lt;a href=&quot;/docs/latest/spire/installing/getting-started-k8s/&quot;&gt;Quickstart for Kubernetes&lt;/a&gt; includes a basic set of Kubernetes YAML files for testing SPIRE Server and Agent&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Additional Kubernetes demos are available in the &lt;a href=&quot;https://github.com/spiffe/spire-tutorials&quot;&gt;spire-tutorials&lt;/a&gt; repo&lt;/p&gt;</description></item><item><title>How does SPIRE compare to other tools?</title><link>https://spiffe.io/docs/latest/spire-about/comparisons/</link><guid>https://spiffe.io/docs/latest/spire-about/comparisons/</guid><description>&lt;h1 id=&quot;secret-stores&quot;&gt;Secret Stores&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;e.g. Hashicorp Vault, Square Keywhiz&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Secrets managers typically control, audit and securely store sensitive information (secrets, typically passwords) on behalf of a workload. Some secrets managers can perform additional functions such as encrypting  and decrypting data. A common feature of many secrets managers is a central storage “vault” with data in the vault encrypted at rest. Workloads must individually authenticate to the vault before performing actions such as secret retrieval or data decryption.&lt;/p&gt;</description></item><item><title>Identifiers</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/identifiers/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/identifiers/</guid><description>&lt;h2 id=&quot;defaults&quot;&gt;Defaults&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;The chart deploys &lt;a href=&quot;https://github.com/spiffe/spire-controller-manager&quot;&gt;SPIRE Controller Manager&lt;/a&gt; to manage SPIFFE Identifiers by Kubernetes Custom Resources.&lt;/li&gt;
&lt;li&gt;The chart deploys a ClusterSPIFFEID Custom Resource that gives an identifier to all pods of the form &lt;code&gt;spiffe://{{ .TrustDomain }}/ns/{{ .PodMeta.Namespace }}/sa/{{ .PodSpec.ServiceAccountName }}&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;For a lot of use cases you don’t need to add additional identifiers.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;custom--additional-identifiers&quot;&gt;Custom / Additional Identifiers&lt;/h2&gt;
&lt;p&gt;In some cases you may want to customize your identifiers or add additional ones.&lt;/p&gt;</description></item><item><title>Install SPIRE Agents</title><link>https://spiffe.io/docs/latest/deploying/install-agents/</link><guid>https://spiffe.io/docs/latest/deploying/install-agents/</guid><description>&lt;h2 id=&quot;step-1&quot;&gt;Step 1: Obtain the SPIRE Binaries&lt;/h2&gt;
&lt;p&gt;Pre-built SPIRE releases can be found on the &lt;a href=&quot;/downloads/#spire-releases&quot;&gt;SPIRE downloads page&lt;/a&gt;. The tarballs contain both server and agent binaries.&lt;/p&gt;
&lt;p&gt;If you wish, you may also &lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0/CONTRIBUTING.md&quot;&gt;build SPIRE from source&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;step-2&quot;&gt;Step 2: Install the Server and Agent&lt;/h2&gt;
&lt;p&gt;This introductory guide describes how to install the server and agent on the same node. On a typical production deployment you will have the server installed on one node and one or more agents installed on distinct nodes.&lt;/p&gt;</description></item><item><title>Install the SPIRE Server</title><link>https://spiffe.io/docs/latest/deploying/install-server/</link><guid>https://spiffe.io/docs/latest/deploying/install-server/</guid><description>&lt;h2 id=&quot;step-1-obtain-the-spire-binaries&quot;&gt;Step 1: Obtain the SPIRE Binaries&lt;/h2&gt;
&lt;p&gt;Pre-built SPIRE releases can be found on the &lt;a href=&quot;/downloads/#spire-releases&quot;&gt;SPIRE downloads page&lt;/a&gt;. The tarballs contain both server and agent binaries.&lt;/p&gt;
&lt;p&gt;If you wish, you may also &lt;a href=&quot;https://github.com/spiffe/spire/blob/main/CONTRIBUTING.md&quot;&gt;build SPIRE from source&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;step-2&quot;&gt;Step 2: Install the Server and Agent&lt;/h2&gt;
&lt;p&gt;This introductory guide describes how to install the server and agent on the same node. On a typical production deployment you will have the server installed on one node and one or more agents installed on distinct nodes.&lt;/p&gt;</description></item><item><title>Installation</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/installation/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/installation/</guid><description>&lt;h2 id=&quot;quick-start&quot;&gt;Quick start&lt;/h2&gt;
&lt;p&gt;To do a quick install suitable for non production environments such as &lt;a href=&quot;https://minikube.sigs.k8s.io/docs/&quot;&gt;minikube&lt;/a&gt;:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;helm upgrade --install --create-namespace -n spire spire-crds spire-crds \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt; --repo https://spiffe.github.io/helm-charts-hardened/&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;helm upgrade --install -n spire spire spire \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt; --repo https://spiffe.github.io/helm-charts-hardened/&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;production-deployment&quot;&gt;Production Deployment&lt;/h2&gt;
&lt;p&gt;Preparing a production deployment requires a few extra steps.&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Save the following to your-values.yaml, ideally in your git repo.&lt;/li&gt;
&lt;/ol&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;global&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  openshift&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;false&lt;/span&gt;&lt;span style=&quot;color:#6A737D&quot;&gt; # If running on openshift, set to true&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  spire&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    recommendations&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    namespaces&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      create&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    ingressControllerType&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;&quot;&quot;&lt;/span&gt;&lt;span style=&quot;color:#6A737D&quot;&gt; # If not openshift, and want to expose services, set to a supported option [ingress-nginx]&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#6A737D&quot;&gt;    # Update these&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    clusterName&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;example-cluster&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    trustDomain&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;example.org&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    caSubject&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      country&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;ARPA&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      organization&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;Example&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      commonName&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;example.org&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;ol start=&quot;2&quot;&gt;
&lt;li&gt;If you need a non default storageClass, append the following to the spire-server section and update:&lt;/li&gt;
&lt;/ol&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;  persistence:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;    storageClass: your-storage-class&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;ol start=&quot;3&quot;&gt;
&lt;li&gt;If your Kubernetes cluster is OpenShift based, use the output of the following command to update the trustDomain setting:&lt;/li&gt;
&lt;/ol&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;shell&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#B392F0&quot;&gt;oc&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; get&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; cm&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; -n&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; openshift-config-managed&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt;  console-public&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; -o&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; go-template=&quot;{{ .data.consoleURL }}&quot;&lt;/span&gt;&lt;span style=&quot;color:#F97583&quot;&gt; |&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#B392F0&quot;&gt;  sed&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; &apos;s@https://@@; s/^[^.]*\.//&apos;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;ol start=&quot;4&quot;&gt;
&lt;li&gt;
&lt;p&gt;Find any additional values you might want to set based on the documentation on this site or the &lt;a href=&quot;https://github.com/spiffe/helm-charts-hardened/tree/main/examples&quot;&gt;examples&lt;/a&gt;. In particular, consider using an external database.&lt;/p&gt;</description></item><item><title>JWT-SVID</title><link>https://spiffe.io/docs/latest/spiffe-specs/jwt-svid/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/jwt-svid/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/JWT-SVID.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity document standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;table-of-contents&quot;&gt;Table of Contents&lt;/h2&gt;
&lt;p&gt;1. &lt;a href=&quot;#1-introduction&quot;&gt;Introduction&lt;/a&gt;&lt;br&gt;
2. &lt;a href=&quot;#2-jose-header&quot;&gt;JOSE Header&lt;/a&gt;&lt;br&gt;
2.1. &lt;a href=&quot;#21-algorithm&quot;&gt;Algorithm&lt;/a&gt;&lt;br&gt;
2.2. &lt;a href=&quot;#22-key-id&quot;&gt;Key ID&lt;/a&gt;&lt;br&gt;
2.3. &lt;a href=&quot;#23-type&quot;&gt;Type&lt;/a&gt;&lt;br&gt;
3. &lt;a href=&quot;#3-jwt-claims&quot;&gt;JWT Claims&lt;/a&gt;&lt;br&gt;
3.1. &lt;a href=&quot;#31-subject&quot;&gt;Subject&lt;/a&gt;&lt;br&gt;
3.2. &lt;a href=&quot;#32-audience&quot;&gt;Audience&lt;/a&gt;&lt;br&gt;
3.3. &lt;a href=&quot;#33-expiration-time&quot;&gt;Expiration Time&lt;/a&gt;&lt;br&gt;
4. &lt;a href=&quot;#4-token-signing-and-validation&quot;&gt;Token Signing and Validation&lt;/a&gt;&lt;br&gt;
5. &lt;a href=&quot;#5-token-transmission&quot;&gt;Token Transmission&lt;/a&gt;&lt;br&gt;
5.1. &lt;a href=&quot;#51-serialization&quot;&gt;Serialization&lt;/a&gt;&lt;br&gt;
5.2. &lt;a href=&quot;#52-http&quot;&gt;HTTP&lt;/a&gt;&lt;br&gt;
5.3. &lt;a href=&quot;#53-grpc&quot;&gt;gRPC&lt;/a&gt;&lt;br&gt;
6. &lt;a href=&quot;#6-representation-in-the-spiffe-bundle&quot;&gt;Representation in the SPIFFE Bundle&lt;/a&gt;&lt;br&gt;
6.1. &lt;a href=&quot;#61-publishing-spiffe-bundle-elements&quot;&gt;Publishing SPIFFE Bundle Elements&lt;/a&gt;&lt;br&gt;
6.2. &lt;a href=&quot;#62-consuming-a-spiffe-bundle&quot;&gt;Consuming a SPIFFE Bundle&lt;/a&gt;&lt;br&gt;
7. &lt;a href=&quot;#7-security-considerations&quot;&gt;Security Considerations&lt;/a&gt;&lt;br&gt;
7.1. &lt;a href=&quot;#71-replay-protection&quot;&gt;Replay Protection&lt;/a&gt;&lt;br&gt;
7.2. &lt;a href=&quot;#72-audience&quot;&gt;Audience&lt;/a&gt;&lt;br&gt;
7.3. &lt;a href=&quot;#73-transport-security&quot;&gt;Transport Security&lt;/a&gt;&lt;br&gt;
Appendix A. &lt;a href=&quot;#appendix-a-validation-reference&quot;&gt;Validation Reference&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Local Mirrors</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-advanced/mirror/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-advanced/mirror/</guid><description>&lt;h2 id=&quot;identify-containers-needing-mirroring&quot;&gt;Identify Containers needing mirroring&lt;/h2&gt;
&lt;p&gt;Run:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;bash&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#B392F0&quot;&gt;helm&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; template&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; spire&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; --repo&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; https://spiffe.github.io/helm-charts-hardened/&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; -f&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; your-values.yaml&lt;/span&gt;&lt;span style=&quot;color:#F97583&quot;&gt; |&lt;/span&gt;&lt;span style=&quot;color:#B392F0&quot;&gt; yq&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; e&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; -rN&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; &apos;[.spec, .spec.template.spec] | flatten(1) | .[]| [.containers, .initContainers] | flatten(1) | .[].image&apos;&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; -&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; \&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#F97583&quot;&gt; |&lt;/span&gt;&lt;span style=&quot;color:#B392F0&quot;&gt; sort&lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt; -u&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Example output:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;plaintext&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span&gt;cgr.dev/chainguard/bash:latest&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;cgr.dev/chainguard/kubectl:latest&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;cgr.dev/chainguard/wait-for-it:latest-20230113&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;ghcr.io/spiffe/spiffe-csi-driver:0.2.3&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;ghcr.io/spiffe/spire-agent:1.6.3&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;ghcr.io/spiffe/spire-controller-manager:0.2.2&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;ghcr.io/spiffe/spire-server:1.6.3&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span&gt;registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.6.2&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h2 id=&quot;mirror-containers&quot;&gt;Mirror Containers&lt;/h2&gt;
&lt;p&gt;Copy each container to your local repository, replacing the server name but keeping the paths.&lt;/p&gt;
&lt;p&gt;This is easiest to do with &lt;a href=&quot;https://github.com/containers/skopeo&quot;&gt;skopeo&lt;/a&gt; or &lt;a href=&quot;https://michaelsauter.github.io/crane/index.html&quot;&gt;crane&lt;/a&gt;, but can be done with docker as well.&lt;/p&gt;</description></item><item><title>Managing Upgrades/Downgrades</title><link>https://spiffe.io/docs/latest/maintenance/upgrading/</link><guid>https://spiffe.io/docs/latest/maintenance/upgrading/</guid><description>&lt;p&gt;This guide describes how to upgrade your SPIRE deployment, as well as the compatibility guarantees that SPIRE users can expect.&lt;/p&gt;
&lt;h2 id=&quot;spire-versioning&quot;&gt;SPIRE Versioning&lt;/h2&gt;
&lt;p&gt;SPIRE versions are expressed as &lt;strong&gt;x.y.z&lt;/strong&gt;, where &lt;strong&gt;x&lt;/strong&gt; is the major version, &lt;strong&gt;y&lt;/strong&gt; is the minor version, and &lt;strong&gt;z&lt;/strong&gt; is the patch version, following Semantic Versioning terminology. The last pre-1.0 versions are 0.12.x, which as an exception have compatibility warranties with 1.0.x. Versions prior to 0.12.0 are not compatible with 1.0.x.&lt;/p&gt;</description></item><item><title>Namespaces</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/namespaces/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/namespaces/</guid><description>&lt;p&gt;&lt;span id=&quot;namespace-creation-options.&quot;&gt;&lt;/span&gt;&lt;/p&gt;
&lt;h2 id=&quot;namespace-creation-options&quot;&gt;Namespace Creation Options&lt;/h2&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Value&lt;/th&gt;&lt;th&gt;Default Value&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;global.spire.namespaces.create&lt;/td&gt;&lt;td&gt;false&lt;/td&gt;&lt;td&gt;Create both recommeded namespaces&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;global.spire.namespaces.server.create&lt;/td&gt;&lt;td&gt;false&lt;/td&gt;&lt;td&gt;Create the namespace specified by global.spire.namespaces.server.name (default spire-server)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;global.spire.namespaces.system.create&lt;/td&gt;&lt;td&gt;false&lt;/td&gt;&lt;td&gt;Create the namespace specified by global.spire.namespaces.spire.name (default spire-server)&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;three-namespace-configuration&quot;&gt;Three Namespace Configuration&lt;/h2&gt;
&lt;p&gt;This is the recommended configuration, it automatically creates and deploys SPIRE across 3 namespaces.&lt;/p&gt;
&lt;p&gt;your-values.yaml snippet:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;global&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  spire&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    recommendations&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    namespaces&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      create&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This will create &lt;code&gt;spire-server&lt;/code&gt; and &lt;code&gt;spire-system&lt;/code&gt; namespaces, label them
for proper Kubernetes Pod Security Standards operations, and deploy the various
services appropriately.&lt;/p&gt;</description></item><item><title>Nested SPIRE</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-advanced/nested-spire/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-advanced/nested-spire/</guid><description>&lt;h2 id=&quot;nested-considerations&quot;&gt;Nested Considerations&lt;/h2&gt;
&lt;h3 id=&quot;architectures&quot;&gt;Architectures&lt;/h3&gt;
&lt;p&gt;The charts can be used to deploy many different styles of Nested SPIRE. A few possibilities are explained below.&lt;/p&gt;
&lt;h3 id=&quot;spire-controller-manager&quot;&gt;SPIRE Controller Manager&lt;/h3&gt;
&lt;p&gt;When multiple charts are installed at the same time with it enabled, they must use different classes. This is setup by default. Do not override without understanding the situation.&lt;/p&gt;
&lt;h3 id=&quot;ttls&quot;&gt;TTLs&lt;/h3&gt;
&lt;p&gt;&lt;em&gt;fixme&lt;/em&gt; note here about tradeoffs between longer ca’s more stable less risky for networking. longer ca time more risk of security issues.&lt;/p&gt;</description></item><item><title>OPA Authorization with Envoy and JWT-SVIDs</title><link>https://spiffe.io/docs/latest/microservices/envoy-jwt-opa/readme/</link><guid>https://spiffe.io/docs/latest/microservices/envoy-jwt-opa/readme/</guid><description>&lt;p&gt;&lt;a href=&quot;https://www.openpolicyagent.org/&quot;&gt;Open Policy Agent&lt;/a&gt; (OPA) is an open source, general-purpose policy engine. The authorization provided by OPA (AuthZ) can be a good complement to the authentication that SPIRE offers (AuthN).&lt;/p&gt;
&lt;p&gt;This tutorial builds on the &lt;a href=&quot;/docs/latest/microservices/envoy-jwt/readme/&quot;&gt;SPIRE Envoy-JWT Tutorial&lt;/a&gt; to demonstrate how to combine SPIRE, Envoy and OPA to perform JWT SVID authentication and request authorization. The changes required to implement request authorization with OPA are shown here as a delta to that tutorial, so you should run, or at least read through, the SPIRE Envoy-JWT tutorial first.&lt;/p&gt;</description></item><item><title>OPA Authorization with Envoy and X.509-SVIDs</title><link>https://spiffe.io/docs/latest/microservices/envoy-opa/readme/</link><guid>https://spiffe.io/docs/latest/microservices/envoy-opa/readme/</guid><description>&lt;p&gt;&lt;a href=&quot;https://www.openpolicyagent.org/&quot;&gt;Open Policy Agent&lt;/a&gt; (OPA) is an open source, general-purpose policy engine. The authorization provided by OPA (AuthZ) can be a good complement to the authentication that SPIRE offers (AuthN).&lt;/p&gt;
&lt;p&gt;This tutorial adds &lt;a href=&quot;https://www.openpolicyagent.org/&quot;&gt;Open Policy Agent&lt;/a&gt; (OPA) to the &lt;a href=&quot;/docs/latest/microservices/envoy-x509/readme/&quot;&gt;SPIRE Envoy-X.509 tutorial&lt;/a&gt; to demonstrate how to combine SPIRE, Envoy, and OPA to perform X.509 SVID authentication and request authorization. The changes required to implement request authorization with OPA are shown here as a delta to that tutorial, so you should run, or at least read through, the SPIRE Envoy-X.509 tutorial first.&lt;/p&gt;</description></item><item><title>Quickstart for Docker</title><link>https://spiffe.io/docs/latest/try/spire101/</link><guid>https://spiffe.io/docs/latest/try/spire101/</guid><description>&lt;h2 id=&quot;overview&quot;&gt;Overview&lt;/h2&gt;
&lt;p&gt;This walkthrough will guide you through the steps needed to set up a running example of a SPIRE Server and SPIRE Agent. Interaction with the &lt;a href=&quot;https://github.com/spiffe/go-spiffe/blob/main/proto/spiffe/workload/workload.proto&quot;&gt;Workload API&lt;/a&gt; will be simulated via a command line tool.&lt;/p&gt;
 &lt;figure&gt;&lt;img src=&quot;/img/checkouts/spiffe/spire/doc/images/SPIRE101.png&quot; style=&quot;width:100%&quot; alt=&quot;SPIRE101&quot;&gt;&lt;/figure&gt;
&lt;h2 id=&quot;requirements&quot;&gt;Requirement(s)&lt;/h2&gt;
&lt;h3 id=&quot;git-setup&quot;&gt;Git Setup&lt;/h3&gt;
&lt;p&gt;Clone the SPIRE github repo.&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;shell&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#B392F0&quot;&gt;$&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; git&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; clone&lt;/span&gt;&lt;span style=&quot;color:#9ECBFF&quot;&gt; https://github.com/spiffe/spire&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;docker-setup&quot;&gt;Docker Setup&lt;/h3&gt;
&lt;p&gt;If you don’t already have Docker installed, please follow these &lt;a href=&quot;https://docs.docker.com/engine/installation/&quot;&gt;installation instructions&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;terminology&quot;&gt;Terminology&lt;/h2&gt;





























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Term&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;spire-server&lt;/td&gt;&lt;td&gt;SPIRE Server executable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;spire-agent&lt;/td&gt;&lt;td&gt;SPIRE Agent executable&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;socketPath&lt;/td&gt;&lt;td&gt;Unix Domain Socket file path through which workloads connect to Workload API&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Join Token&lt;/td&gt;&lt;td&gt;Nonce generated by the SPIRE Server to attest SPIRE Agents&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;selector&lt;/td&gt;&lt;td&gt;A native property of a node or workload&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;walkthrough&quot;&gt;Walkthrough&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Build the development Docker image.&lt;/p&gt;</description></item><item><title>Quickstart for Kubernetes</title><link>https://spiffe.io/docs/latest/try/getting-started-k8s/</link><guid>https://spiffe.io/docs/latest/try/getting-started-k8s/</guid><description>&lt;h1 id=&quot;overview&quot;&gt;Overview&lt;/h1&gt;
&lt;p&gt;This guide walks you through getting a SPIRE Server and SPIRE Agent running in a Kubernetes cluster, and configuring a workload container to access SPIRE.&lt;/p&gt;
&lt;p&gt;In this introduction to SPIRE on Kubernetes you will learn how to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Create the appropriate Kubernetes namespaces and service accounts to deploy SPIRE&lt;/li&gt;
&lt;li&gt;Deploy the SPIRE Server as a Kubernetes statefulset&lt;/li&gt;
&lt;li&gt;Deploy the SPIRE Agent as a Kubernetes daemonset&lt;/li&gt;
&lt;li&gt;Configure a registration entry for a workload&lt;/li&gt;
&lt;li&gt;Fetch an x509-SVID over the SPIFFE Workload API&lt;/li&gt;
&lt;li&gt;Learn where to find resources for more complex installations&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The steps in this guide have been tested using Kubernetes versions 1.29 through 1.34.&lt;/p&gt;</description></item><item><title>Quickstart for Linux and MacOS X</title><link>https://spiffe.io/docs/latest/try/getting-started-linux-macos-x/</link><guid>https://spiffe.io/docs/latest/try/getting-started-linux-macos-x/</guid><description>&lt;h1 id=&quot;overview&quot;&gt;Overview&lt;/h1&gt;
&lt;p&gt;In this introduction to SPIRE you will learn how to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Start the spire-server process&lt;/li&gt;
&lt;li&gt;Attest a spire-agent to the server using a join token&lt;/li&gt;
&lt;li&gt;Configure a registration entry for a workload&lt;/li&gt;
&lt;li&gt;Fetch an x509-SVID over the WorkloadAPI&lt;/li&gt;
&lt;li&gt;Learn where to find resources for more complex installations&lt;/li&gt;
&lt;/ul&gt;
&lt;h1 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h1&gt;
&lt;ul&gt;
&lt;li&gt;A 64 bit Linux or macOS environment&lt;/li&gt;
&lt;li&gt;The openssl command line tool&lt;/li&gt;
&lt;li&gt;For macOS, Go 1.13 or higher must be installed to build SPIRE. See &lt;a href=&quot;https://golang.org/dl/&quot;&gt;https://golang.org/dl/&lt;/a&gt; or run &lt;code&gt;brew install golang&lt;/code&gt; .&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The commands in this getting started guide can be run as a standard user or root.&lt;/p&gt;</description></item><item><title>Recommendations</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/recommendations/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/recommendations/</guid><description>&lt;h1 id=&quot;enable-recommendations&quot;&gt;Enable Recommendations&lt;/h1&gt;
&lt;p&gt;In a production deployment there are a series of recommendations we
have. By enabling the recommendations, you can easily get all of
them applied to your deployment. If there are particular recommmendations
you do not wish to use, you can still set those recommendations to &lt;code&gt;false&lt;/code&gt;
to disable them.&lt;/p&gt;
&lt;p&gt;your-values.yaml snippet:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;global&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  spire&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;    recommendations&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;      enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;true&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;
&lt;h1 id=&quot;individual-recommentations&quot;&gt;Individual Recommentations&lt;/h1&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Name&lt;/th&gt;&lt;th&gt;Value&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/recommendations/#namespace-layout&quot;&gt;Namespace Layout&lt;/a&gt;&lt;/td&gt;&lt;td&gt;global.spire.recommendations.namespaceLayout&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/recommendations/#namespace-pod-security-standards&quot;&gt;Namespace Pod Security Standards&lt;/a&gt;&lt;/td&gt;&lt;td&gt;global.spire.recommendations.namespacePSS&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/recommendations/#priority-class-name&quot;&gt;PriorityClassName&lt;/a&gt;&lt;/td&gt;&lt;td&gt;global.spire.recommendations.priorityClassName&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/recommendations/#prometheus&quot;&gt;Prometheus&lt;/a&gt;&lt;/td&gt;&lt;td&gt;global.spire.recommendations.prometheus&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/recommendations/#namespace-layout&quot;&gt;Strict Mode&lt;/a&gt;&lt;/td&gt;&lt;td&gt;global.spire.recommendations.strictMode&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;/docs/latest/spire-helm-charts-hardened-about/recommendations/#security-contexts&quot;&gt;Security Contexts&lt;/a&gt;&lt;/td&gt;&lt;td&gt;global.spire.recommendations.securityContexts&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;namespace-layout&quot;&gt;Namespace Layout&lt;/h2&gt;
&lt;p&gt;Option &lt;code&gt;global.spire.recommendations.namespaceLayout&lt;/code&gt; causes the services to be deployed
across the two recommended namespaces for the services:&lt;/p&gt;</description></item><item><title>Registering workloads</title><link>https://spiffe.io/docs/latest/deploying/registering/</link><guid>https://spiffe.io/docs/latest/deploying/registering/</guid><description>&lt;h1 id=&quot;create-registration-entry&quot;&gt;How to create a registration entry&lt;/h1&gt;
&lt;p&gt;A registration entry contains the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a SPIFFE ID&lt;/li&gt;
&lt;li&gt;a set of one or more selectors&lt;/li&gt;
&lt;li&gt;a parent ID&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The server will send to the agent a list of all registration entries for workloads that are entitled to run on that node. Agents cache these registration entries and keep them updated.&lt;/p&gt;
&lt;p&gt;During workload attestation, the agent discovers selectors and compares them to those in the cached registration entries to determine which SVIDs they should assign to the workload.&lt;/p&gt;</description></item><item><title>Scaling SPIRE</title><link>https://spiffe.io/docs/latest/planning/scaling_spire/</link><guid>https://spiffe.io/docs/latest/planning/scaling_spire/</guid><description>&lt;h2 id=&quot;scalability&quot;&gt;Scalability&lt;/h2&gt;
&lt;p&gt;A SPIRE deployment has the capacity to be changed in size or scale to accommodate a growing amount of workloads. A SPIRE deployment is composed of a number of one or more SPIRE Servers that share a replicated datastore, or conversely, a set of SPIRE servers in the same trust domain, and at least one SPIRE Agent, but typically more than one.&lt;/p&gt;
&lt;p&gt;Deployments range in size. A single SPIRE Server may accommodate a number of Agents and Workload Registration entries. A scale sizing consideration is that the memory and CPU consumption of SPIRE Server instances tends to grow proportionally to the number of Workload Registration entries in a deployment due to the number of operations involved in managing and issuing identities corresponding to those entries. A single instance of a SPIRE Server also represents a single point of failure.&lt;/p&gt;</description></item><item><title>Secure Production Identity Framework for Everyone</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity and identity issuance standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Distributed design patterns and practices such as microservices, container orchestrators, and cloud computing have led to production environments that are increasingly dynamic and heterogeneous. Conventional security practices (such as network policies that only allow traffic between particular IP addresses) struggle to scale under this complexity. A first-class identity framework for workloads in an organization becomes necessary.&lt;/p&gt;</description></item><item><title>Service Selection</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/service-selection/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/service-selection/</guid><description>&lt;h1 id=&quot;services-provided-by-the-chart&quot;&gt;Services provided by the chart&lt;/h1&gt;
&lt;p&gt;There are multiple services provided by the chart. They can be enabled/disabled as needed using helm
values.&lt;/p&gt;
&lt;h2 id=&quot;production-services&quot;&gt;Production Services&lt;/h2&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Service Name&lt;/th&gt;&lt;th&gt;Value&lt;/th&gt;&lt;th&gt;Enabled by Default&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;SPIRE Server&lt;/td&gt;&lt;td&gt;spire-server.enabled&lt;/td&gt;&lt;td&gt;true&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SPIRE Agent&lt;/td&gt;&lt;td&gt;spire-agent.enabled&lt;/td&gt;&lt;td&gt;true&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SPIRE Controller Manager&lt;/td&gt;&lt;td&gt;spire-server.spireControllerManager.enabled&lt;/td&gt;&lt;td&gt;true&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SPIFFE OIDC Discovery Provider&lt;/td&gt;&lt;td&gt;spiffe-oidc-discovery-provider.enabled&lt;/td&gt;&lt;td&gt;true&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SPIFFE CSI Driver&lt;/td&gt;&lt;td&gt;spiffe-csi-driver.enabled&lt;/td&gt;&lt;td&gt;true&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;experimental-services&quot;&gt;Experimental Services&lt;/h2&gt;




















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Service Name&lt;/th&gt;&lt;th&gt;Value&lt;/th&gt;&lt;th&gt;Enabled by Default&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;Tornjak Frontend&lt;/td&gt;&lt;td&gt;tornjak-frontend.enabled&lt;/td&gt;&lt;td&gt;false&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Tornjak Backend&lt;/td&gt;&lt;td&gt;spire-server.tornjak.enabled&lt;/td&gt;&lt;td&gt;false&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;customization-examples&quot;&gt;Customization Examples&lt;/h2&gt;
&lt;p&gt;Example: Running the SPIRE Server Standalone:&lt;/p&gt;
&lt;p&gt;your-values.yaml snippet:&lt;/p&gt;
&lt;pre class=&quot;astro-code github-dark&quot; style=&quot;background-color:#24292e;color:#e1e4e8; overflow-x: auto;&quot; tabindex=&quot;0&quot; data-language=&quot;yaml&quot; dir=&quot;ltr&quot;&gt;&lt;code&gt;&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;spire-agent&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;false&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;spiffe-oidc-discovery-provider&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;false&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;spiffe-csi-driver&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;:&lt;/span&gt;&lt;/span&gt;
&lt;span class=&quot;line&quot;&gt;&lt;span style=&quot;color:#85E89D&quot;&gt;  enabled&lt;/span&gt;&lt;span style=&quot;color:#E1E4E8&quot;&gt;: &lt;/span&gt;&lt;span style=&quot;color:#79B8FF&quot;&gt;false&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;</description></item><item><title>Solving the Bottom Turtle</title><link>https://spiffe.io/book/</link><guid>https://spiffe.io/book/</guid><description>&lt;div class=&quot;hero-body&quot;&gt;
    &lt;p class=&quot;book title is-size-2 is-size-2-mobile has-text-weight-light&quot;&gt;
        About the Book: &lt;i&gt;Solving the Bottom Turtle&lt;/i&gt;
    &lt;/p&gt;
&lt;/div&gt;
&lt;div class=&quot;columns&quot;&gt;
    &lt;div class=&quot;column&quot;&gt;
        &lt;p&gt;
            This book presents the SPIFFE standard for service identity, and SPIRE, the reference implementation for
            SPIFFE. These projects provide a uniform identity control plane across modern, heterogeneous
            infrastructure. Both projects are open source and are part of the Cloud
            Native Computing Foundation.
        &lt;/p&gt;
        &lt;p&gt;
            As organizations grow their application architectures to make the most of new infrastructure
            technologies, their security models must also evolve. Software has grown from one monolith on one box,
            to dozens or hundreds of tightly linked microservices that may be spread across thousands of virtual
            machines in public clouds or private data centers. In this new infrastructure world, SPIFFE and SPIRE
            help keep systems secure.
        &lt;/p&gt;</description></item><item><title>SPIFFE Broker API</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_broker_api/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_broker_api/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Broker_API.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Broker_API.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Incubating&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity API standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Brokers are trusted infrastructure components that can act on-behalf-of workloads. This API enables them to retrieve the SVIDs and trust bundles of workloads they represent by referencing each workload with a workload reference (for example, a process ID or a Kubernetes object).&lt;/p&gt;</description></item><item><title>SPIFFE Broker Endpoint</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_broker_endpoint/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_broker_endpoint/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Broker_Endpoint.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Broker_Endpoint.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Incubating&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity endpoint standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;The SPIFFE Broker Endpoint is a dedicated endpoint for trusted infrastructure components in SPIFFE. It offers specific APIs that are not targeted to workloads but components in the infrastructure that can act on behalf of workloads and request corresponding SVIDs.&lt;/p&gt;</description></item><item><title>SPIFFE Concepts</title><link>https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/</link><guid>https://spiffe.io/docs/latest/spiffe-about/spiffe-concepts/</guid><description>&lt;p&gt;This section looks at some basic concepts in SPIFFE that we refer to frequently throughout this overview.&lt;/p&gt;
&lt;h2 id=&quot;workload&quot;&gt;Workload&lt;/h2&gt;
&lt;p&gt;A workload is a single piece of software, deployed with a particular configuration for a single purpose; it may comprise multiple running instances of software, all of which perform the same task. The term “workload” may encompass a range of different definitions of a software system, including:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A web server running a Python web application, running on a cluster of virtual machines with a load-balancer in front of it.&lt;/li&gt;
&lt;li&gt;An instance of a MySQL database.&lt;/li&gt;
&lt;li&gt;A worker program processing items on a queue.&lt;/li&gt;
&lt;li&gt;A collection of independently deployed systems that work together, such as a web application that uses a database service. The web application and database could also individually be considered workloads.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For SPIFFE’s purposes, a workload may often be more fine-grained than a physical or virtual node – often as fine grained as individual processes on the node. This is crucial for workloads that, for example, are hosted in a container orchestrator, where several workloads may be coexisting (yet be isolated from each other) on a single node.&lt;/p&gt;</description></item><item><title>SPIFFE Ecosystem</title><link>https://spiffe.io/docs/latest/spiffe-about/ecosystem/</link><guid>https://spiffe.io/docs/latest/spiffe-about/ecosystem/</guid><description>&lt;p&gt;SPIFFE is supported by a broad ecosystem of projects, ranging from the core specifications and their reference implementation through to SDKs, deployment tooling, and the many open-source and commercial platforms that issue or consume SPIFFE identities.&lt;/p&gt;
&lt;p&gt;This page collects some of the more notable projects, grouped by what they do. Each one is marked as a SPIFFE official project, a community project, or a commercial offering. The list is not exhaustive - if a project is missing, contributions are welcome via a &lt;a href=&quot;https://github.com/spiffe/spiffe.io&quot;&gt;pull request to this site&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>SPIFFE Federation</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_federation/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_federation/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Federation.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Federation.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity API standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;table-of-contents&quot;&gt;Table of Contents&lt;/h2&gt;
&lt;p&gt;1. &lt;a href=&quot;#1-background&quot;&gt;Background&lt;/a&gt;&lt;br&gt;
2. &lt;a href=&quot;#2-introduction&quot;&gt;Introduction&lt;/a&gt;&lt;br&gt;
3. &lt;a href=&quot;#3-targeted-use-cases&quot;&gt;Targeted Use Cases&lt;/a&gt;&lt;br&gt;
4. &lt;a href=&quot;#4-spiffe-bundle-endpoint&quot;&gt;SPIFFE Bundle Endpoint&lt;/a&gt;&lt;br&gt;
4.1. &lt;a href=&quot;#41-adding-and-removing-keys&quot;&gt;Adding and Removing Keys&lt;/a&gt;&lt;br&gt;
4.2. &lt;a href=&quot;#42-managing-fetched-bundles&quot;&gt;Managing Fetched Bundles&lt;/a&gt;&lt;br&gt;
4.3. &lt;a href=&quot;#43-endpoint-address-stability&quot;&gt;Endpoint Address Stability&lt;/a&gt;&lt;br&gt;
5. &lt;a href=&quot;#5-serving-and-consuming-a-spiffe-bundle-endpoint&quot;&gt;Serving and Consuming a SPIFFE Bundle Endpoint&lt;/a&gt;&lt;br&gt;
5.1. &lt;a href=&quot;#51-endpoint-parameters&quot;&gt;Endpoint Parameters&lt;/a&gt;&lt;br&gt;
5.2. &lt;a href=&quot;#52-endpoint-profiles&quot;&gt;Endpoint Profiles&lt;/a&gt;&lt;br&gt;
5.2.1. &lt;a href=&quot;#521-web-pki-https_web&quot;&gt;Web PKI (&lt;code&gt;https_web&lt;/code&gt;)&lt;/a&gt;&lt;br&gt;
5.2.1.1. &lt;a href=&quot;#5211-endpoint-url-requirements&quot;&gt;Endpoint URL Requirements&lt;/a&gt;&lt;br&gt;
5.2.1.2. &lt;a href=&quot;#5212-endpoint-parameters&quot;&gt;Endpoint Parameters&lt;/a&gt;&lt;br&gt;
5.2.1.3. &lt;a href=&quot;#5213-serving-a-bundle-endpoint&quot;&gt;Serving a Bundle Endpoint&lt;/a&gt;&lt;br&gt;
5.2.1.4. &lt;a href=&quot;#5214-consuming-a-bundle-endpoint&quot;&gt;Consuming a Bundle Endpoint&lt;/a&gt;&lt;br&gt;
5.2.2. &lt;a href=&quot;#522-spiffe-authentication-https_spiffe&quot;&gt;SPIFFE Authentication (&lt;code&gt;https_spiffe&lt;/code&gt;)&lt;/a&gt;&lt;br&gt;
5.2.2.1. &lt;a href=&quot;#5221-endpoint-url-requirements&quot;&gt;Endpoint URL Requirements&lt;/a&gt;&lt;br&gt;
5.2.2.2. &lt;a href=&quot;#5222-endpoint-parameters&quot;&gt;Endpoint Parameters&lt;/a&gt;&lt;br&gt;
5.2.2.3. &lt;a href=&quot;#5223-serving-a-bundle-endpoint&quot;&gt;Serving a Bundle Endpoint&lt;/a&gt;&lt;br&gt;
5.2.2.4. &lt;a href=&quot;#5224-consuming-a-bundle-endpoint&quot;&gt;Consuming a Bundle Endpoint&lt;/a&gt;&lt;br&gt;
6. &lt;a href=&quot;#6-relationship-lifecycle&quot;&gt;Relationship Lifecycle&lt;/a&gt;&lt;br&gt;
6.1. &lt;a href=&quot;#61-establishing-a-relationship&quot;&gt;Establishing a Relationship&lt;/a&gt;&lt;br&gt;
6.2. &lt;a href=&quot;#62-maintaining-a-relationship&quot;&gt;Maintaining a Relationship&lt;/a&gt;&lt;br&gt;
6.3. &lt;a href=&quot;#63-terminating-a-relationship&quot;&gt;Terminating a Relationship&lt;/a&gt;&lt;br&gt;
6.4. &lt;a href=&quot;#64-lifecycle-diagram&quot;&gt;Lifecycle Diagram&lt;/a&gt;&lt;br&gt;
7. &lt;a href=&quot;#7-security-considerations&quot;&gt;Security Considerations&lt;/a&gt;&lt;br&gt;
7.1. &lt;a href=&quot;#71-distribution-of-endpoint-parameters&quot;&gt;Distribution of Endpoint Parameters&lt;/a&gt;&lt;br&gt;
7.2. &lt;a href=&quot;#72-explicitly-defined-endpoint-parameters&quot;&gt;Explicitly-defined Endpoint Parameters&lt;/a&gt;&lt;br&gt;
7.3. &lt;a href=&quot;#73-preserving-the-trust-domain-bundle-binding&quot;&gt;Preserving the &lt;code&gt;&amp;#x3C;Trust Domain, Bundle&gt;&lt;/code&gt; Binding&lt;/a&gt;&lt;br&gt;
7.4. &lt;a href=&quot;#74-trustworthiness-of-the-bundle-endpoint-server&quot;&gt;Trustworthiness of the Bundle Endpoint Server&lt;/a&gt;&lt;br&gt;
7.5. &lt;a href=&quot;#75-authenticity-of-the-bundle-endpoint&quot;&gt;Authenticity of the Bundle Endpoint&lt;/a&gt;&lt;br&gt;
7.5.1. &lt;a href=&quot;#751-bundle-endpoint-url-redirection&quot;&gt;Bundle Endpoint URL Redirection&lt;/a&gt;&lt;br&gt;
7.5.2. &lt;a href=&quot;#752-network-traffic-interception&quot;&gt;Network Traffic Interception&lt;/a&gt;&lt;br&gt;
7.5.3. &lt;a href=&quot;#753-endpoint-parameters&quot;&gt;Endpoint Parameters&lt;/a&gt;&lt;br&gt;
7.6. &lt;a href=&quot;#76-chaining-trust-with-https_spiffe&quot;&gt;Chaining Trust with &lt;code&gt;https_spiffe&lt;/code&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>SPIFFE Filesystem Delivery</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_filesystem_delivery/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_filesystem_delivery/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Filesystem_Delivery.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Filesystem_Delivery.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Incubating&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity API standard for the internet community, and
requests discussion and suggestions for improvements. Distribution of this
document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Many applications run in environments where SPIFFE certificates and trust
bundles are more easily delivered via the filesystem, rather than the SPIFFE
Workload API.  This specification gives applications and identity provisioning
systems a concrete target to aim for:&lt;/p&gt;</description></item><item><title>SPIFFE Identity and Verifiable Identity Document</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe-id/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe-id/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE-ID.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE-ID.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity and identity issuance standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;The SPIFFE standard provides a specification for a framework capable of bootstrapping and issuing identity to services across heterogeneous environments and organizational boundaries. It encompasses a variety of specifications, each defining the operation of a specific subset of the SPIFFE functionality.&lt;/p&gt;</description></item><item><title>SPIFFE Library Usage Examples</title><link>https://spiffe.io/docs/latest/deploying/libraries/</link><guid>https://spiffe.io/docs/latest/deploying/libraries/</guid><description>&lt;p&gt;You can use one of the following libraries to fetch SVIDs and trust bundles from within your applications. These libraries handle the work of interfacing with the SPIFFE Workload API to make your coding easier.&lt;/p&gt;
&lt;p&gt;The following code samples demonstrate how to use the libraries to establish and maintain SPIFFE-enabled connections transparently between applications.&lt;/p&gt;
&lt;h1 id=&quot;c-c&quot;&gt;C, C++&lt;/h1&gt;
&lt;p&gt;See the &lt;a href=&quot;https://github.com/HewlettPackard/c-spiffe&quot;&gt;c-spiffe library GitHub page&lt;/a&gt; for more information about a SPIFFE C/C++ library. This library is not yet part of the official SPIFFE repo and is still under development in June 2021. An earlier official c-spiffe library became out-of-date and was archived.&lt;/p&gt;</description></item><item><title>SPIFFE Overview</title><link>https://spiffe.io/docs/latest/spiffe-about/overview/</link><guid>https://spiffe.io/docs/latest/spiffe-about/overview/</guid><description>&lt;p&gt;&lt;strong&gt;SPIFFE&lt;/strong&gt;, the Secure Production Identity Framework for Everyone, is a set of open-source standards for securely identifying software systems in dynamic and heterogeneous environments. Systems that adopt SPIFFE can easily and reliably mutually authenticate wherever they are running.&lt;/p&gt;
&lt;p&gt;Distributed design patterns and practices such as micro-services, container orchestrators, and cloud computing have led to production environments that are increasingly dynamic and heterogeneous. Conventional security practices (such as network policies that only allow traffic between particular IP addresses) struggle to scale under this complexity. A first-class identity framework for workloads in an organization becomes necessary.&lt;/p&gt;</description></item><item><title>SPIFFE Specification Stability</title><link>https://spiffe.io/docs/latest/spiffe-specs/stability/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/stability/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/STABILITY.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/STABILITY.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;h2 id=&quot;table-of-contents&quot;&gt;Table of Contents&lt;/h2&gt;
&lt;p&gt;1. &lt;a href=&quot;#1-what-this-is&quot;&gt;What this is&lt;/a&gt;&lt;br&gt;
2. &lt;a href=&quot;#2-stability-levels&quot;&gt;Stability levels&lt;/a&gt;&lt;br&gt;
2.1. &lt;a href=&quot;#21-proposed&quot;&gt;Proposed&lt;/a&gt;&lt;br&gt;
2.2. &lt;a href=&quot;#22-experimental&quot;&gt;Experimental&lt;/a&gt;&lt;br&gt;
2.3. &lt;a href=&quot;#23-incubating&quot;&gt;Incubating&lt;/a&gt;&lt;br&gt;
2.4. &lt;a href=&quot;#24-stable&quot;&gt;Stable&lt;/a&gt;&lt;br&gt;
3. &lt;a href=&quot;#3-marking-stability&quot;&gt;Marking stability&lt;/a&gt;&lt;br&gt;
3.1. &lt;a href=&quot;#31-marking-part-of-a-specification&quot;&gt;Marking part of a specification&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&quot;1-what-this-is&quot;&gt;1. What this is&lt;/h2&gt;
&lt;p&gt;This document defines stability levels for SPIFFE &lt;em&gt;specifications&lt;/em&gt; and the
process for moving a specification between them.&lt;/p&gt;
&lt;p&gt;This is distinct from &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main//MATURITY.md&quot;&gt;MATURITY.md&lt;/a&gt;, which describes the maturity
of SPIFFE &lt;em&gt;software projects&lt;/em&gt; (e.g. SPIRE). This document (STABILITY.md) is
only concerned with the stability of specifications.&lt;/p&gt;</description></item><item><title>SPIFFE Trust Domain and Bundle</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_trust_domain_and_bundle/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_trust_domain_and_bundle/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Trust_Domain_and_Bundle.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Trust_Domain_and_Bundle.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity document standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;The SPIFFE standard provides a specification for a framework capable of bootstrapping and issuing interoperable identity to services across heterogeneous environments and organizations. It defines a concept known as “trust domains” which are used to delineate administrative and/or security boundaries. Trust domains isolate issuing authorities and differentiate identity namespaces, but can also be loosely coupled to provide federation.&lt;/p&gt;</description></item><item><title>SPIFFE Workload API</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_workload_api/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_workload_api/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_API.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity API standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Portable and interoperable cryptographic identity for networked workloads is perhaps &lt;em&gt;the&lt;/em&gt; core use case for SPIFFE. In order to wholly address this requirement, the community must converge upon a standardized way to retrieve, validate, and interact with SPIFFE identities. This specification outlines the API signatures and client/server behavior required in order to support SPIFFE-based authentication systems.&lt;/p&gt;</description></item><item><title>SPIFFE Workload Endpoint</title><link>https://spiffe.io/docs/latest/spiffe-specs/spiffe_workload_endpoint/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/spiffe_workload_endpoint/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_Endpoint.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/SPIFFE_Workload_Endpoint.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity endpoint standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;Portable and interoperable cryptographic identity for networked workloads is perhaps &lt;em&gt;the&lt;/em&gt; core use case for SPIFFE. In order to wholly address this requirement, the community must converge upon a standardized way to both retrieve identity and consume identity-related services at runtime.&lt;/p&gt;</description></item><item><title>SPIRE Agent Configuration Reference</title><link>https://spiffe.io/docs/latest/deploying/spire_agent/</link><guid>https://spiffe.io/docs/latest/deploying/spire_agent/</guid><description>&lt;p&gt;This document is a configuration reference for SPIRE Agent. It includes information about plugin types, built-in plugins, the agent configuration file, plugin configuration, and command line options for &lt;code&gt;spire-agent&lt;/code&gt; commands.&lt;/p&gt;
&lt;h2 id=&quot;plugin-types&quot;&gt;Plugin types&lt;/h2&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;Generates and stores the agent’s private key. Useful for binding keys to hardware, etc.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;Gathers information used to attest the agent’s identity to the server. Generally paired with a server plugin of the same type.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WorkloadAttestor&lt;/td&gt;&lt;td&gt;Introspects a workload to determine its properties, generating a set of selectors associated with it.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SVIDStore&lt;/td&gt;&lt;td&gt;Stores X509-SVIDs (Private key, leaf certificate and intermediates if any), bundle, and federated bundles into a trust store.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;built-in-plugins&quot;&gt;Built-in plugins&lt;/h2&gt;




































































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Name&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_keymanager_disk.md&quot;&gt;disk&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A key manager which writes the private key to disk&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_keymanager_memory.md&quot;&gt;memory&lt;/a&gt;&lt;/td&gt;&lt;td&gt;An in-memory key manager which does not persist private keys (must re-attest after restarts)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_aws_iid.md&quot;&gt;aws_iid&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an AWS Instance Identity Document&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_azure_imds.md&quot;&gt;azure_imds&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using the Azure Instance Metadata Service&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_azure_msi.md&quot;&gt;azure_msi&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an Azure MSI token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_gcp_iit.md&quot;&gt;gcp_iit&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using a GCP Instance Identity Token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_jointoken.md&quot;&gt;join_token&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which uses a server-generated join token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_k8s_psat.md&quot;&gt;k8s_psat&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using a Kubernetes Projected Service Account token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_sshpop.md&quot;&gt;sshpop&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an existing ssh certificate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_tpm_devid.md&quot;&gt;tpm_devid&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using a TPM that has been provisioned with a DevID certificate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_nodeattestor_x509pop.md&quot;&gt;x509pop&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an existing X.509 certificate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WorkloadAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_workloadattestor_docker.md&quot;&gt;docker&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A workload attestor which allows selectors based on docker constructs such &lt;code&gt;label&lt;/code&gt; and &lt;code&gt;image_id&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WorkloadAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_workloadattestor_k8s.md&quot;&gt;k8s&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A workload attestor which allows selectors based on Kubernetes constructs such &lt;code&gt;ns&lt;/code&gt; (namespace) and &lt;code&gt;sa&lt;/code&gt; (service account)&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WorkloadAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_workloadattestor_unix.md&quot;&gt;unix&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A workload attestor which generates unix-based selectors like &lt;code&gt;uid&lt;/code&gt; and &lt;code&gt;gid&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WorkloadAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_workloadattestor_systemd.md&quot;&gt;systemd&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A workload attestor which generates selectors based on systemd unit properties such as &lt;code&gt;Id&lt;/code&gt; and &lt;code&gt;FragmentPath&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;WorkloadAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_workloadattestor_slurm.md&quot;&gt;slurm&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A workload attestor which allows selectors based on Slurm job information&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SVIDStore&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_svidstore_aws_secretsmanager.md&quot;&gt;aws_secretsmanager&lt;/a&gt;&lt;/td&gt;&lt;td&gt;An SVIDstore which stores secrets in the AWS secrets manager with the resulting X509-SVIDs of the entries that the agent is entitled to.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;SVIDStore&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_agent_svidstore_gcp_secretmanager.md&quot;&gt;gcp_secretmanager&lt;/a&gt;&lt;/td&gt;&lt;td&gt;An SVIDStore which stores secrets in the Google Cloud Secret Manager with the resulting X509-SVIDs of the entries that the agent is entitled to.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;agent-configuration-file&quot;&gt;Agent configuration file&lt;/h2&gt;
&lt;p&gt;The following table outlines the configuration options for SPIRE agent. These may be set in a top-level &lt;code&gt;agent { ... }&lt;/code&gt; section of the configuration file. Most options have a corresponding CLI flag which, if set, takes precedence over values defined in the file.&lt;/p&gt;</description></item><item><title>SPIRE Case Studies</title><link>https://spiffe.io/docs/latest/spire-about/case-studies/</link><guid>https://spiffe.io/docs/latest/spire-about/case-studies/</guid><description>&lt;div class=&quot;presentation&quot;&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=fxtG1wuLSDw&amp;amp;feature=youtu.be&amp;amp;t=17m37s&quot;&gt;&lt;img src=&quot;https://img.youtube.com/vi/fxtG1wuLSDw/1.jpg&quot; width=&quot;120&quot; height=&quot;90&quot; alt=&quot;&quot;&gt;&lt;/a&gt;&lt;div&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=fxtG1wuLSDw&amp;amp;feature=youtu.be&amp;amp;t=17m37s&quot;&gt;&lt;strong&gt;How Network Service Mesh uses SPIFFE and SPIRE&lt;/strong&gt;&lt;/a&gt; (Network Service Mesh)&lt;p&gt;A brief overview of how the open source project Network Service Mesh is integrating SPIFFE/SPIRE&lt;/p&gt;&lt;p&gt;&lt;i&gt;Presented by Ed Warnicke at SPIFFE Community Day on 24-Apr-2020.&lt;/i&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;
&lt;div class=&quot;presentation&quot;&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=fxtG1wuLSDw&amp;amp;feature=youtu.be&amp;amp;t=14m41s&quot;&gt;&lt;img src=&quot;https://img.youtube.com/vi/fxtG1wuLSDw/1.jpg&quot; width=&quot;120&quot; height=&quot;90&quot; alt=&quot;&quot;&gt;&lt;/a&gt;&lt;div&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=fxtG1wuLSDw&amp;amp;feature=youtu.be&amp;amp;t=14m41s&quot;&gt;&lt;strong&gt;How Frontdoor is using SPIRE&lt;/strong&gt;&lt;/a&gt; (Frontdoor)&lt;p&gt;A brief overview of how Frontdoor is using SPIRE&lt;/p&gt;&lt;p&gt;&lt;i&gt;Presented by Domingo Kiser at SPIFFE Community Day on 24-Apr-2020.&lt;/i&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;
&lt;div class=&quot;presentation&quot;&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=fxtG1wuLSDw&amp;amp;feature=youtu.be&amp;amp;t=6m2s&quot;&gt;&lt;img src=&quot;https://img.youtube.com/vi/fxtG1wuLSDw/1.jpg&quot; width=&quot;120&quot; height=&quot;90&quot; alt=&quot;&quot;&gt;&lt;/a&gt;&lt;div&gt;&lt;a href=&quot;https://www.youtube.com/watch?v=fxtG1wuLSDw&amp;amp;feature=youtu.be&amp;amp;t=6m2s&quot;&gt;&lt;strong&gt;How doc.ai and Anthem are using SPIRE&lt;/strong&gt;&lt;/a&gt; (doc.ai, Anthem)&lt;p&gt;A brief overview of how doc.ai and Anthem are implementing zero-trust authentication using SPIRE&lt;/p&gt;</description></item><item><title>SPIRE Concepts</title><link>https://spiffe.io/docs/latest/spire-about/spire-concepts/</link><guid>https://spiffe.io/docs/latest/spire-about/spire-concepts/</guid><description>&lt;p&gt;SPIRE is a production-ready implementation of the &lt;a href=&quot;/docs/latest/spiffe/overview/&quot;&gt;SPIFFE APIs&lt;/a&gt; that performs node and workload attestation in order to securely issue SVIDs to workloads, and verify the SVIDs of other workloads, based on a predefined set of conditions.&lt;/p&gt;
&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;SPIRE is just one implementation of the SPIFFE specification. For a list of current implementations, see the &lt;a href=&quot;/&quot;&gt;spiffe.io homepage&lt;/a&gt;.&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;p&gt;This section describes the architecture and components of SPIRE, walks you through “a day in the life of” how SPIRE issues an identity to a workload, and looks at some basic SPIRE concepts.&lt;/p&gt;</description></item><item><title>SPIRE Server Configuration Reference</title><link>https://spiffe.io/docs/latest/deploying/spire_server/</link><guid>https://spiffe.io/docs/latest/deploying/spire_server/</guid><description>&lt;p&gt;This document is a configuration reference for SPIRE Server. It includes information about plugin types, built-in plugins, the server configuration file, plugin configuration, and command line options for &lt;code&gt;spire-server&lt;/code&gt; commands.&lt;/p&gt;
&lt;h2 id=&quot;plugin-types&quot;&gt;Plugin types&lt;/h2&gt;





































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th align=&quot;left&quot;&gt;Type&lt;/th&gt;&lt;th align=&quot;left&quot;&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;DataStore&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;Provides persistent storage and HA features. &lt;strong&gt;Note:&lt;/strong&gt; Pluggability for the DataStore is no longer supported. Only the built-in SQL plugin can be used.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;KeyManager&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;Implements both signing and key storage logic for the server’s signing operations. Useful for leveraging hardware-based key operations.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;CredentialComposer&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;Allows customization of SVID and CA attributes.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;NodeAttestor&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;Implements validation logic for nodes attempting to assert their identity. Generally paired with an agent plugin of the same type.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;UpstreamAuthority&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;Allows SPIRE server to integrate with existing PKI systems.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;Notifier&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;&lt;strong&gt;Deprecated:&lt;/strong&gt; use BundlePublisher instead. Notified by SPIRE server for certain events that are happening or have happened. For events that are happening, the notifier can advise SPIRE server on the outcome.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td align=&quot;left&quot;&gt;BundlePublisher&lt;/td&gt;&lt;td align=&quot;left&quot;&gt;Publishes the local trust bundle to a store.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;built-in-plugins&quot;&gt;Built-in plugins&lt;/h2&gt;
































































































































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Name&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;DataStore&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_datastore_sql.md&quot;&gt;sql&lt;/a&gt;&lt;/td&gt;&lt;td&gt;An SQL database storage for SQLite, PostgreSQL and MySQL databases for the SPIRE datastore&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_keymanager_aws_kms.md&quot;&gt;aws_kms&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A key manager which manages keys in AWS KMS&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_keymanager_disk.md&quot;&gt;disk&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A key manager which manages keys persisted on disk&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_keymanager_hashicorp_vault.md&quot;&gt;hashicorp_vault&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A key manager which manages keys in HashiCorp Vault’s Transit Secret Engine&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_keymanager_kmip.md&quot;&gt;kmip&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A key manager which manages keys in a KMIP-compliant server over binary TTLV/TCP&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;KeyManager&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_keymanager_memory.md&quot;&gt;memory&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A key manager which manages unpersisted keys in memory&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;CredentialComposer&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_credentialcomposer_uniqueid.md&quot;&gt;uniqueid&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Adds the x509UniqueIdentifier attribute to workload X509-SVIDs.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_aws_iid.md&quot;&gt;aws_iid&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an AWS Instance Identity Document&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_azure_imds.md&quot;&gt;azure_imds&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using the Azure Instance Metadata Service&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_azure_msi.md&quot;&gt;azure_msi&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an Azure MSI token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_gcp_iit.md&quot;&gt;gcp_iit&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using a GCP Instance Identity Token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_jointoken.md&quot;&gt;join_token&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which validates agents attesting with server-generated join tokens&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_k8s_psat.md&quot;&gt;k8s_psat&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using a Kubernetes Projected Service Account token&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_sshpop.md&quot;&gt;sshpop&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an existing ssh certificate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_tpm_devid.md&quot;&gt;tpm_devid&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using a TPM that has been provisioned with a DevID certificate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;NodeAttestor&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_nodeattestor_x509pop.md&quot;&gt;x509pop&lt;/a&gt;&lt;/td&gt;&lt;td&gt;A node attestor which attests agent identity using an existing X.509 certificate&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_disk.md&quot;&gt;disk&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses a CA loaded from disk to sign SPIRE server intermediate certificates.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_aws_pca.md&quot;&gt;aws_pca&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses a Private Certificate Authority from AWS Certificate Manager to sign SPIRE server intermediate certificates.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_awssecret.md&quot;&gt;awssecret&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses a CA loaded from AWS SecretsManager to sign SPIRE server intermediate certificates.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_gcp_cas.md&quot;&gt;gcp_cas&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses a Private Certificate Authority from GCP Certificate Authority Service to sign SPIRE Server intermediate certificates.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_vault.md&quot;&gt;vault&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses a PKI Secret Engine from HashiCorp Vault to sign SPIRE server intermediate certificates.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_spire.md&quot;&gt;spire&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses an upstream SPIRE server in the same trust domain to obtain intermediate signing certificates for SPIRE server.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;UpstreamAuthority&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_upstreamauthority_cert_manager.md&quot;&gt;cert-manager&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Uses a referenced cert-manager Issuer to request intermediate signing certificates.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Notifier&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_notifier_gcs_bundle.md&quot;&gt;gcs_bundle&lt;/a&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Deprecated:&lt;/strong&gt; use the &lt;code&gt;gcp_cloudstorage&lt;/code&gt; BundlePublisher instead. A notifier that pushes the latest trust bundle contents into an object in Google Cloud Storage.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Notifier&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_notifier_k8sbundle.md&quot;&gt;k8sbundle&lt;/a&gt;&lt;/td&gt;&lt;td&gt;&lt;strong&gt;Deprecated:&lt;/strong&gt; use the &lt;code&gt;k8s_configmap&lt;/code&gt; BundlePublisher instead. A notifier that pushes the latest trust bundle contents into a Kubernetes ConfigMap.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;BundlePublisher&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_bundlepublisher_aws_s3.md&quot;&gt;aws_s3&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Publishes the trust bundle to an Amazon S3 bucket.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;BundlePublisher&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_bundlepublisher_gcp_cloudstorage.md&quot;&gt;gcp_cloudstorage&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Publishes the trust bundle to a Google Cloud Storage bucket.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;BundlePublisher&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_bundlepublisher_aws_rolesanywhere_trustanchor.md&quot;&gt;aws_rolesanywhere_trustanchor&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Publishes the trust bundle to an AWS IAM Roles Anywhere trust anchor.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;BundlePublisher&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_bundlepublisher_azure_blob.md&quot;&gt;azure_blob&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Publishes the trust bundle to an Azure Blob Storage account.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;BundlePublisher&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spiffe/spire/blob/v1.16.0//doc/plugin_server_bundlepublisher_k8s_configmap.md&quot;&gt;k8s_configmap&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Publishes the trust bundle to a Kubernetes ConfigMap.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h2 id=&quot;server-configuration-file&quot;&gt;Server configuration file&lt;/h2&gt;
&lt;p&gt;The following table outlines the configuration options for SPIRE server. These may be set in a top-level &lt;code&gt;server { ... }&lt;/code&gt; section of the configuration file. Most options have a corresponding CLI flag which, if set, takes precedence over values defined in the file.&lt;/p&gt;</description></item><item><title>SPIRE Telemetry Configuration</title><link>https://spiffe.io/docs/latest/deploying/telemetry_config/</link><guid>https://spiffe.io/docs/latest/deploying/telemetry_config/</guid><description>&lt;p&gt;If telemetry is desired, it may be configured by using a dedicated &lt;code&gt;telemetry { ... }&lt;/code&gt; section. The following metrics collectors are currently supported:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Prometheus&lt;/li&gt;
&lt;li&gt;Statsd&lt;/li&gt;
&lt;li&gt;DogStatsd&lt;/li&gt;
&lt;li&gt;M3&lt;/li&gt;
&lt;li&gt;In-Memory&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;You may use all, some, or none of the collectors. The following collectors support multiple declarations in the event that you want to send metrics to more than one collector:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Statsd&lt;/li&gt;
&lt;li&gt;DogStatsd&lt;/li&gt;
&lt;li&gt;M3&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;telemetry-configuration-syntax&quot;&gt;Telemetry configuration syntax&lt;/h2&gt;

























































































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Configuration&lt;/th&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;th&gt;Default&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;InMem&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;InMem&lt;/code&gt;&lt;/td&gt;&lt;td&gt;In-memory configuration&lt;/td&gt;&lt;td&gt;running&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;Prometheus&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;Prometheus&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Prometheus configuration&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;DogStatsd&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]DogStatsd&lt;/code&gt;&lt;/td&gt;&lt;td&gt;List of DogStatsd configurations&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;Statsd&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]Statsd&lt;/code&gt;&lt;/td&gt;&lt;td&gt;List of Statsd configurations&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;M3&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]M3&lt;/code&gt;&lt;/td&gt;&lt;td&gt;List of M3 configurations&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;MetricPrefix&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Prefix to add to all emitted metrics&lt;/td&gt;&lt;td&gt;spire_server/spire_agent&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;EnableTrustDomainLabel&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;bool&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Enable optional trust domain label for all metrics&lt;/td&gt;&lt;td&gt;false&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;EnableHostnameLabel&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;bool&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Enable adding hostname to labels&lt;/td&gt;&lt;td&gt;true&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;AllowedPrefixes&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A list of metric prefixes to allow, with ’.’ as the separator&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;AllowedPrefixes&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A list of metric prefixes to allow, with ’.’ as the separator&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;BlockedPrefixes&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A list of metric prefixes to block, with ’.’ as the separator&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;AllowedLabels&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A list of metric labels to allow, with ’.’ as the separator&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;BlockedLabels&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;[]string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;A list of metric labels to block, with ’.’ as the separator&lt;/td&gt;&lt;td&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;prometheus&quot;&gt;&lt;code&gt;Prometheus&lt;/code&gt;&lt;/h3&gt;

























&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Configuration&lt;/th&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;host&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Prometheus exporter listen address&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;port&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;int&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Prometheus exporter listen port&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;tls&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;object&lt;/code&gt;&lt;/td&gt;&lt;td&gt;TLS configuration for the Prometheus exporter&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h4 id=&quot;prometheustls&quot;&gt;&lt;code&gt;Prometheus.tls&lt;/code&gt;&lt;/h4&gt;



































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Configuration&lt;/th&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;cert_file&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Path to the PEM-encoded certificate for the Prometheus exporter. Must be set with &lt;code&gt;key_file&lt;/code&gt; unless &lt;code&gt;use_spire_svid&lt;/code&gt; is enabled&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;key_file&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Path to the PEM-encoded private key for the Prometheus exporter. Must be set with &lt;code&gt;cert_file&lt;/code&gt; unless &lt;code&gt;use_spire_svid&lt;/code&gt; is enabled&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;client_ca_file&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Optional path to the PEM-encoded CA bundle used to verify client certificates for mTLS. Cannot be combined with &lt;code&gt;authorized_spiffe_ids&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;use_spire_svid&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;bool&lt;/code&gt;&lt;/td&gt;&lt;td&gt;When &lt;code&gt;true&lt;/code&gt;, serve the Prometheus endpoint with the current SPIRE SVID instead of &lt;code&gt;cert_file&lt;/code&gt; and &lt;code&gt;key_file&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;authorized_spiffe_ids&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;list(string)&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Optional list of SPIFFE IDs allowed to connect to the Prometheus endpoint. Requires SPIRE trust bundles and cannot be combined with &lt;code&gt;client_ca_file&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;dogstatsd&quot;&gt;&lt;code&gt;DogStatsd&lt;/code&gt;&lt;/h3&gt;















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Configuration&lt;/th&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;address&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;DogStatsd address&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;statsd&quot;&gt;&lt;code&gt;Statsd&lt;/code&gt;&lt;/h3&gt;















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Configuration&lt;/th&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;address&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;Statsd address&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;h3 id=&quot;m3&quot;&gt;&lt;code&gt;M3&lt;/code&gt;&lt;/h3&gt;




















&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Configuration&lt;/th&gt;&lt;th&gt;Type&lt;/th&gt;&lt;th&gt;Description&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;address&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;M3 address&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;&lt;code&gt;env&lt;/code&gt;&lt;/td&gt;&lt;td&gt;&lt;code&gt;string&lt;/code&gt;&lt;/td&gt;&lt;td&gt;M3 environment, e.g. &lt;code&gt;production&lt;/code&gt;, &lt;code&gt;staging&lt;/code&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Here is a sample configuration:&lt;/p&gt;</description></item><item><title>SPIRE Use Cases</title><link>https://spiffe.io/docs/latest/spire-about/use-cases/</link><guid>https://spiffe.io/docs/latest/spire-about/use-cases/</guid><description>&lt;h1 id=&quot;authenticating-workloads-in-untrusted-networks-using-mtls&quot;&gt;Authenticating workloads in untrusted networks using mTLS&lt;/h1&gt;
&lt;p&gt;When sending messages between distributed software systems, it is common to rely on the network to determine the identity of the system that sent a message, to ensure that messages can only be received by systems that are authorized to view them, and to ensure that the message has not been seen or modified in transit by a malicious party.&lt;/p&gt;
&lt;p&gt;However, for complex distributed applications - which may span multiple networks that share many services deployed by different teams - it may be undesirable to rely on the network to protect communication. Mutual &lt;a href=&quot;https://en.wikipedia.org/wiki/Transport_Layer_Security&quot;&gt;Transport Layer Security&lt;/a&gt; (mTLS) is a well established technology that relies on asymmetric cryptography to prove the identity of the sender and recipient of a message, as well as assert that the message has not been viewed or modified in transit by a third party. It is thus useful for establishing communication in potentially untrusted networks.&lt;/p&gt;</description></item><item><title>Upgrading</title><link>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/upgrading/</link><guid>https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/upgrading/</guid><description>&lt;h1 id=&quot;chart-version-number-meaning&quot;&gt;Chart version number meaning&lt;/h1&gt;
&lt;p&gt;The chart has its own version number following the semver scheme of:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Major&lt;/code&gt;.&lt;code&gt;Minor&lt;/code&gt;.&lt;code&gt;Patch&lt;/code&gt; versioning.&lt;/p&gt;
&lt;h1 id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h1&gt;
&lt;h2 id=&quot;version-upgrades&quot;&gt;Version upgrades&lt;/h2&gt;
&lt;p&gt;We only support upgrading one Major/Minor version at a time. Version skipping isn’t supported except for patch versions.&lt;/p&gt;
&lt;p&gt;Examples:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;It’s supported to upgrade from 0.11.1 directly to 0.11.7&lt;/li&gt;
&lt;li&gt;It’s supported to upgrade from 0.11.2 to 0.12.1&lt;/li&gt;
&lt;li&gt;It’s not supported to upgrade from 0.11.0 to 0.13.0&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;additional-upgrade-steps&quot;&gt;Additional Upgrade Steps&lt;/h2&gt;
&lt;p&gt;From time to time you may need to do some upgrade steps before upgrading. We’ll only do this
during Major or Minor version changes of the chart, never a patch release.&lt;/p&gt;</description></item><item><title>Using Envoy with JWT-SVIDs</title><link>https://spiffe.io/docs/latest/microservices/envoy-jwt/readme/</link><guid>https://spiffe.io/docs/latest/microservices/envoy-jwt/readme/</guid><description>&lt;p&gt;This tutorial builds on the &lt;a href=&quot;https://github.com/spiffe/spire-tutorials/blob/main/k8s/envoy-x509&quot;&gt;SPIRE Envoy-X.509 Tutorial&lt;/a&gt; to demonstrate how to use SPIRE to perform JWT SVID authentication on a workload’s behalf instead of X.509 SVID authentication. The changes required to implement JWT SVID authentication are shown here as a delta to that tutorial, so you should run, or at least read through, the X.509 tutorial first.&lt;/p&gt;
&lt;p&gt;To illustrate JWT authentication, we add sidecars to each of the services used in the Envoy X.509 tutorial. Each sidecar acts as an &lt;a href=&quot;https://www.envoyproxy.io/docs/envoy/v1.25.1/intro/arch_overview/security/ext_authz_filter#arch-overview-ext-authz&quot;&gt;external authorization filter&lt;/a&gt; for Envoy.&lt;/p&gt;</description></item><item><title>Using Envoy with SPIRE</title><link>https://spiffe.io/docs/latest/microservices/envoy/</link><guid>https://spiffe.io/docs/latest/microservices/envoy/</guid><description>&lt;p&gt;Envoy is a popular open-source service proxy that is widely used to provide abstracted, secure, authenticated and encrypted communication between services. Envoy enjoys a rich configuration system that allows for flexible third-party interaction.&lt;/p&gt;
&lt;p&gt;One component of this configuration system is the Secret Discovery Service protocol or SDS. Envoy uses SDS to retrieve and maintain updated “secrets” from SDS providers. In the context of TLS authentication, these secrets are the TLS certificates, private keys, and trusted CA certificates. The SPIRE Agent can be configured as an SDS provider for Envoy, allowing it to directly provide Envoy with the key material it needs to provide TLS authentication. The SPIRE Agent will also take care of re-generating the short-lived keys and certificates as required.&lt;/p&gt;</description></item><item><title>Using Envoy with X.509-SVIDs</title><link>https://spiffe.io/docs/latest/microservices/envoy-x509/readme/</link><guid>https://spiffe.io/docs/latest/microservices/envoy-x509/readme/</guid><description>&lt;p&gt;This tutorial builds on the &lt;a href=&quot;/docs/latest/try/getting-started-k8s/&quot;&gt;Kubernetes Quickstart Tutorial&lt;/a&gt; to demonstrate how to configure SPIRE to provide service identity dynamically in the form of X.509 certificates that will be consumed by Envoy secret discovery service (SDS). The changes required to implement X.509 SVID authentication are shown here as a delta to that tutorial, so you should run, or at least read through, the Kubernetes Quickstart Tutorial first.&lt;/p&gt;
&lt;p&gt;To illustrate X.509 authentication, we create a simple scenario with three services. One service will be the backend that is a simple nginx instance serving static data. On the other side, we run two instances of the &lt;code&gt;Symbank&lt;/code&gt; demo banking application acting as the frontend services. The &lt;code&gt;Symbank&lt;/code&gt; frontend services send HTTP requests to the nginx backend to get the user account details.&lt;/p&gt;</description></item><item><title>Using SPIRE and OIDC to Authenticate Workloads to Retrieve Vault Secrets</title><link>https://spiffe.io/docs/latest/keyless/vault/readme/</link><guid>https://spiffe.io/docs/latest/keyless/vault/readme/</guid><description>&lt;p&gt;This tutorial builds on the &lt;a href=&quot;/spire/try/getting-started-k8s/&quot;&gt;Kubernetes Quickstart&lt;/a&gt; guide to describe how to set up OIDC Federation between a SPIRE Server and a Vault server. This will allow a SPIRE-identified workload to authenticate against a federated Vault server by presenting no more than its JWT-SVID. Using this technique the workload won’t need to authenticate itself against the Vault server using another authentication method like AppRole or Username &amp;#x26; Password.&lt;/p&gt;
&lt;p&gt;In this tutorial you will learn how to:&lt;/p&gt;</description></item><item><title>WIT-SVID</title><link>https://spiffe.io/docs/latest/spiffe-specs/wit-svid/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/wit-svid/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/WIT-SVID.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/WIT-SVID.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Incubating&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity document standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;table-of-contents&quot;&gt;Table of Contents&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;#1-introduction&quot;&gt;1. Introduction&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#2-jose-header&quot;&gt;2. JOSE Header&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;#21-key-id---kid&quot;&gt;2.1. Key ID - &lt;code&gt;kid&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#22-type---typ&quot;&gt;2.2. Type - &lt;code&gt;typ&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#23-algorithm---alg&quot;&gt;2.3. Algorithm - &lt;code&gt;alg&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#24-additional-header-parameters&quot;&gt;2.4. Additional Header Parameters&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#3-claims&quot;&gt;3. Claims&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;#31-subject---sub&quot;&gt;3.1. Subject - &lt;code&gt;sub&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#32-confirmation---cnf&quot;&gt;3.2. Confirmation - &lt;code&gt;cnf&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#33-jwt-id---jti&quot;&gt;3.3. JWT ID - &lt;code&gt;jti&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#34-expiry---exp&quot;&gt;3.4. Expiry - &lt;code&gt;exp&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#35-not-before---nbf&quot;&gt;3.5. Not Before - &lt;code&gt;nbf&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#36-issued-at---iat&quot;&gt;3.6. Issued At - &lt;code&gt;iat&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#37-issuer---iss&quot;&gt;3.7. Issuer - &lt;code&gt;iss&lt;/code&gt;&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#38-additional-claims&quot;&gt;3.8. Additional Claims&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#4-token-issuance-and-validation&quot;&gt;4. Token Issuance and Validation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#5-token-presentation&quot;&gt;5. Token Presentation&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#6-representation-in-the-spiffe-bundle&quot;&gt;6. Representation in the SPIFFE Bundle&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;#61-publishing-spiffe-bundle-elements&quot;&gt;6.1 Publishing SPIFFE Bundle Elements&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#62-consuming-spiffe-bundle-elements&quot;&gt;6.2 Consuming SPIFFE Bundle Elements&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#7-security-considerations&quot;&gt;7. Security Considerations&lt;/a&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;#71-mandatory-proof-of-possession&quot;&gt;7.1 Mandatory Proof of Possession&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#72-proof-of-possession-and-mitigation-of-tampering-and-replay&quot;&gt;7.2 Proof of Possession and Mitigation of Tampering and Replay&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#73-transport-security&quot;&gt;7.3 Transport Security&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#appendix-a-example-wit-svid&quot;&gt;Appendix A. Example WIT-SVID&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#appendix-b-comparing-wimse-wit-with-spiffe-wit-svid&quot;&gt;Appendix B. Comparing WIMSE WIT with SPIFFE WIT-SVID&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#appendix-c-comparing-the-jwt-svid-and-wit-svid&quot;&gt;Appendix C. Comparing the JWT-SVID and WIT-SVID&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;#appendix-d-comparing-the-x509-svid-and-wit-svid&quot;&gt;Appendix D. Comparing the X509-SVID and WIT-SVID&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;1-introduction&quot;&gt;1. Introduction&lt;/h2&gt;
&lt;p&gt;The Workload Identity Token (WIT) is a token format specified by the IETF WIMSE working group in the &lt;a href=&quot;https://datatracker.ietf.org/doc/draft-ietf-wimse-workload-creds/&quot;&gt;WIMSE Workload Credentials&lt;/a&gt; document. The WIT binds a public key to the identity of a workload.&lt;/p&gt;</description></item><item><title>Working with SVIDs</title><link>https://spiffe.io/docs/latest/deploying/svids/</link><guid>https://spiffe.io/docs/latest/deploying/svids/</guid><description>&lt;p&gt;A SPIFFE-compatible identity provider such as SPIRE will expose &lt;a href=&quot;/docs/latest/spiffe/concepts/#spiffe-verifiable-identity-document-svid&quot;&gt;SPIFFE Verifiable Identity Documents&lt;/a&gt; (SVIDs) via the &lt;a href=&quot;/docs/latest/spiffe/concepts/#spiffe-workload-api&quot;&gt;SPIFFE Workload API&lt;/a&gt;. Workloads can use SVIDs retrieved from this API to verify the provenance of a message or to establish mutual TLS secured channels between two workloads.&lt;/p&gt;
&lt;h1 id=&quot;interacting-with-the-workload-api&quot;&gt;Interacting with the Workload API&lt;/h1&gt;
&lt;p&gt;Developers coding a new workload that needs to interact with SPIFFE can interact directly with the SPIFFE Workload API to:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Retrieve the workload’s identity, described as a SPIFFE ID such as &lt;code&gt;spiffe://prod.acme.com/billing/api&lt;/code&gt;&lt;/p&gt;</description></item><item><title>X509-SVID</title><link>https://spiffe.io/docs/latest/spiffe-specs/x509-svid/</link><guid>https://spiffe.io/docs/latest/spiffe-specs/x509-svid/</guid><description>&lt;aside aria-label=&quot;Note&quot; class=&quot;starlight-aside starlight-aside--note&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 11a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0v-4a1 1 0 0 0-1-1Zm.38-3.92a1 1 0 0 0-.76 0 1 1 0 0 0-.33.21 1.15 1.15 0 0 0-.21.33 1 1 0 0 0 .21 1.09c.097.088.209.16.33.21A1 1 0 0 0 13 8a1.05 1.05 0 0 0-.29-.71 1 1 0 0 0-.33-.21ZM12 2a10 10 0 1 0 0 20 10 10 0 0 0 0-20Zm0 18a8 8 0 1 1 0-16.001A8 8 0 0 1 12 20Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Note&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;This document is part of the SPIFFE standard. The canonical version can be found at &lt;a href=&quot;https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md&quot;&gt;https://github.com/spiffe/spiffe/blob/main/standards/X509-SVID.md&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Stability: Stable&lt;/strong&gt; - see &lt;a href=&quot;/docs/latest/spiffe-specs/stability/&quot;&gt;STABILITY.md&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h2 id=&quot;status-of-this-memo&quot;&gt;Status of this Memo&lt;/h2&gt;
&lt;p&gt;This document specifies an identity document standard for the internet community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited.&lt;/p&gt;
&lt;h2 id=&quot;abstract&quot;&gt;Abstract&lt;/h2&gt;
&lt;p&gt;The SPIFFE standard provides a specification for a framework capable of bootstrapping and issuing identity to services across heterogeneous environments and organizational boundaries. It defines an identity document known as the SPIFFE Verifiable Identity Document (SVID).&lt;/p&gt;</description></item></channel></rss>