mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-08-03 17:30:19 +03:00
Mahipal
2fb6a9faff
Each rewritten description now states both what the skill does (concrete capability, named tools/artifacts) and an explicit when-to-use trigger, improving agent discovery/activation. Grounded in each skill's own body; changes confined to the `description` field only (bodies and all other frontmatter untouched). Produced by a gated audit->rewrite->recheck loop (548 -> 0 flagged) with a sampled anti-invention check (0 ungrounded). Schema: 817/817 pass. Framework-ID gate: 0 defects.
69 lines
2.6 KiB
Markdown
69 lines
2.6 KiB
Markdown
---
|
|
name: implementing-siem-use-case-tuning
|
|
description: Tune SIEM detection rules in Splunk and Elastic to reduce false positives
|
|
by analyzing alert volumes, creating context-aware exclusion lists, adjusting
|
|
thresholds against environmental baselines, and measuring precision/recall efficacy
|
|
metrics. Use when a SOC is drowning in noisy alerts and needs to tune correlation
|
|
searches or detection rules, or when measuring and reporting alert-to-incident
|
|
conversion rates.
|
|
domain: cybersecurity
|
|
subdomain: security-operations
|
|
tags:
|
|
- siem
|
|
- detection-engineering
|
|
- false-positive-reduction
|
|
- splunk
|
|
- elastic
|
|
- alert-tuning
|
|
- soc
|
|
version: '1.0'
|
|
author: mahipal
|
|
license: Apache-2.0
|
|
nist_csf:
|
|
- DE.CM-01
|
|
- RS.MA-01
|
|
- GV.OV-01
|
|
- DE.AE-02
|
|
mitre_attack:
|
|
- T1078
|
|
- T1190
|
|
- T1059
|
|
- T1685.002
|
|
- T1685.005
|
|
---
|
|
|
|
# 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.
|
|
|
|
|
|
## When to Use
|
|
|
|
- When deploying or configuring implementing siem use case tuning capabilities in your environment
|
|
- When establishing security controls aligned to compliance requirements
|
|
- When building or improving security architecture for this domain
|
|
- When conducting security assessments that require this implementation
|
|
|
|
## 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 `requests` library
|
|
- SIEM admin credentials or API tokens
|
|
|
|
## Steps
|
|
|
|
1. Export current alert volumes per detection rule from SIEM
|
|
2. Calculate false positive rate per rule using analyst disposition data
|
|
3. Identify top noise-generating rules by volume and FP rate
|
|
4. Build environmental baselines for thresholds (e.g., login counts, process spawns)
|
|
5. Create whitelist entries for known-good entities (service accounts, scanners)
|
|
6. Adjust rule thresholds using statistical analysis (mean + N standard deviations)
|
|
7. 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.
|