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

[RFC][Proposal] : Plugin API for provisioning CA secrets from external PKIs/Key servers #23

Open
avalluri opened this issue Mar 15, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@avalluri
Copy link
Contributor

Currently, for CA provisiong (non selfsign case) the TCS is instantiate a QutoeAttestation CR with the SGX quote details and, depends on an attestation controller to reconcile the CR and provision the issuer CA secrets to the enclave. Attestation controller uses the configured key server plugin(s) to validate the quote and fetching the encrypted secret from the key server. There are a few caveats in this design:

  • The TCS enclave quote exposed in the QuoteAttestation CR can be read or altered by som maliciaou application which has the appropriate permission. This could happen in a cluster where access QuoteAttestation CR is not protected by the appropriate RBAC rules.
  • Some malicious enclave application initiates the attestation request with it's own quote and public-key, and could steal the CA secrets.
  • Unnecessary additional Kubernetes instance with sensitive data (quote), which could be avoided.

Instead, I would like to propose that , the TCS itself provides a gRPC plugin API for attestation and secret provisioning. Key severs can integrated by implementing this API. And the plugin has to run as sidecar to TCS container and exposes the plugin service over UNIX domain socket. So in this case the quote is shared in secure channel to the plugin.

@avalluri avalluri added the enhancement New feature or request label Mar 15, 2022
@avalluri
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant