[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B567FRC99HV8V0BY25KBXK":3,"skill-same:01M7B567FRC99HV8V0BY25KBXK":109},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":55,"commitSha":56,"skillDirectory":57,"forksCount":13,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M7B567FRC99HV8V0BY25KBXK","building-detection-rule-with-splunk-spl",null,"Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: building-detection-rule-with-splunk-spl\ndescription: Build effective detection rules using Splunk Search Processing Language\n  (SPL) correlation searches to identify security threats in SOC environments.\ndomain: cybersecurity\nsubdomain: soc-operations\ntags:\n- splunk\n- spl\n- detection-engineering\n- correlation-search\n- siem\n- soc\n- threat-detection\n- enterprise-security\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- Executable Denylisting\n- Execution Isolation\n- File Metadata Consistency Validation\n- Content Format Conversion\n- File Content Analysis\nnist_csf:\n- DE.CM-01\n- DE.AE-02\n- RS.MA-01\n- DE.AE-06\nmitre_attack:\n- T1059.001\n- T1003.001\n- T1021.002\n- T1110.003\n- T1053.005\n- T1048\n---\n\n# Building Detection Rules with Splunk SPL\n\n## Overview\n\nSplunk Search Processing Language (SPL) is the primary query language used in Splunk Enterprise Security for building correlation searches that detect suspicious events and patterns. A well-crafted detection rule aggregates, correlates, and enriches security events to generate actionable notable events for SOC analysts. Enterprise SIEMs on average cover only 21% of MITRE ATT&CK techniques, making skilled SPL rule writing essential for closing detection gaps.\n\n\n## When to Use\n\n- When deploying or configuring building detection rule with splunk spl capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Splunk Enterprise Security (ES) deployed and configured\n- Access to Splunk Search & Reporting app with appropriate roles\n- Understanding of Common Information Model (CIM) data models\n- Familiarity with MITRE ATT&CK framework techniques\n- Knowledge of the organization's log sources and data flows\n\n## Core SPL Detection Rule Patterns\n\n### 1. Threshold-Based Detection\n\nDetects events exceeding a defined count within a time window.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security EventCode=4625\n| stats count as failed_logins dc(TargetUserName) as unique_users by src_ip\n| where failed_logins > 10 AND unique_users > 3\n| eval severity=\"high\"\n| eval description=\"Brute force attack detected from \".src_ip.\" with \".failed_logins.\" failed logins across \".unique_users.\" accounts\"\n```\n\n### 2. Sequence-Based Detection (Failed Login Followed by Success)\n\nCorrelates a sequence of events indicating a successful brute force attack.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security (EventCode=4625 OR EventCode=4624)\n| eval login_status=case(EventCode=4625, \"failure\", EventCode=4624, \"success\")\n| stats count(eval(login_status=\"failure\")) as failures count(eval(login_status=\"success\")) as successes latest(_time) as last_event by src_ip, TargetUserName\n| where failures > 5 AND successes > 0\n| eval description=\"Account \".TargetUserName.\" compromised via brute force from \".src_ip\n| eval urgency=\"critical\"\n```\n\n### 3. Anomaly Detection with Baseline Comparison\n\nCompares current activity against a baseline period to detect spikes.\n\n```spl\nindex=proxy sourcetype=squid\n| bin _time span=1h\n| stats count as current_count by src_ip, _time\n| join src_ip type=left [\n    search index=proxy sourcetype=squid earliest=-7d@d latest=-1d@d\n    | stats avg(count) as avg_count stdev(count) as stdev_count by src_ip\n]\n| eval threshold=avg_count + (3 * stdev_count)\n| where current_count > threshold\n| eval deviation=round((current_count - avg_count) \u002F stdev_count, 2)\n| eval description=\"Anomalous web traffic from \".src_ip.\" - \".deviation.\" standard deviations above baseline\"\n```\n\n### 4. Lateral Movement Detection\n\nIdentifies potential lateral movement using Windows logon events.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security EventCode=4624 Logon_Type=3\n| where NOT match(TargetUserName, \".*\\$$\")\n| stats dc(dest) as unique_hosts values(dest) as hosts by src_ip, TargetUserName\n| where unique_hosts > 5\n| eval severity=case(unique_hosts > 20, \"critical\", unique_hosts > 10, \"high\", true(), \"medium\")\n| eval description=TargetUserName.\" accessed \".unique_hosts.\" unique hosts from \".src_ip.\" via network logon\"\n```\n\n### 5. Data Exfiltration Detection\n\nMonitors for large outbound data transfers.\n\n```spl\nindex=firewall sourcetype=pan:traffic action=allowed direction=outbound\n| stats sum(bytes_out) as total_bytes_out dc(dest_ip) as unique_destinations by src_ip, user\n| eval total_mb=round(total_bytes_out\u002F1048576, 2)\n| where total_mb > 500 OR unique_destinations > 50\n| lookup asset_lookup ip as src_ip OUTPUT asset_category, asset_owner\n| eval severity=case(total_mb > 2000, \"critical\", total_mb > 1000, \"high\", true(), \"medium\")\n| eval description=user.\" transferred \".total_mb.\"MB to \".unique_destinations.\" unique destinations\"\n```\n\n### 6. PowerShell Suspicious Execution Detection\n\nDetects encoded or obfuscated PowerShell commands.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security EventCode=4104\n| where match(ScriptBlockText, \"(?i)(encodedcommand|invoke-expression|iex|downloadstring|frombase64string|net\\.webclient|invoke-webrequest|bitstransfer|invoke-mimikatz|invoke-shellcode)\")\n| eval decoded_length=len(ScriptBlockText)\n| stats count values(ScriptBlockText) as commands by Computer, UserName\n| where count > 0\n| eval severity=\"high\"\n| eval mitre_technique=\"T1059.001\"\n| eval description=\"Suspicious PowerShell execution on \".Computer.\" by \".UserName\n```\n\n## Building Correlation Searches in Splunk ES\n\n### Step-by-Step Process\n\n1. **Define the Use Case**: Map to MITRE ATT&CK technique and define what behavior to detect\n2. **Identify Data Sources**: Determine which indexes and sourcetypes contain relevant events\n3. **Write the Base Search**: Build SPL that extracts relevant events\n4. **Add Aggregation**: Use `stats`, `eventstats`, or `streamstats` to summarize\n5. **Apply Thresholds**: Set conditions with `where` clause that distinguish normal from anomalous\n6. **Enrich Context**: Add lookups for asset information, identity data, and threat intelligence\n7. **Configure Notable Event**: Set severity, urgency, and description fields\n8. **Schedule and Test**: Run against historical data and validate detection accuracy\n\n### Correlation Search Configuration Template\n\n```spl\n| tstats summariesonly=true count from datamodel=Authentication\n    where Authentication.action=failure\n    by Authentication.src, Authentication.user, _time span=5m\n| rename \"Authentication.*\" as *\n| stats count as total_failures dc(user) as unique_users values(user) as targeted_users by src\n| where total_failures > 20 AND unique_users > 5\n| lookup dnslookup clientip as src OUTPUT clienthost as src_dns\n| lookup asset_lookup ip as src OUTPUT priority as asset_priority, category as asset_category\n| eval urgency=case(asset_priority==\"critical\", \"critical\", asset_priority==\"high\", \"high\", true(), \"medium\")\n| eval rule_name=\"Brute Force Against Multiple Accounts\"\n| eval rule_description=\"Multiple authentication failures from \".src.\" targeting \".unique_users.\" unique accounts\"\n| eval mitre_attack=\"T1110.001 - Password Guessing\"\n```\n\n### Enrichment Best Practices\n\n```spl\n| lookup identity_lookup identity as user OUTPUT department, manager, risk_score as user_risk\n| lookup asset_lookup ip as src_ip OUTPUT asset_name, asset_category, asset_priority, asset_owner\n| lookup threatintel_lookup ip as src_ip OUTPUT threat_type, threat_confidence, threat_source\n| eval context=case(\n    isnotnull(threat_type), \"Known threat: \".threat_type,\n    user_risk > 80, \"High-risk user: risk score \".user_risk,\n    asset_priority==\"critical\", \"Critical asset: \".asset_name,\n    true(), \"Standard context\"\n)\n```\n\n## Performance Optimization\n\n### Use Data Models with tstats\n\n```spl\n| tstats summariesonly=true count from datamodel=Network_Traffic\n    where All_Traffic.action=allowed\n    by All_Traffic.src_ip, All_Traffic.dest_ip, All_Traffic.dest_port, _time span=1h\n| rename \"All_Traffic.*\" as *\n```\n\n### Limit Time Ranges and Use Indexed Fields\n\n```spl\nindex=wineventlog source=\"WinEventLog:Security\" EventCode=4688\n    earliest=-15m latest=now()\n| where NOT match(New_Process_Name, \"(?i)(svchost|csrss|lsass|services)\")\n```\n\n### Use Summary Indexing for Historical Baselines\n\n```spl\n| tstats count from datamodel=Authentication where Authentication.action=failure by Authentication.src, _time span=1h\n| collect index=summary source=\"auth_failure_baseline\" marker=\"report_name=auth_failure_hourly\"\n```\n\n## Testing and Validation\n\n### Test Against Known Attack Patterns\n\n```spl\n| makeresults count=1\n| eval src_ip=\"10.0.0.50\", failed_logins=25, unique_users=8, severity=\"high\"\n| eval description=\"Test brute force detection\"\n| append [\n    search index=wineventlog sourcetype=WinEventLog:Security EventCode=4625\n    earliest=-24h latest=now()\n    | stats count as failed_logins dc(TargetUserName) as unique_users by src_ip\n    | where failed_logins > 10 AND unique_users > 3\n    | eval severity=\"high\"\n]\n```\n\n### Calculate Detection Metrics\n\n```spl\nindex=notable\n| search rule_name=\"Brute Force*\"\n| stats count as total_alerts count(eval(status_label=\"Closed - True Positive\")) as true_positives count(eval(status_label=\"Closed - False Positive\")) as false_positives by rule_name\n| eval precision=round(true_positives \u002F (true_positives + false_positives) * 100, 2)\n| eval fpr=round(false_positives \u002F total_alerts * 100, 2)\n```\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Technique Name | SPL Detection Approach |\n|---|---|---|\n| T1110.001 | Password Guessing | Threshold on EventCode 4625 by src_ip |\n| T1059.001 | PowerShell | Pattern match on EventCode 4104 ScriptBlockText |\n| T1021.002 | SMB\u002FWindows Admin Shares | Logon Type 3 with dc(dest) threshold |\n| T1048 | Exfiltration Over C2 | bytes_out aggregation over time window |\n| T1053.005 | Scheduled Task | EventCode 4698 with suspicious command patterns |\n| T1003.001 | LSASS Memory | Process access to lsass.exe via Sysmon EventCode 10 |\n\n## References\n\n- [Splunk ES Correlation Searches Best Practices](https:\u002F\u002Fdetect.fyi\u002Fsplunk-es-correlation-searches-rules-best-cool-practices-06ef94884170)\n- [Writing Practical Splunk Detection Rules](https:\u002F\u002Fmedium.com\u002F@vitbukac\u002Fpractical-splunk-detection-rules-how-to-part-1-crawl-a24bc39a4b9d)\n- [Configure Correlation Searches - Splunk Documentation](https:\u002F\u002Fhelp.splunk.com\u002Fen\u002Fsplunk-enterprise-security-8\u002Fsplunk-app-for-pci-compliance\u002Finstallation-and-configuration-manual\u002F6.1\u002Fconfigure-correlation-searches\u002Fconfigure-correlation-searches)\n- [SOC Prime - Correlation Events in Splunk](https:\u002F\u002Fsocprime.com\u002Fblog\u002Fcreating-correlation-events-in-splunk-using-alerts\u002F)\n","# Building Detection Rules with Splunk SPL\n\n## Overview\n\nSplunk Search Processing Language (SPL) is the primary query language used in Splunk Enterprise Security for building correlation searches that detect suspicious events and patterns. A well-crafted detection rule aggregates, correlates, and enriches security events to generate actionable notable events for SOC analysts. Enterprise SIEMs on average cover only 21% of MITRE ATT&CK techniques, making skilled SPL rule writing essential for closing detection gaps.\n\n\n## When to Use\n\n- When deploying or configuring building detection rule with splunk spl capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Splunk Enterprise Security (ES) deployed and configured\n- Access to Splunk Search & Reporting app with appropriate roles\n- Understanding of Common Information Model (CIM) data models\n- Familiarity with MITRE ATT&CK framework techniques\n- Knowledge of the organization's log sources and data flows\n\n## Core SPL Detection Rule Patterns\n\n### 1. Threshold-Based Detection\n\nDetects events exceeding a defined count within a time window.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security EventCode=4625\n| stats count as failed_logins dc(TargetUserName) as unique_users by src_ip\n| where failed_logins > 10 AND unique_users > 3\n| eval severity=\"high\"\n| eval description=\"Brute force attack detected from \".src_ip.\" with \".failed_logins.\" failed logins across \".unique_users.\" accounts\"\n```\n\n### 2. Sequence-Based Detection (Failed Login Followed by Success)\n\nCorrelates a sequence of events indicating a successful brute force attack.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security (EventCode=4625 OR EventCode=4624)\n| eval login_status=case(EventCode=4625, \"failure\", EventCode=4624, \"success\")\n| stats count(eval(login_status=\"failure\")) as failures count(eval(login_status=\"success\")) as successes latest(_time) as last_event by src_ip, TargetUserName\n| where failures > 5 AND successes > 0\n| eval description=\"Account \".TargetUserName.\" compromised via brute force from \".src_ip\n| eval urgency=\"critical\"\n```\n\n### 3. Anomaly Detection with Baseline Comparison\n\nCompares current activity against a baseline period to detect spikes.\n\n```spl\nindex=proxy sourcetype=squid\n| bin _time span=1h\n| stats count as current_count by src_ip, _time\n| join src_ip type=left [\n    search index=proxy sourcetype=squid earliest=-7d@d latest=-1d@d\n    | stats avg(count) as avg_count stdev(count) as stdev_count by src_ip\n]\n| eval threshold=avg_count + (3 * stdev_count)\n| where current_count > threshold\n| eval deviation=round((current_count - avg_count) \u002F stdev_count, 2)\n| eval description=\"Anomalous web traffic from \".src_ip.\" - \".deviation.\" standard deviations above baseline\"\n```\n\n### 4. Lateral Movement Detection\n\nIdentifies potential lateral movement using Windows logon events.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security EventCode=4624 Logon_Type=3\n| where NOT match(TargetUserName, \".*\\$$\")\n| stats dc(dest) as unique_hosts values(dest) as hosts by src_ip, TargetUserName\n| where unique_hosts > 5\n| eval severity=case(unique_hosts > 20, \"critical\", unique_hosts > 10, \"high\", true(), \"medium\")\n| eval description=TargetUserName.\" accessed \".unique_hosts.\" unique hosts from \".src_ip.\" via network logon\"\n```\n\n### 5. Data Exfiltration Detection\n\nMonitors for large outbound data transfers.\n\n```spl\nindex=firewall sourcetype=pan:traffic action=allowed direction=outbound\n| stats sum(bytes_out) as total_bytes_out dc(dest_ip) as unique_destinations by src_ip, user\n| eval total_mb=round(total_bytes_out\u002F1048576, 2)\n| where total_mb > 500 OR unique_destinations > 50\n| lookup asset_lookup ip as src_ip OUTPUT asset_category, asset_owner\n| eval severity=case(total_mb > 2000, \"critical\", total_mb > 1000, \"high\", true(), \"medium\")\n| eval description=user.\" transferred \".total_mb.\"MB to \".unique_destinations.\" unique destinations\"\n```\n\n### 6. PowerShell Suspicious Execution Detection\n\nDetects encoded or obfuscated PowerShell commands.\n\n```spl\nindex=wineventlog sourcetype=WinEventLog:Security EventCode=4104\n| where match(ScriptBlockText, \"(?i)(encodedcommand|invoke-expression|iex|downloadstring|frombase64string|net\\.webclient|invoke-webrequest|bitstransfer|invoke-mimikatz|invoke-shellcode)\")\n| eval decoded_length=len(ScriptBlockText)\n| stats count values(ScriptBlockText) as commands by Computer, UserName\n| where count > 0\n| eval severity=\"high\"\n| eval mitre_technique=\"T1059.001\"\n| eval description=\"Suspicious PowerShell execution on \".Computer.\" by \".UserName\n```\n\n## Building Correlation Searches in Splunk ES\n\n### Step-by-Step Process\n\n1. **Define the Use Case**: Map to MITRE ATT&CK technique and define what behavior to detect\n2. **Identify Data Sources**: Determine which indexes and sourcetypes contain relevant events\n3. **Write the Base Search**: Build SPL that extracts relevant events\n4. **Add Aggregation**: Use `stats`, `eventstats`, or `streamstats` to summarize\n5. **Apply Thresholds**: Set conditions with `where` clause that distinguish normal from anomalous\n6. **Enrich Context**: Add lookups for asset information, identity data, and threat intelligence\n7. **Configure Notable Event**: Set severity, urgency, and description fields\n8. **Schedule and Test**: Run against historical data and validate detection accuracy\n\n### Correlation Search Configuration Template\n\n```spl\n| tstats summariesonly=true count from datamodel=Authentication\n    where Authentication.action=failure\n    by Authentication.src, Authentication.user, _time span=5m\n| rename \"Authentication.*\" as *\n| stats count as total_failures dc(user) as unique_users values(user) as targeted_users by src\n| where total_failures > 20 AND unique_users > 5\n| lookup dnslookup clientip as src OUTPUT clienthost as src_dns\n| lookup asset_lookup ip as src OUTPUT priority as asset_priority, category as asset_category\n| eval urgency=case(asset_priority==\"critical\", \"critical\", asset_priority==\"high\", \"high\", true(), \"medium\")\n| eval rule_name=\"Brute Force Against Multiple Accounts\"\n| eval rule_description=\"Multiple authentication failures from \".src.\" targeting \".unique_users.\" unique accounts\"\n| eval mitre_attack=\"T1110.001 - Password Guessing\"\n```\n\n### Enrichment Best Practices\n\n```spl\n| lookup identity_lookup identity as user OUTPUT department, manager, risk_score as user_risk\n| lookup asset_lookup ip as src_ip OUTPUT asset_name, asset_category, asset_priority, asset_owner\n| lookup threatintel_lookup ip as src_ip OUTPUT threat_type, threat_confidence, threat_source\n| eval context=case(\n    isnotnull(threat_type), \"Known threat: \".threat_type,\n    user_risk > 80, \"High-risk user: risk score \".user_risk,\n    asset_priority==\"critical\", \"Critical asset: \".asset_name,\n    true(), \"Standard context\"\n)\n```\n\n## Performance Optimization\n\n### Use Data Models with tstats\n\n```spl\n| tstats summariesonly=true count from datamodel=Network_Traffic\n    where All_Traffic.action=allowed\n    by All_Traffic.src_ip, All_Traffic.dest_ip, All_Traffic.dest_port, _time span=1h\n| rename \"All_Traffic.*\" as *\n```\n\n### Limit Time Ranges and Use Indexed Fields\n\n```spl\nindex=wineventlog source=\"WinEventLog:Security\" EventCode=4688\n    earliest=-15m latest=now()\n| where NOT match(New_Process_Name, \"(?i)(svchost|csrss|lsass|services)\")\n```\n\n### Use Summary Indexing for Historical Baselines\n\n```spl\n| tstats count from datamodel=Authentication where Authentication.action=failure by Authentication.src, _time span=1h\n| collect index=summary source=\"auth_failure_baseline\" marker=\"report_name=auth_failure_hourly\"\n```\n\n## Testing and Validation\n\n### Test Against Known Attack Patterns\n\n```spl\n| makeresults count=1\n| eval src_ip=\"10.0.0.50\", failed_logins=25, unique_users=8, severity=\"high\"\n| eval description=\"Test brute force detection\"\n| append [\n    search index=wineventlog sourcetype=WinEventLog:Security EventCode=4625\n    earliest=-24h latest=now()\n    | stats count as failed_logins dc(TargetUserName) as unique_users by src_ip\n    | where failed_logins > 10 AND unique_users > 3\n    | eval severity=\"high\"\n]\n```\n\n### Calculate Detection Metrics\n\n```spl\nindex=notable\n| search rule_name=\"Brute Force*\"\n| stats count as total_alerts count(eval(status_label=\"Closed - True Positive\")) as true_positives count(eval(status_label=\"Closed - False Positive\")) as false_positives by rule_name\n| eval precision=round(true_positives \u002F (true_positives + false_positives) * 100, 2)\n| eval fpr=round(false_positives \u002F total_alerts * 100, 2)\n```\n\n## MITRE ATT&CK Mapping\n\n| Technique ID | Technique Name | SPL Detection Approach |\n|---|---|---|\n| T1110.001 | Password Guessing | Threshold on EventCode 4625 by src_ip |\n| T1059.001 | PowerShell | Pattern match on EventCode 4104 ScriptBlockText |\n| T1021.002 | SMB\u002FWindows Admin Shares | Logon Type 3 with dc(dest) threshold |\n| T1048 | Exfiltration Over C2 | bytes_out aggregation over time window |\n| T1053.005 | Scheduled Task | EventCode 4698 with suspicious command patterns |\n| T1003.001 | LSASS Memory | Process access to lsass.exe via Sysmon EventCode 10 |\n\n## References\n\n- [Splunk ES Correlation Searches Best Practices](https:\u002F\u002Fdetect.fyi\u002Fsplunk-es-correlation-searches-rules-best-cool-practices-06ef94884170)\n- [Writing Practical Splunk Detection Rules](https:\u002F\u002Fmedium.com\u002F@vitbukac\u002Fpractical-splunk-detection-rules-how-to-part-1-crawl-a24bc39a4b9d)\n- [Configure Correlation Searches - Splunk Documentation](https:\u002F\u002Fhelp.splunk.com\u002Fen\u002Fsplunk-enterprise-security-8\u002Fsplunk-app-for-pci-compliance\u002Finstallation-and-configuration-manual\u002F6.1\u002Fconfigure-correlation-searches\u002Fconfigure-correlation-searches)\n- [SOC Prime - Correlation Events in Splunk](https:\u002F\u002Fsocprime.com\u002Fblog\u002Fcreating-correlation-events-in-splunk-using-alerts\u002F)\n",{"name":5,"tags":24,"author":33,"domain":34,"license":14,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42,"d3fend_techniques":49},[25,26,27,28,29,30,31,32],"splunk","spl","detection-engineering","correlation-search","siem","soc","threat-detection","enterprise-security","mahipal","cybersecurity","1.0",[37,38,39,40],"DE.CM-01","DE.AE-02","RS.MA-01","DE.AE-06","soc-operations",[43,44,45,46,47,48],"T1059.001","T1003.001","T1021.002","T1110.003","T1053.005","T1048",[50,51,52,53,54],"Executable Denylisting","Execution Isolation","File Metadata Consistency Validation","Content Format Conversion","File Content Analysis","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill building-detection-rule-with-splunk-spl",{"tool":67,"command":68},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill building-detection-rule-with-splunk-spl",{"tool":70,"command":71},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill building-detection-rule-with-splunk-spl","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002FSKILL.md",true,[75,81,85,91,95,99,105],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"assets\u002Ftemplate.md","ASSET","资产文件",1982,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002Fassets\u002Ftemplate.md",{"path":82,"resourceType":82,"resourceTypeDesc":83,"sizeBytes":84,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fapi-reference.md","REFERENCE","参考文档",1554,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002Freferences\u002Fapi-reference.md",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fstandards.md",2366,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002Freferences\u002Fstandards.md",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fworkflows.md",2069,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002Freferences\u002Fworkflows.md",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"scripts\u002Fagent.py","SCRIPT","脚本",6128,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002Fscripts\u002Fagent.py",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"scripts\u002Fprocess.py",14541,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fbuilding-detection-rule-with-splunk-spl\u002Fscripts\u002Fprocess.py",[110,118,125,132,139,146],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":114,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":152,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]