mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-06-13 14:44:58 +03:00
mukul975
de282538ae
- implementing-vulnerability-management-with-greenbone: python-gvm GMP API, scan task creation, XML report parsing - detecting-email-account-compromise: Microsoft Graph inbox rules, impossible travel detection, OAuth grant analysis - performing-threat-intelligence-sharing-with-misp: PyMISP event creation, attribute management, sharing validation - analyzing-cobaltstrike-malleable-c2-profiles: dissect.cobaltstrike C2Profile parsing, Suricata rule generation - hunting-for-registry-run-key-persistence: Sysmon Event 13 analysis, T1547.001 detection, Sigma rule generation
1.9 KiB
1.9 KiB
name, description, domain, subdomain, tags, version, author, license
| name | description | domain | subdomain | tags | version | author | license | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| implementing-siem-use-case-tuning | Tune SIEM detection rules to reduce false positives by analyzing alert volumes, creating whitelists, adjusting thresholds, and measuring detection efficacy metrics in Splunk and Elastic | cybersecurity | security-operations |
|
1.0 | mahipal | Apache-2.0 |
Implementing SIEM Use Case Tuning
Overview
SIEM use case tuning reduces alert fatigue by systematically analyzing detection rules for false positive rates, adjusting thresholds based on environmental baselines, creating context-aware whitelists, and measuring detection efficacy through precision/recall metrics. This skill covers tuning workflows for Splunk correlation searches and Elastic detection rules, including statistical baselining, exclusion list management, and alert-to-incident conversion tracking.
Prerequisites
- Splunk Enterprise/Cloud with ES or Elastic SIEM with detection rules enabled
- Historical alert data (minimum 30 days) for baseline analysis
- Python 3.8+ with
requestslibrary - SIEM admin credentials or API tokens
Steps
- Export current alert volumes per detection rule from SIEM
- Calculate false positive rate per rule using analyst disposition data
- Identify top noise-generating rules by volume and FP rate
- Build environmental baselines for thresholds (e.g., login counts, process spawns)
- Create whitelist entries for known-good entities (service accounts, scanners)
- Adjust rule thresholds using statistical analysis (mean + N standard deviations)
- Measure tuning impact via before/after precision and alert-to-incident ratio
Expected Output
JSON report with per-rule tuning recommendations including current FP rate, suggested threshold adjustments, whitelist entries, and projected alert reduction percentages.