-
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
Add correlation section to audit logging docs #123757
Conversation
f3d7b80
to
31a5dbf
Compare
31a5dbf
to
ad6ef48
Compare
💚 Build Succeeded
History
To update your PR or re-run it, just comment with: |
Pinging @elastic/kibana-security (Team:Security) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
{"event":{"action":"http_request","category":["web"],"outcome":"unknown"},"http":{"request":{"method":"post"}},"url":{"domain":"localhost","path":"/api/alerting/rule","port":5601,"scheme":"https"},"user":{"name":"thom","roles":["superuser"]},"kibana":{"space_id":"default","session_id":"3dHCZRB..."},"@timestamp":"2022-01-25T13:05:34.449-05:00","message":"User is requesting [/api/alerting/rule] endpoint","trace":{"id":"e300e06..."}} | ||
{"event":{"action":"space_get","category":["database"],"type":["access"],"outcome":"success"},"kibana":{"space_id":"default","session_id":"3dHCZRB...","saved_object":{"type":"space","id":"default"}},"user":{"name":"thom","roles":["superuser"]},"@timestamp":"2022-01-25T13:05:34.454-05:00","message":"User has accessed space [id=default]","trace":{"id":"e300e06..."}} | ||
{"event":{"action":"connector_get","category":["database"],"type":["access"],"outcome":"success"},"kibana":{"space_id":"default","session_id":"3dHCZRB...","saved_object":{"type":"action","id":"5e3b1ae..."}},"user":{"name":"thom","roles":["superuser"]},"@timestamp":"2022-01-25T13:05:34.948-05:00","message":"User has accessed connector [id=5e3b1ae...]","trace":{"id":"e300e06..."}} | ||
{"event":{"action":"connector_get","category":["database"],"type":["access"],"outcome":"success"},"kibana":{"space_id":"default","session_id":"3dHCZRB...","saved_object":{"type":"action","id":"5e3b1ae..."}},"user":{"name":"thom","roles":["superuser"]},"@timestamp":"2022-01-25T13:05:34.956-05:00","message":"User has accessed connector [id=5e3b1ae...]","trace":{"id":"e300e06..."}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of scope for this PR, but do you know why we are accessing the same connector twice? That feels like a bug, or at the very least unnecessary overhead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great minds think alike! I opened a GH issue for this yesterday: #123753
It's not a bug but it is unnecessary overhead IMO.
(cherry picked from commit 6e4c311)
(cherry picked from commit 6e4c311)
…elastic#123830) * Add correlation section to audit logging docs (elastic#123757) (cherry picked from commit 6e4c311) * "Correlating audit events" -> "Correlating ECS audit events" (cherry picked from commit 8241279)
…elastic#123830) * Add correlation section to audit logging docs (elastic#123757) (cherry picked from commit 6e4c311) * "Correlating audit events" -> "Correlating ECS audit events" (cherry picked from commit 8241279)
…elastic#123830) * Add correlation section to audit logging docs (elastic#123757) (cherry picked from commit 6e4c311) * "Correlating audit events" -> "Correlating ECS audit events" (cherry picked from commit 8241279)
…elastic#123830) * Add correlation section to audit logging docs (elastic#123757) (cherry picked from commit 6e4c311) * "Correlating audit events" -> "Correlating ECS audit events" (cherry picked from commit 8241279)
…elastic#123830) * Add correlation section to audit logging docs (elastic#123757) (cherry picked from commit 6e4c311) * "Correlating audit events" -> "Correlating ECS audit events" (cherry picked from commit 8241279)
…elastic#123830) * Add correlation section to audit logging docs (elastic#123757) (cherry picked from commit 6e4c311) * "Correlating audit events" -> "Correlating ECS audit events" (cherry picked from commit 8241279)
Related to: #123737
This PR updates the audit logging docs to include more details about how audit events can be correlated.
Docs preview link: https://kibana_123757.docs-preview.app.elstc.co/diff
Note: the backports to 7.17 and earlier will need to have the "Correlating audit events" section header changed to "Correlating ECS audit events"