mirror of
https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git
synced 2026-06-15 07:24:56 +03:00
mukul975
efca3ec611
Mapped every skill to NIST CSF 2.0 subcategory IDs (GV/ID/PR/DE/RS/RC functions) based on subdomain and content analysis. Restores 11 skills corrupted during prior rebase, re-enriching with ATLAS, D3FEND, NIST AI RMF, and CSF 2.0 fields. All 754 skills now carry structured mappings for all 5 security frameworks: - MITRE ATT&CK (in tags) - MITRE ATLAS v5.5 (atlas_techniques) - MITRE D3FEND v1.3 (d3fend_techniques) - NIST AI RMF 1.0 (nist_ai_rmf) - NIST CSF 2.0 (nist_csf)
59 lines
2.3 KiB
Markdown
59 lines
2.3 KiB
Markdown
---
|
|
name: implementing-siem-use-case-tuning
|
|
description: 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
|
|
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
|
|
---
|
|
|
|
# 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.
|