Idea: Encrypt incoming data by default
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reviewing the Tokenizer HTTP proxy and the proposed Cloudflare Rules or Workers placement in front of it. Define the inbound and outbound encryption and substitution boundaries, including the sensitive-data and destination examples in the issue. Done would require an agreed implementation scope and security design, but no files or tests are identified here.
Written by the indexing model from the issue text.
Description
Feel free to close this, I just thought this could be a fun project for anyone interested in playing around with Tokenizer.
Goal: Ensure your server cannot hold any sensitive data by automatically encrypting incoming fields in requests (eg credit card data).
How:
- Inbound: Encrypt with Tokenizer public key using Cloudflare Rules and/or Workers (or any other provider that you can place in front of all your traffic)
- Your backend just gets the tokenized value substituted inside the request body
- Outbound: Send data though Tokenizer, values encrypted by default will be replaced in the request to your destination (eg Stripe)
Most of the work here seems unrelated to this project: configuring encryption and substitutions in the provider of your choice. I think this project is interesting bc it makes Tokenizer a replacement for a service like VGS https://www.verygoodsecurity.com/platform.
Any ideas on how to improve this or what to watch out for is someone wants to implement this?
- Dominant language
- Go
- Stars
- 494
- Forks
- 20
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from superfly/tokenizer
-
Support for MITM Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in superfly/tokenizer
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100