Back to catalog
Static reviewDevelopment

Skill dossier

building-detection-rule-with-splunk-spl

Source declaration

Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.

The author's original description, preserved in English. It describes intent, not verified performance.

Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Step-by-Step Process [Source statement; provisional, not tested. Evidence: skills/building-detection-rule-with-splunk-spl/SKILL.md:L150]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/building-detection-rule-with-splunk-spl/SKILL.md:L1-L37]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
49.4 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/building-detection-rule-with-splunk-spl/assets/template.mdReference1.9 KB
skills/building-detection-rule-with-splunk-spl/LICENSEOther11 KB
skills/building-detection-rule-with-splunk-spl/references/api-reference.mdReference1.5 KB
skills/building-detection-rule-with-splunk-spl/references/standards.mdReference2.3 KB
skills/building-detection-rule-with-splunk-spl/references/workflows.mdReference2 KB
skills/building-detection-rule-with-splunk-spl/scripts/agent.pyScript6 KB
skills/building-detection-rule-with-splunk-spl/scripts/process.pyScript14.2 KB
skills/building-detection-rule-with-splunk-spl/SKILL.mdInstruction10.4 KB

SKILL.md frontmatter

{
  "name": "building-detection-rule-with-splunk-spl",
  "description": "Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.",
  "domain": "cybersecurity",
  "subdomain": "soc-operations",
  "tags": [
    "splunk",
    "spl",
    "detection-engineering",
    "correlation-search",
    "siem",
    "soc",
    "threat-detection",
    "enterprise-security"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Executable Denylisting",
    "Execution Isolation",
    "File Metadata Consistency Validation",
    "Content Format Conversion",
    "File Content Analysis"
  ],
  "nist_csf": [
    "DE.CM-01",
    "DE.AE-02",
    "RS.MA-01",
    "DE.AE-06"
  ],
  "mitre_attack": [
    "T1059.001",
    "T1003.001",
    "T1021.002",
    "T1110.003",
    "T1053.005",
    "T1048"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core SPL Detection Rule Patterns

    Source-described action candidate under “Core SPL Detection Rule Patterns”; not verified execution.

  4. 04
    Action

    Building Correlation Searches in Splunk ES

    Source-described action candidate under “Building Correlation Searches in Splunk ES”; not verified execution.

  5. 05
    Action

    Step-by-Step Process

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  6. 06
    Action

    Define the Use Case: Map to MITRE ATT&CK technique and define what behavior to detect

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

Inspect all extracted workflow candidates (17 candidate steps)
  1. 07
    Action

    Identify Data Sources: Determine which indexes and sourcetypes contain relevant events

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  2. 08
    Output

    Write the Base Search: Build SPL that extracts relevant events

    Source-described output candidate under “Step-by-Step Process”; not verified execution.

  3. 09
    Action

    Add Aggregation: Use `stats`, `eventstats`, or `streamstats` to summarize

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  4. 10
    Action

    Apply Thresholds: Set conditions with `where` clause that distinguish normal from anomalous

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  5. 11
    Action

    Enrich Context: Add lookups for asset information, identity data, and threat intelligence

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  6. 12
    Action

    Configure Notable Event: Set severity, urgency, and description fields

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  7. 13
    Action

    Schedule and Test: Run against historical data and validate detection accuracy

    Source-described action candidate under “Step-by-Step Process”; not verified execution.

  8. 14
    Action

    Performance Optimization

    Source-described action candidate under “Performance Optimization”; not verified execution.

  9. 15
    Action

    Testing and Validation

    Source-described action candidate under “Testing and Validation”; not verified execution.

  10. 16
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  11. 17
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

54 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Note

File modification is described or implemented

44 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 44 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

8 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 8 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Dynamic command execution is referenced

2 occurrences

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/building-detection-rule-with-splunk-spl/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/building-detection-rule-with-splunk-spl/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/building-detection-rule-with-splunk-spl
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.