The presentation discusses the challenges of locking down Providence metadata fields in Tecton and proposes a solution using Spiffy Inspire for strong attestation and verification.
- Tecton users have direct access to objects and metadata fields, making it difficult to lock down Providence metadata fields
- Kubernetes cluster classes are managed by different entities, making it challenging to restrict access to metadata fields
- The Task Run object becomes a main attack point for malicious actors
- The proposed solution involves creating a trusted computing base and restricting access to metadata fields
- Spiffy Inspire provides strong attestation and verification for the trusted computing base
- Future work includes extending the solution to other custom resources and validating artifacts passed between tasks