You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally it is about things running within kubernetes, but I think it's worth to share - maybe this idea can somehow be adapted for hardening constellation:
We can now assert two statements are true, our agent runs:
Therefore, you already can prove that the VM is located in a specific AWS region. You cannot bind the name of the EC2 instance to the attestation but you have a better TCB since you don't have to reply on AWS' IMDS API.
Does this already has the security properties you need? It would be great to have a clear picture of your requirements.
Also, with Constellation being a Kubernetes distribution pinning against concrete VM names sounds counter intuitive at first since e.g. on a Constellation upgrade all the nodes are replaced.
Use case
Originally it is about things running within kubernetes, but I think it's worth to share - maybe this idea can somehow be adapted for hardening constellation:
https://control-plane.io/posts/spiffe-confidential-computing-august-2023/
spiffe intros:
https://spiffe.io/
https://github.com/spiffe/spire
https://control-plane.io/posts/spiffe-keystone-of-cloud-native/
and the spiffe plugin:
RFC: SEV SNP Node Attestation Plugin
spiffe/spire#4469
Describe your solution
No response
Would you be willing to implement this feature?
The text was updated successfully, but these errors were encountered: