PAGES
← all tools
◆ Detection Engineering

Splunk Security Content

v6.9.2 open-source

Summary

Splunk Security Content is an open-source repository of detection content—Splunk searches, machine learning algorithms, and analytic stories mapping tactics and techniques to the MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior. Framework, Lockheed Martin Cyber Kill Chain, and CISCISA nonprofit that publishes consensus-based configuration benchmarks and controls for hardening operating systems, cloud environments, and software; cyber tools use it as a ready-made compliance baseline. Controls—that plugs into Splunk deployments rather than running as a standalone tool. It's built for SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts and detection engineers who need pre-built, mapped detections rather than starting from scratch, and content development now runs through Detection Studio, the project's officially supported successor to contentctl. Coverage spans commodity threats to nation-state tradecraft, from Cisco IOS XE and SD-WANSD-WANSoftware-defined wide-area networking: an approach that decouples WAN routing logic from physical hardware, letting operators centrally control traffic paths across MPLS, broadband, and LTE links to reduce cost and improve resilience. analytics to EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. evasion, bootkit activity, and RMM tool abuse, with older detections formally deprecated and removed as techniques age out. It sits alongside sister projects Splunk Attack Range for simulation and contentctl-ng for packaging.

How Splunk Security Content helps

Which techniques in my environment have no detection coverage yet?

each analytic story ties its searches to specific MITRE ATT&CK techniques, kill chain phases, and CIS Controls, so a reader can line up the shipped searches against the framework and see which techniques have nothing written for them

Do I have any way to catch the tradecraft behind a specific named threat or campaign, like Salt Typhoon or Cobalt Strike beaconing?

analytic stories group the searches, background, and mapped techniques for a given actor or tool family together, so pointing a deployment at one story brings in every search built for that campaign at once

Are my Cisco IOS XE, SD-WAN, or Secure Access logs already being watched for known abuse patterns?

dedicated detections look for specific behaviors in that telemetry, such as multiple source IPs authenticating to vManage or guestshell activation sequences, so a reader can check whether their ingested logs line up with what those searches expect

Can my existing Windows or Linux logs reveal EDR tampering, bootkit activity, or privilege-escalation attempts already in the environment?

each detection specifies the log source and search logic it runs against, such as auditd telemetry for privilege escalation or registry events for EDR agent removal, so a reader can run the search against their own data and see if the behavior has already occurred

Which of my alerting workflows depend on detections that are being phased out?

detections slated for deprecation or removal are called out by name ahead of the cut, so a reader can check their correlation searches and use cases against that list before the content disappears in a later version

Is a piece of detection content still relevant to what's happening in my environment right now, or built for tradecraft that's since changed?

creation and modification dates are exposed on every detection and story, so a reader can weigh a search's age against the current threat before relying on it

all 17 features, with the evidence for each →

Languages

Not documented

Features

17 capabilities across 3 capability groups · 5 backed by code, an API document or a real run

Built from Splunk Security Content's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • Splunk Security Content covers 3 of the 11 logs and telemetry capabilities we track.

What Splunk Security Content offers you

  • Command-line interface2
  • CSV data export1
  • Ticketing integration1
Log parsing and normalization 1 feature Logs and telemetry since 2026
SCS prefix configuration verified Allows users to set a Splunk Common Schema (SCS) prefix applied across detection content at generation or validation time. 1 other source · first seen Jan 2026

Shared capability: Log parsing and normalization

command line

Log enrichment 1 feature Logs and telemetry since 2022
Detection lookup enrichment shipped Maintains reference lookup files (e.g. attacker tools, malware user-agent strings) that augment detections with additional context at search time. 23 releases · first seen Oct 2022

Shared capability: Log enrichment

