-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Filter sensitive data from the logs #5036
Comments
simianhacker
added a commit
to simianhacker/kibana
that referenced
this issue
Sep 25, 2015
- Closes elastic#5036 - Add `applyFilterToKey()` - Add test for `applyFilterToKey()` - Add `filter` attribute to config for reporters - Add `this.filter` method to `LogFormat` class
Would it be possible for the filtered behavior to be the default, and require configuration/option application? |
@GlenRSmith The defaults implemented in #5038 automatically remove any |
These patches never made it into 4.2.0 so the logging of sensitive data is still a problem. |
It will go into 4.3 and possibly 4.2.1 |
epixa
pushed a commit
to epixa/kibana
that referenced
this issue
Nov 5, 2015
- Closes elastic#5036 - Add `applyFilterToKey()` - Add test for `applyFilterToKey()` - Add `filter` attribute to config for reporters - Add `this.filter` method to `LogFormat` class
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should make an effort to filter sensitive data from the logs. An good example would be to censor
req.headers.authorization
which would change this log entry:to this
The text was updated successfully, but these errors were encountered: