Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: SPIFFE unique workload identifiers with TPM support #2927

Open
Tracked by #2129
bencorrado opened this issue Oct 8, 2024 · 0 comments
Open
Tracked by #2129

feat: SPIFFE unique workload identifiers with TPM support #2927

bencorrado opened this issue Oct 8, 2024 · 0 comments
Labels
enhancement New feature or request triage Add this label to issues that should be triaged and prioretized in the next planning call

Comments

@bencorrado
Copy link
Contributor

bencorrado commented Oct 8, 2024

Is your feature request related to a problem? Please describe.
Being able to unique identify workloads on the network and tie to a specific trust domain and attest to specifically which node they are running on linking back to the TPM using Keylime. This will allow a high level of certainty that as to where (which Karios device) services are being run.

https://spiffe.io/docs/latest/spiffe-about/overview/

Describe the solution you'd like
I would like to implement SPIFFE using SPIRE support into Kairos.

SPIRE supports Keylime with this plugin. Keylime is already planned in #1115

Keylime support to expose the right APIs on the right interfaces and configure any firewall settings will be important.

It seems like a bundle could be created added to #592 similar to:
https://spiffe.io/docs/latest/spire-helm-charts-hardened-about/ or https://spiffe.io/docs/latest/deploying/install-agents/

We should dive more into a deeper integration with the standard packaging as well:
https://spiffe.io/docs/latest/deploying/registering/

Describe alternatives you've considered
This could be implemented without Keylime support

Depends on: #1115

@bencorrado bencorrado added enhancement New feature or request triage Add this label to issues that should be triaged and prioretized in the next planning call labels Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage Add this label to issues that should be triaged and prioretized in the next planning call
Projects
Status: No status
Development

No branches or pull requests

1 participant