release 23 total

  • Adds nist_ai_rmf_subcategories lookup to align detections with NIST AI Risk Management Framework subcategories v6.6.0 · Sep 2026 · source · release history
  • Refreshes the attacker_tools and malware_user_agents lookup CSV files with updated content to improve detection and investigation context. v6.4.0 · Aug 2026 · source · release history
  • Updated Cisco Secure Firewall - Intrusion Events by Threat Activity lookup with the latest Snort IDs for improved ArcaneDoor threat coverage. v5.15.0 · Sep 2025 · source · release history
  • New lookup: typo_squatted_python_packages — backs detection of typosquatted Python package installations via Cisco NVM telemetry. v5.9.0 · Jul 2025 · source · release history
  • New lookup: suspicious_ports_list — supports detections flagging outbound connections to suspicious ports. v5.9.0 · Jul 2025 · source · release history
  • Updates lookups cisco_secure_firewall_filetype_lookup and cisco_snort_ids_to_threat_mapping with expanded coverage. v5.7.0 · Jun 2025 · source · release history
Log replay 1 feature Logs and telemetry since 2022
Custom test index replay shipped Allows testers to configure and replay test data into specific or custom Splunk indexes rather than the default main index, enabling isolation of detection testing. 1 release · 1 other source · first seen Jun 2022

Shared capability: Log replay

release

  • Adds custom_index field to test.yml to allow replaying data into a custom index instead of the default main v3.43.0 · Jun 2022 · source · release history

example

  • Replay test data into a specific index rather than the default main Add the line custom_index: my_test_index to your `test.yml` file. v3.43.0 · Jun 2022 · source
Other / not yet classified 14 features Features we have not matched to a capability yet. A suggested match is marked.
Detection content library shipped A curated, versioned library of threat detections spanning Windows, Linux, cloud, and network platforms, continuously updated with new analytics, analytic stories, and data sources. 1372 releases · 2 other sources · first seen Nov 2019

release 1372 total

  • Advances four M365 Copilot jailbreak analytics to production. v6.9.0 · Oct 2026 · source · release history
  • Adds AWS Anomalous Secrets Manager Batch Retrieval, AWS Repeated CloudWatch Logs Read Operations, AWS EC2 Multiple SSH Public Keys Uploaded by a Single Identity, AWS EC2 Startup Script Modified on Stopped Instance, and AWS IAM Role Created with External Trust detections for expanded AWS CloudTrail coverage,… v6.9.0 · Oct 2026 · source · release history
  • Adds three new Cisco AI Defense detections: Cisco AI Defense Allowed Sensitive Prompt, Cisco AI Defense Allowed Sensitive Response, and Cisco AI Defense Repeated High Risk Activity.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v6.9.0 · Oct 2026 · source · release history
  • Adds PowerShell Download from Code Hosting Service and Windows Process Outbound Connection To Social Media Domain endpoint detections. v6.9.0 · Oct 2026 · source · release history
  • Introduces a new Abuse of GenAI Systems and Applications analytic story covering GenAI abuse surface. v6.9.0 · Oct 2026 · source · release history
  • Refreshes remote access software coverage and its lookup, adds a file-sharing domains lookup, and updates suspicious-port detection for Cisco Secure Firewall. v6.9.0 · Oct 2026 · source · release history

docs

  • Repository of Splunk Analytic Stories, detections, and playbooks mapped to MITRE ATT&CK for threat detection and response.

example

  • Use the new PSAs hunting workbook for incident response In the Splunk SOAR playbook library, import and run 'Splunk PSA Hunting 06/22' v3.43.0 · Jun 2022 · source
Detection deprecation and removal lifecycle shipped Formally retires outdated or superseded detections on a documented schedule, giving users advance notice and replacement guidance before content is permanently removed. 41 releases · first seen Jul 2022

release 41 total

  • MacOS - Re-opened Applications, Windows Process Injection into Notepad, and XMRIG Driver Loaded detections are scheduled for removal in ESCU version 6.10.0. v6.7.0 · Sep 2026 · source · release history
  • MacOS - Re-opened Applications detection scheduled for removal in ESCU version 6.10.0 v6.7.0 · Sep 2026 · source · release history
  • XMRIG Driver Loaded detection scheduled for removal in ESCU version 6.10.0 v6.7.0 · Sep 2026 · source · release history
  • Windows Process Injection into Notepad detection scheduled for removal in ESCU version 6.10.0 v6.7.0 · Sep 2026 · source · release history
  • The following detections are permanently removed: PowerShell - Connect To Internet With Hidden Window, Regsvr32 with Known Silent Switch Cmdline, Rundll32 CreateRemoteThread In Browser, Splunk App for Lookup File Editing RCE via User XSLT, Splunk Code Injection via custom dashboard leading to RCE, Splunk… v6.4.0 · Aug 2026 · source · release history
  • Detections PowerShell - Connect To Internet With Hidden Window, Regsvr32 with Known Silent Switch Cmdline, Rundll32 CreateRemoteThread In Browser, Splunk App for Lookup File Editing RCE via User XSLT, Splunk Code Injection via custom dashboard leading to RCE, Splunk Enterprise KV Store Incorrect… v6.4.0 · Aug 2026 · source · release history
Automated incident response playbooks shipped Provides executable workflows (playbooks) for automated incident response actions, such as Active Directory account management and Jira ticket integration. 20 releases · first seen Jan 2022

Also counts toward: Ticketing integration

release 20 total

  • New CrowdStrike EDR Playbook Pack for Splunk SOAR — 9 playbooks enabling automated investigation and response via CrowdStrike Falcon OAuth API, covering device isolation, network restore, process termination, file collection/eviction/restore, executable denylisting, endpoint analysis, and device info retrieval. v5.9.0 · Jul 2025 · source · release history
  • Adds MS Graph for Office 365 Message Eviction playbook v4.26.0 · Mar 2024 · source · release history
  • Adds MS Graph for Office365 Search and Purge playbook v4.26.0 · Mar 2024 · source · release history
  • Adds MS Graph for Office 365 Message Restore playbook v4.26.0 · Mar 2024 · source · release history
  • Adds MS Graph for Office365 Search and Restore playbook v4.26.0 · Mar 2024 · source · release history
  • Adds G Suite for Gmail Message Eviction playbook v4.26.0 · Mar 2024 · source · release history
Lookup generation and metadata configuration verified Provides command-line arguments to control the generation, output, metadata handling, and filtering of detection content and lookup files. 6 other sources · first seen Sep 2026

Also counts toward: Command-line interface, CSV data export

command line

  • --modified-date — Metadata modification date in YYYY-MM-DD format. Default: today. v6.6.0 · Sep 2026 · command-line history
  • --dry-run — Write generated CSV to stdout instead of --output. v6.6.0 · Sep 2026 · command-line history
  • --no-metadata-update — Do not bump lookup metadata when --output changes. v6.6.0 · Sep 2026 · command-line history
  • --rmf-lookup v6.6.0 · Sep 2026 · command-line history
  • --metadata v6.6.0 · Sep 2026 · command-line history
  • --include-deprecated — Include detections under detections/deprecated and detections with deprecated status. v6.6.0 · Sep 2026 · command-line history
Detection testing infrastructure shipped Provides capabilities to ingest test data into custom or isolated indexes and view audit dashboards, enabling the validation of detections against specific data formats. 4 releases · first seen Aug 2022

release

  • New datasource testing in contentctl v4.4.5 validates detection compatibility when new Technology Add-ons (TAs) are introduced. v4.43.0 · Nov 2024 · source · release history
  • Adds ESCU - AppLocker dashboard for auditing Windows AppLocker events v4.30.0 · Apr 2024 · source · release history
  • Adds new input macro sourcetype="kube:container:falco" for Falco data ingestion. v4.23.0 · Jan 2024 · source · release history
  • Adds consolidated requirements.txt file for contentctl and docker detection testing. v3.48.0 · Aug 2022 · source · release history
Content repository initialization and inspection shipped Provides commands to initialize a new detection content repository from scratch, inspect existing content structure, and deploy detected content to cloud environments. 1 release · 3 other sources · first seen Aug 2022

Also counts toward: Command-line interface

release

  • Adds init, inspect, and cloud_deploy subcommands to the contentctl project v3.47.0 · Aug 2022 · source · release history

example

  • Initialize a new repository from scratch using the contentctl CLI. contentctl init v3.47.0 · Aug 2022 · source
  • Deploy a custom Splunk application to Splunk Cloud. contentctl cloud_deploy v3.47.0 · Aug 2022 · source
  • Validate and build Splunk content app contentctl-ng build
