Trusted Attestation Controller

Trusted Attestation Controller is an archived, no-longer-maintained Intel Kubernetes controller that deploys and manages TCS (Trusted Compute Services), an…

  • Infrastructure
  • Security
  • Tools & Utilities
Trusted Attestation Controller is an archived, no-longer-maintained Intel Kubernetes controller that deploys and manages TCS (Trusted Compute Services), an in-cluster remote attestation service that verifies the hardware and software attestation evidence of enclaves. It is aimed at Kubernetes administrators who want enclave attestation inside their own cluster. Intel has ceased all development and no longer accepts patches, so you will need to fork and maintain the project yourself to keep running it.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

9/100 Low

Maintained
0GitHub repository is archived
Popular
102 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
2
Open issues
4
Last commit
2025-04-03
License
Apache-2.0
Activity
stale

Checked 3 days ago - source: GitHub (intel/trusted-attestation-controller)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the Trusted Types library If you are running this in Node.js (a JavaScript runtime), run npm install trusted-types so the code can create Trusted Types policies. Without it, anything that expects trustedTypes will fail before the app can start. source
  • Allow the policy names you use Add the policy names your app creates to the page's Content-Security-Policy (a browser header that controls what the page may run), such as trusted-types foo bar. If a name is missing, the browser blocks policy creation and you will see a violation. source
  • Load the API-only polyfill if needed If the browser you test in does not support Trusted Types, load the API-only polyfill script shown in the README so policy creation can still run. This gives you a fallback, but it does not enforce the same page security checks. source
  • Provision TCS issuer certificate and install from source Before deploying, provision the TCS issuer root certificate and private key, then install from source code as described in the repository README. source
  • Before installing Intel no longer maintains this project; fork the repository if you need ongoing updates. source
  • Maintenance Intel states this project is no longer under active management; fork it if you need continued maintenance. source

Fetched 2 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I build and push the controller image from source?

Clone the repository, set the REGISTRY make variable to a registry reachable from the Kubernetes cluster, and run make docker-build docker-push.

What certificate material must be provisioned before deployment?

Provision the Trusted Certificate Service issuer root certificate and private key before deploying the controller.

Does the controller validate the SGX quote itself?

No. It proxies the QuoteAttestation request over a UNIX domain socket to the plugin container running in the same Pod.

How can an external key server integrate with the controller?

A key server can plug into the controller by implementing the controller's API. The controller acts as a proxy between the Trusted Certificate Service and the key server.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads