think the phrase “running in the TEE” is the idiomatic way to describe a program running on the main CPU
In the Confidentiality/Integrity/Availability triangle, a secondary process running in another operating system gives you integrity, but not confidentiality
They lay out all the protections they have in place to ensure private prompt execution. The TEE is used to validate the integrity of the binary, and they use other protections like E2EE, SEV-SNP on the coordinator, MacOS security protections (hardened runtime, SIP, kernel protections, etc), plus (from what i can tell an optional enrollment from providers) in Apple’s MDM which makes Apple verify the integrity of the system.
I very much disagree with
In the Confidentiality/Integrity/Availability triangle, a secondary process running in another operating system gives you integrity, but not confidentiality
You both should just read the docs
https://docs.darkbloom.dev/security/overview
They lay out all the protections they have in place to ensure private prompt execution. The TEE is used to validate the integrity of the binary, and they use other protections like E2EE, SEV-SNP on the coordinator, MacOS security protections (hardened runtime, SIP, kernel protections, etc), plus (from what i can tell an optional enrollment from providers) in Apple’s MDM which makes Apple verify the integrity of the system.
That’s literally what I said, and why I disagreed with the other poster saying it ran in the TEE
Whether the protections of the main binary are sufficient I’ve made no comment on