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

Should we have an allowlist for kases? #332

Closed
elizabethhealy opened this issue Aug 23, 2024 · 1 comment
Closed

Should we have an allowlist for kases? #332

elizabethhealy opened this issue Aug 23, 2024 · 1 comment

Comments

@elizabethhealy
Copy link
Member

Allowlists protect against malicious files -- someone could edit the KAO in the manifest to point to a malicious kas url. The sdk would pass an access token to that url that could possibly be used maliciously to decrypt tdfs.

Allowlists require the client/pep to know and provide all possible kases on initialization -- With key splits this can get tedious as there could be many kases and possibly kases that are unknown/hidden to the user.

@jentfoo
Copy link
Contributor

jentfoo commented Oct 14, 2024

Moving risk discussion to Jira: https://virtru.atlassian.net/browse/VULN-35

@jentfoo jentfoo closed this as completed Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants