What it does. Reduces SIEM false positives through systematic rule tuning, threshold Part of mukul975/Anthropic-Cybersecurity-Skills (817 security skills) (mukul975/Anthropic-Cybersecurity-Skills).

Upstream	mukul975/Anthropic-Cybersecurity-Skills
Skill file	skills/performing-false-positive-reduction-in-siem/SKILL.md
License	Apache-2.0 (skill folder LICENSE)
Author	mukul975
Fetched	2026-09-10

Install

• npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-false-positive-reduction-in-siem, or copy the skill folder into ~/.claude/skills/performing-false-positive-reduction-in-siem/.
• Raw file: curl -sL https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/HEAD/skills/performing-false-positive-reduction-in-siem/SKILL.md

SKILL.md (verbatim)

name: performing-false-positive-reduction-in-siem
description: Reduces SIEM false positives through systematic rule tuning, threshold
  adjustment, correlation logic refinement, allowlisting, and threat intelligence
  enrichment. Use when SOC analysts are overwhelmed by alert noise, when tuning noisy
  detection rules, or during a quarterly SIEM rule review to cut alert fatigue.
domain: cybersecurity
subdomain: soc-operations
tags:
- siem
- false-positive
- alert-tuning
- detection-engineering
- alert-fatigue
- soc
- correlation
version: '1.0'
author: mahipal
license: Apache-2.0
d3fend_techniques:
- Token Binding
- Restore Access
- Password Authentication
- Reissue Credential
- Strong Password Policy
nist_csf:
- DE.CM-01
- DE.AE-02
- RS.MA-01
- DE.AE-06
mitre_attack:
- T1078
- T1685.002
- T1685.005
- T1566

Performing False Positive Reduction in SIEM

Overview

False positive alerts are non-malicious events that trigger security rules, overwhelming SOC analysts with noise. Studies show that up to 45% of SIEM alerts are false positives, and a typical SOC analyst can only investigate 20-25 alerts per shift effectively. Reducing false positives requires systematic tuning across thresholds, correlation logic, allowlists, enrichment, and continuous validation. SIEM rules should be reviewed on a quarterly cycle at minimum.

When to Use

• When conducting security assessments that involve performing false positive reduction in siem
• When following incident response procedures for related security events
• When performing scheduled security testing or auditing activities
• When validating security controls through hands-on testing

Prerequisites

• Familiarity with soc operations concepts and tools
• Access to a test or lab environment for safe execution
• Python 3.8+ with required dependencies installed
• Appropriate authorization for any testing activities

False Positive Reduction Techniques

1. Identify the Noisiest Rules

# Splunk - Top 10 noisiest correlation searches
index=notable
| stats count by rule_name
| sort -count
| head 10
| eval pct=round(count / total * 100, 1)

# False positive rate per rule
index=notable
| stats count as total
    count(eval(status_label="Closed - False Positive")) as false_positives
    count(eval(status_label="Closed - True Positive")) as true_positives
    by rule_name
| eval fp_rate=round(false_positives / total * 100, 1)
| sort -fp_rate
| where total > 10

2. Threshold Tuning

# Before: Too sensitive - fires on 5 failed logins
index=wineventlog EventCode=4625
| stats count by src_ip
| where count > 5

# After: Tuned - requires 20+ failures across 3+ accounts in 10 minutes
index=wineventlog EventCode=4625
| bin _time span=10m
| stats count dc(TargetUserName) as unique_accounts by src_ip, _time
| where count > 20 AND unique_accounts > 3

3. Allowlist/Exclusion Management

# Create allowlist lookup for known benign sources
| inputlookup fp_allowlist.csv
| fields src_ip, reason, approved_by, expiry_date

# Apply allowlist in detection rule
index=wineventlog EventCode=4625
| lookup fp_allowlist src_ip OUTPUT reason as allowlisted_reason
| where isnull(allowlisted_reason)
| stats count dc(TargetUserName) as unique_accounts by src_ip
| where count > 20 AND unique_accounts > 3

4. Correlation Enhancement

# Before: Single-event detection (noisy)
index=wineventlog EventCode=4688 New_Process_Name="*powershell.exe"
| eval severity="medium"

# After: Multi-signal correlation (precise)
index=wineventlog EventCode=4688 New_Process_Name="*powershell.exe"
| join src_ip type=left [
    search index=wineventlog EventCode=4625
    | stats count as failed_logins by src_ip
]
| join Computer type=left [
    search index=sysmon EventCode=3
    | stats dc(DestinationIp) as unique_external_connections by Computer
    | where unique_external_connections > 10
]
| where isnotnull(failed_logins) OR unique_external_connections > 10
| eval severity=case(
    failed_logins > 10 AND unique_external_connections > 10, "critical",
    failed_logins > 5 OR unique_external_connections > 5, "high",
    true(), "medium"
)

5. Time-Based Exclusions

# Exclude known maintenance windows
| eval hour=strftime(_time, "%H")
| eval day=strftime(_time, "%A")
| where NOT (hour >= "02" AND hour <= "04" AND day="Sunday")

# Exclude known batch job schedules
| lookup scheduled_tasks_allowlist process_name, schedule_time
    OUTPUT is_scheduled
| where isnull(is_scheduled)

6. Behavioral Baseline Integration

# Build baseline for user login patterns
index=wineventlog EventCode=4624
| bin _time span=1h
| stats count as logins dc(Computer) as unique_hosts by TargetUserName, _time
| eventstats avg(logins) as avg_logins stdev(logins) as stdev_logins
    avg(unique_hosts) as avg_hosts stdev(unique_hosts) as stdev_hosts
    by TargetUserName
| where logins > (avg_logins + 3 * stdev_logins)
    OR unique_hosts > (avg_hosts + 3 * stdev_hosts)

7. Threat Intelligence Filtering

# Only alert when destination matches known threat intelligence
index=firewall action=allowed direction=outbound
| lookup ip_threat_intel_lookup ip as dest_ip OUTPUT threat_type, confidence
| where isnotnull(threat_type) AND confidence > 70
# This eliminates FPs from flagging connections to benign IPs

Tuning Process Framework

Step 1: Identify (Weekly)

• Pull top 10 rules by alert volume
• Calculate FP rate for each
• Identify rules with FP rate > 30%

Step 2: Analyze (Weekly)

• Sample 20 false positives per rule
• Categorize root cause of each FP
• Identify common patterns

Step 3: Tune (Bi-weekly)

• Adjust thresholds based on baseline data
• Add allowlist entries for benign patterns
• Enhance correlation logic
• Add enrichment context

Step 4: Validate (Monthly)

• Run Atomic Red Team tests to verify true positives still trigger
• Calculate new FP rate after tuning
• Document tuning rationale
• Review with detection engineering team

Step 5: Report (Quarterly)

• FP reduction metrics per rule
• Overall alert volume trends
• Analyst productivity improvements
• Rules retired or replaced

Validation Testing

# Run Atomic Red Team test after tuning to confirm detection still works
# Example: Test brute force detection after threshold adjustment
Invoke-AtomicTest T1110.001 -TestNumbers 1

# Verify detection still triggers after tuning
index=notable rule_name="Brute Force Detection"
earliest=-24h
| stats count
| where count > 0

FP Reduction Metrics

Metric	Formula	Target
False Positive Rate	FP / (FP + TP) * 100	< 20%
Alert Volume Reduction	(Old Volume - New Volume) / Old Volume * 100	30-50% per quarter
Mean Triage Time	Total triage time / Total alerts	< 8 minutes
Rule Precision	TP / (TP + FP)	> 0.80
Analyst Satisfaction	Survey score	> 4/5

References

• CyberSierra - Tune SIEM Alerts to Eliminate False Positives
• ConnectWise - 9 Ways to Eliminate SIEM False Positives
• Prophet Security - Alert Tuning Best Practices
• ManageEngine - Reducing SIEM Alert False Positives

Other files in this skill

• LICENSE
• assets/template.md
• references/api-reference.md
• references/standards.md
• references/workflows.md
• scripts/agent.py
• scripts/process.py

assets/template.md (verbatim)

False Positive Reduction Template

Rule Tuning Request

Field	Value
Rule Name
Current FP Rate
Target FP Rate
Alert Volume (30 days)
Root Cause Category	Threshold / Missing context / Known benign / Outdated

FP Root Cause Analysis

Sample #	Source	Classification	Root Cause	Recommended Fix
1		FP
2		FP
3		FP

Tuning Action Plan

• Adjust threshold from ___ to ___
• Add allowlist entries for: ___
• Add correlation with: ___
• Add enrichment lookup: ___
• Test with Atomic Red Team: ___
• Validate FP rate improvement after 7 days

references/api-reference.md (verbatim)

API Reference — Performing False Positive Reduction in SIEM

Libraries Used

• csv: Parse SIEM alert export files (Splunk, QRadar, Sentinel)
• collections.Counter: Aggregate alert patterns by rule, source, severity

CLI Interface

python agent.py analyze --csv alerts.csv [--threshold 5]
python agent.py tune --csv alerts.csv
python agent.py simulate --csv alerts.csv [--disable-rules "Rule A" "Rule B"] [--whitelist-sources 10.0.0.1]

Core Functions

analyze_alerts(csv_file, threshold) — Identify false positive patterns

Parses alert CSV, calculates per-rule FP rates, identifies noisy rules exceeding threshold. Returns: total alerts, FP count/rate, noisy rules ranked by FP rate, top FP sources.

generate_tuning_recommendations(csv_file) — Create tuning action plan

Maps FP rates to actions: DISABLE (>=90%), ADD_WHITELIST (>=70%), TUNE_THRESHOLD (>=50%), REVIEW (<50%).

simulate_tuning_impact(csv_file, rules_to_disable, sources_to_whitelist) — Model tuning changes

Calculates alert volume reduction and new FP rate after applying proposed rule disables and source whitelists.

Expected CSV Columns

• rule_name / Rule / alert_name: Detection rule identifier
• src_ip / source_ip / Source: Source IP address
• status / Status / disposition: Alert disposition (false_positive, fp, closed_fp, benign)
• severity / Severity: Alert severity level

FP Status Keywords

false_positive, fp, closed_fp, benign

Dependencies

No external packages — Python standard library only.

references/standards.md (verbatim)

Standards - False Positive Reduction in SIEM

Detection Quality Metrics (Industry Standards)

Metric	Excellent	Good	Needs Improvement	Critical
False Positive Rate	< 10%	10-20%	20-40%	> 40%
Rule Precision	> 0.90	0.80-0.90	0.60-0.80	< 0.60
Mean Triage Time	< 5 min	5-10 min	10-20 min	> 20 min
Alert-to-Incident Ratio	1:5	1:10	1:20	> 1:50

Tuning Frameworks

NIST Continuous Monitoring (SP 800-137)

• Requires regular assessment and adjustment of detection capabilities
• Defines metrics-based approach to monitoring effectiveness

SANS Detection Maturity Model

• Level 1: Basic alerts with high FP rate
• Level 2: Tuned alerts with correlation
• Level 3: Behavioral analytics reducing noise
• Level 4: Automated tuning with ML feedback loops

Allowlist Management Standards

• All exclusions require documented justification
• Expiry dates mandatory (90-day maximum default)
• Quarterly review of all active exclusions
• Approval from detection engineering lead required

references/workflows.md (verbatim)

Workflows - False Positive Reduction

Tuning Cycle

Identify Noisy Rules --> Analyze FP Root Causes --> Tune Rules -->
Validate with Testing --> Measure Improvement --> Report --> Repeat

FP Analysis Categorization

Category	Action	Example
Known benign	Add to allowlist	Vulnerability scanner IPs
Threshold too low	Raise threshold	Login failure count from 5 to 20
Missing context	Add correlation	PowerShell + network = suspicious
Missing enrichment	Add lookup	Asset criticality context
Rule outdated	Rewrite or retire	Legacy detection no longer relevant

Back to mukul975/Anthropic-Cybersecurity-Skills (817 security skills) or Agent skills.