YAML detection formatting verified Formats detection YAML files using a configurable yamlfmt binary, keeping detection content consistently styled. 1 release · 2 other sources · first seen Oct 2022

release

  • Removes the slim dependency from Github Actions workflows v3.50.0 · Oct 2022 · source · release history

command line

YAML detection validation verified Validates YAML detection files against a specified OpenAPI schema, with configurable input paths and optional colored output. 3 other sources · first seen Jan 2026

command line

  • paths — Paths to YAML files or directories to validate (default: detections/) v5.23.0 · Mar 2026 · command-line history
  • --no-color — Disable colored output v5.23.0 · Mar 2026 · command-line history
  • --schema — Path to the OpenAPI YAML schema file v5.20.0 · Jan 2026 · command-line history
Detection content version diffing verified Accepts archives of two content versions to compare or diff detection content between releases. 2 other sources · first seen Oct 2026

command line

Detection naming constraint enforcement shipped Enforces a maximum character limit on detection names to ensure consistency and compatibility with downstream systems. 2 releases · first seen Mar 2022

release

  • Correlation rule labels now use the ESCU - RIR - <rule_name> - Rule format instead of the previous naming convention. v3.49.0 · Sep 2022 · source · release history
  • Enforces a max length of 67 characters for detection names. v3.37.0 · Mar 2022 · source · release history
Cisco AI Defense threat operations dashboard shipped Provides an alpha dashboard for reviewing AI runtime activity, enforcement outcomes, risky behavior, sensitive data matches, and activity broken down by application and model. 1 release · first seen Oct 2026

release

  • Introduces the Cisco AI Defense Threat Operations dashboard (alpha) for reviewing runtime activity, enforcement outcomes, risky behavior, sensitive data matches, and activity by application and model. v6.9.0 · Oct 2026 · source · release history
UI navigation and dashboard access shipped Provides interactive navigation elements and dropdown menus within the tool interface to facilitate quick access to dashboards and core functionality. 1 release · first seen Feb 2025

release

  • Adds a dashboard dropdown to the navigation bar in the Splunk Security Content UI. v5.1.0 · Feb 2025 · source · release history
RMM alert content dashboard shipped Provides a dedicated dashboard for auditing and monitoring detection content related to Remote Monitoring and Management (RMM) software. 1 release · first seen Aug 2024

release

  • New RMM Software Tracking Dashboard for auditing and monitoring Remote Monitoring and Management alert content. v4.39.0 · Aug 2024 · source · release history
Detection content modification shipped Provides functionality to programmatically modify or transform detection content. 1 release · first seen Jun 2023

release

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Splunk Security Content, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Splunk Security Content puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Coverage

Missing something? Tell us

What Splunk Security Content connects to, runs on and detects, read from its release notes and docs. So far: 6 new detections, 4 updated detections, 1 updated supported platform, 1 new integration, 1 updated integration.

Show

