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

Small explanation about what this library is used for #61

Open
konrazem opened this issue Jul 30, 2021 · 3 comments
Open

Small explanation about what this library is used for #61

konrazem opened this issue Jul 30, 2021 · 3 comments

Comments

@konrazem
Copy link

It may be silly to ask but it would be nice if you can give a small explanation about the usage of this library. Why should I use it?
I guess it is related to PII. 😊

@moimikey
Copy link

moimikey commented Sep 7, 2021

if you log any kind of PII, you wouldn't want social security numbers and credit cards to sit in your logs. this would break PCI/DSS compliance for example.

@konrazem
Copy link
Author

konrazem commented Sep 8, 2021

Thank you @moimikey for the answer. What I meant was to add such a section in README and explain where those logs can be shown and what can be covered. Not everybody is aware of logging systems like Sentry or Elastic. I think this is the purpose, to not store such information, not only to not log it? Where is the place I need to hide it and when? What can I hide with this package?

@mattwelke
Copy link

Depends on peoples' use cases. We're using this to prevent data from entering our system at all. That will cause any logging we do or data storage we do after the data passes the "redact" step we're building to be considered clean (or at least, as clean as it could be - if people encode their credit card numbers in base64, we can't help them).

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

3 participants