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

✨ Masking sensitive information in lang/emb requests #258

Open
roma-glushko opened this issue May 13, 2024 · 1 comment
Open

✨ Masking sensitive information in lang/emb requests #258

roma-glushko opened this issue May 13, 2024 · 1 comment
Labels
area:config gep:required model:embedding model:language type:epic A high level issue that usually consist of smaller tasks and corresponds to some functionality

Comments

@roma-glushko
Copy link
Member

roma-glushko commented May 13, 2024

Requirements

  • Mask PHI, PII, and PCI information in lang/embedding requests
  • Unmask all masked values before returning LLM chat responses back
  • Unmask masked tokens in streaming chat requests
  • Allow to enable the functionality per router
  • consider using the middleware-like approach to the architecture and that there may be more pre/post processing logic to include in the future (like ✨ [Cost] Incoming Token Compression #259)

Use Case

  • I want to be able to mask sensitive information (PHI, PII, and PCI) before sending it to LLM providers, so I'm not leaking it. If model returns masked placeholders, I want it to be unmasked automatically and seamlessly
@roma-glushko roma-glushko added area:config gep:required model:language model:embedding type:epic A high level issue that usually consist of smaller tasks and corresponds to some functionality labels May 13, 2024
@roma-glushko
Copy link
Member Author

cc @mkrueger12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:config gep:required model:embedding model:language type:epic A high level issue that usually consist of smaller tasks and corresponds to some functionality
Projects
Status: Icebox
Development

No branches or pull requests

1 participant