Add rule catalog documentation#59
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9c11b88d53
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| This rule identifies concentrated sudo command activity by one user. It does not decide whether the activity is malicious, authorized maintenance, incident response, package management, service repair, or a scripted administrative task. | ||
|
|
||
| The finding is strongest when reviewed with session context, change windows, host ownership, and the command text preserved in the report. |
There was a problem hiding this comment.
Remove unsupported claim that reports preserve sudo commands
For sudo-burst findings, the report artifacts only render the count/window/summary and do not include the raw Event::message or sudo COMMAND= value in Markdown, JSON, or CSV. In contexts where reviewers follow this catalog and expect the command text to be available in the report, this will misdirect triage unless they return to the original log, so the documentation should not claim that the command text is preserved there.
Useful? React with 👍 / 👎.
Summary
Validation