Journald Audit Logs Masking Documentation #6748
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
theopolis
approved these changes
Nov 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds additional notices to the osquery documentation to warn users about the impact on journald audit logs and how to mask those logs from entering the systemd journald if needed.
This problem has been discussed on the following thread in the Osquery slack channel and @theopolis has recommended to add this to the documentation.
Idea is, by default, systemd journald will collect the audit logs generated by the kernel auditing (something that osquery enables). On busy boxes, we saw that the lack of mask on those logs can greatly affect the performance on the box - for example considerably increasing the disk write operations that can reach limits like the burst allowance ones enforced on AWS so it is really recommended to enable this masking on Linux installations specially when event tables are enabled.
Please let me know if there is any additional info required.