-
Notifications
You must be signed in to change notification settings - Fork 614
[Rule Tuning] Linux DR Tuning - 9 #5508
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
base: main
Are you sure you want to change the base?
Conversation
Rule: Tuning - GuidelinesThese guidelines serve as a reminder set of considerations when tuning an existing rule. Documentation and Context
Rule Metadata Checks
Testing and Validation
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
|
@copilot Summarize this entire pull request. Consider all commits, file diffs, and conversations. Overwrite the main summary comment with the summary you created. Also, use these instructions: “Generate a PR summary for reviewers. Include: Why (problem), What changed (bullets), Behavioral impact, Risk/edge cases, How to test, and Notes for rollout. Keep it concise and accurate; if unsure, say so.” |
|
⛔️ Test failed Results
|
|
⛔️ Test failed Results
|
PR 5508 Reviewer Summary
Why
This PR updates and refines a broad set of Linux persistence detection rules to:
What Changed
Severity & Risk Score Adjustments
severityand/orrisk_scorelowered (e.g., from "medium" to "low", 47→21) to reduce alert fatigue.persistence_bpf_probe_write_user,persistence_linux_backdoor_user_creation) had severity/risk increased to highlight criticality.Expanded Exclusions & Pattern Matching
:,in) to pattern-based (like,like~) for broader, more accurate detection..dpkg-new,.source), and benign system behaviors.Query & Logic Improvements
Metadata & Integration Updates
Triage/Investigation Guide Enhancements
notesection with detailed, AI-generated triage, false positive analysis, and response/remediation steps.Rule-Specific Notables
Behavioral Impact
Risks / Edge Cases
like,like~) may have unforeseen effects on rule triggering in edge cases.Rollout Notes