13 changes, tracked since Oct 22, 2026.

  • Oct 282026

    new Cisco Secure Firewall PHP2Shell detections

    With Cisco Secure Firewall - PHP2Shell Exploitation Attempt, Cisco Secure Firewall - PHP2Shell Serialized Payload Activity, Cisco Secure Firewall - PHP2Shell Suspicious Upload Activity

    Added three analytics based on Threat Defense Intrusion Events: one detects serialized payload activity, one identifies suspicious upload activity, and one correlates multiple PHP2Shell-related intrusion indicators against the same destination.

    v6.9.2 Source ↗

  • Oct 282026

    new Suricata PHP2Shell detections

    With Large HTTP POST Request Failure or Missing Response - Suricata, PHP Opening Tag in Upload Filename - Suricata, Serialized PHP Token in Upload Filename - Suricata

    Added analytics for large HTTP POST requests that receive an HTTP 500 response or have no response status, PHP opening tags in upload filenames, and serialized PHP tokens in upload filenames.

    v6.9.2 Source ↗

  • Oct 282026

    updated PHP2Shell endpoint and web detections updated

    No new names. Restates the 7 already listed.

    Updated Analytics - [7]

    v6.9.2 Source ↗

  • Oct 282026

    updated Apache data source support

    Covers 7: apache:access:combined, apache:access:kv, apache:access:json, apache:access, access_combined, apache:error and 1 more

    Updated the Apache access and error data sources with Splunk Add-on for Apache Web Server fields and supported sourcetypes. Expanded the Apache macros to recognize the supported sourcetypes, with apache:access:combined identified as the currently supported access format for the detection.

    v6.9.2 Source ↗

  • Oct 282026

    updated Windows shell macro updated to detect renamed shell binaries

    Adds wscript.exe, cscript.exe, mshta.exe, Command Prompt, Windows PowerShell, PowerShell ISE, PowerShell 7. 7 in all.

    Updated Windows shell macro: Removed wscript.exe, cscript.exe, and mshta.exe to reduce unrelated matches. Added original_file_name checks for Command Prompt, Windows PowerShell, PowerShell ISE, and PowerShell 7 so renamed shell binaries remain detectable.

    v6.9.2 Source ↗

  • Oct 282026

    updated Linux shell macro expanded with additional shell variants

    With ash, mksh

    Expanded Linux shell macro: Added ash and mksh to cover additional shell variants used in Alpine and BusyBox environments.

    v6.9.2 Source ↗

How we count

Read from 2 of 140 release notes and docs updates we hold for Splunk Security Content. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Splunk Security Content's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

140 entries

  1. October 20263
  2. September 20263
  3. August 20262
  4. July 20262
  5. June 20263
  6. May 20261
  7. April 20262
  8. March 20262
  9. February 20262
  10. January 20261
  11. December 20251
  12. November 20251
  13. October 20252
  14. September 20253
  15. August 20253
  16. July 20252
  17. June 20252
  18. May 20252
  19. April 20252
  20. March 20251
  21. February 20251
  22. January 20251
  23. December 20241
  24. November 20241
  25. October 20241
  26. September 20242
  27. August 20242
  28. July 20242
  29. June 20242
  30. May 20242
  31. April 20242
  32. March 20243
  33. January 20242
  34. December 20232
  35. November 20232
  36. October 20231
  37. September 20231
  38. August 20232
  39. June 20231
  40. May 20233
  41. April 20232
  42. March 20233
  43. February 20232
  44. January 20232
  45. December 20221
  46. November 20222
  47. October 20222
  48. September 20221
  49. August 20222
  50. July 20222
  51. June 20222
  52. May 20222
  53. April 20221
  54. March 20222
  55. February 20221
  56. January 20223
  57. December 20212
  58. September 20212
  59. August 20213
  60. July 20211
  61. June 20211
  62. May 20212
  63. April 20212
  64. March 20213
  65. February 20211
  66. January 20213
  67. December 20201
  68. November 20201
  69. October 20201
  70. September 20201
  71. August 20202
  72. July 20201
  73. June 20203
  74. April 20201
  75. March 20201
  76. February 20201
  77. January 20201
  78. December 20191
  79. November 20191
    Show
    Coverage in all entries

    140 entries

    Project health

    Issue, contributor and maintainer activity in splunk/security_content, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 49 +5 vs prior 12 months
    2. Maintainers 10 +8 joined · −7 left, last 12 months
    3. Bus factor 5 committers behind half the commits
    4. Community-filed 98% of issues opened, last 12 months
    5. Median time to close 6.3 days first maintainer reply 10 days
    6. Open backlog 6 of 379 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 6
    3. Contributors / month 8
    4. Commits / month 28
    5. Stars 1,696
    Issue themes, last 12 months
    • bugs 74%
    • features 12%
    • other 14%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Threat coverage

    Content for the last year of exploited CVEs and attack reports.

    Splunk Security Content has content for 510 of the 982 threats tracked in the last year, 30 of them exact.

    exact30names the CVE
    related480names the technique or product
    tracked982threats in the last year

    See the threats, and how similar tools compare threat by threat, with Researcher and Business.

    See plans → Already subscribed? Sign in →

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →