Document all fields used in auditd dashboards #3962
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
To allow the dashboards to load all fields used in the dashboards need to be in the Kibana index pattern. I also change pid, ppid, item, and item to just be keywords. There wasn’t really a good reason reason for these to be stored as numbers and sometime in the events these were set to characters like “?”.
dedemorton
reviewed
Apr 7, 2017
filebeat/docs/fields.asciidoc
Outdated
| The item field indicates which item out of the total number of items. This number is zero-based; a value of 0 means it is the first item. | ||
|
|
||
|
|
||
| [float] | ||
| === auditd.log.a0 | ||
|
|
||
| This first argument to the system call. |
There was a problem hiding this comment.
Should this say, "The first argument..."?
There was a problem hiding this comment.
Yep, will fix them all. Thanks
dedemorton
reviewed
Apr 7, 2017
filebeat/docs/fields.asciidoc
Outdated
| [float] | ||
| === auditd.log.res | ||
|
|
||
| This result of the system call (success or failure). |
There was a problem hiding this comment.
Should this say, "The result of..."
dedemorton
reviewed
Apr 7, 2017
| description: > | ||
| The item field indicates which item out of the total number of items. | ||
| This number is zero-based; a value of 0 means it is the first item. | ||
| - name: a0 | ||
| description: > | ||
| This first argument to the system call. |
dedemorton
reviewed
Apr 7, 2017
| This first argument to the system call. | ||
| - name: res | ||
| description: > | ||
| This result of the system call (success or failure). |
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this pull request
Apr 10, 2017
… (elastic#3941) (elastic#3962) The PR adds an auditd module for parsing logs from the auditd daemon. There is a sample dashboard for viewing this data. Features - Parses audit event type, unix epoch time, audit event counter, and the arbitrary key/value pairs that follow. - Applies geoip lookup to the `auditd.log.addr` field which is present for some remote login events. - Decodes hex encoded ascii values that are sometimes used for the `auditd.log.exe` and `auditd.log.cmd` fields. - Remove key/value pairs where the value is `?`. Missing Features - Decoder for `auditd.log.saddr` field present in SOCKADDR audit events. A recipe is described [here](https://unix.stackexchange.com/questions/102926/how-to-interpret-the-saddr-field-of-an-audit-log) and could probably be ported to painless. Sample value: `type=SOCKADDR msg=audit(1481078693.491:873): saddr=01002F7661722F72756E2F6E7363642F736F636B657400008983B330BE7F0000000000000000000070830130BE7F000004000000000000001B00000000000000D128B7ED000000008B8BB330BE7F00003B00000000000000403E4BF7FD7F0000447F0130BE7F000080150230BE7F`
tsg
pushed a commit
that referenced
this pull request
Apr 11, 2017
) (#3975) The PR adds an auditd module for parsing logs from the auditd daemon. There is a sample dashboard for viewing this data. Features - Parses audit event type, unix epoch time, audit event counter, and the arbitrary key/value pairs that follow. - Applies geoip lookup to the `auditd.log.addr` field which is present for some remote login events. - Decodes hex encoded ascii values that are sometimes used for the `auditd.log.exe` and `auditd.log.cmd` fields. - Remove key/value pairs where the value is `?`. Missing Features - Decoder for `auditd.log.saddr` field present in SOCKADDR audit events. A recipe is described [here](https://unix.stackexchange.com/questions/102926/how-to-interpret-the-saddr-field-of-an-audit-log) and could probably be ported to painless. Sample value: `type=SOCKADDR msg=audit(1481078693.491:873): saddr=01002F7661722F72756E2F6E7363642F736F636B657400008983B330BE7F0000000000000000000070830130BE7F000004000000000000001B00000000000000D128B7ED000000008B8BB330BE7F00003B00000000000000403E4BF7FD7F0000447F0130BE7F000080150230BE7F`
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.
To allow the dashboards to load all fields used in the dashboards need to be in the Kibana index pattern.
I also changed pid, ppid, item, and item to just be keywords. There wasn’t really a good reason reason for these to be stored as numbers and sometimes in the events these were set to characters like “?”.