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

TEEs in Non Public DCs #34

Closed
thegreatfatzby opened this issue Jun 6, 2023 · 1 comment
Closed

TEEs in Non Public DCs #34

thegreatfatzby opened this issue Jun 6, 2023 · 1 comment
Assignees
Labels

Comments

@thegreatfatzby
Copy link
Contributor

This was one of my questions originally in issue #29 , but after some internal discussion I wanted to be more specific and dig in on this one in particular.

TEEs
I am no security expert, so if there's something very obvious here than apologies, but has any consideration been given to TEEs running in non-public-cloud environments but providing the necessary constraints, attestations, etc, through some combination of technical and audit requirements? I ask because one of the twix-inesses I see here is that Ad Techs (at least the one I work for) will likely continue to have to support some set of existing use cases outside of a Fledge/Parakeet context, and those use cases are of size anywhere between non-trivial and quite substantial. Having to setup a TEE inside of a non-public-dc with some set of even relatively "intrusive" requirements could be preferable to forcing network and system topologies.

@kevinkiklee
Copy link
Collaborator

This issue has been migrated to the new WICG/protected-auction-services-discussion repository.

Please continue the discussion in the migrated issue here: WICG/protected-auction-services-discussion#14

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

No branches or pull requests

4 participants