--- name: building-threat-intelligence-enrichment-in-splunk-8e3886a7a063 description: Build automated IOC enrichment pipelines in Splunk Enterprise Security by ingesting threat feeds into KV Store collections and correlating them against security events via lookup tables, modular inputs, and the Threat Intelligence Framework. Use when wiring threat intel into Splunk correlation searches to flag IOC matches and cut SOC triage time. domain: cybersecurity subdomain: soc-operations tags: - splunk - threat-intelligence - enrichment - ioc - lookup - siem - soc - enterprise-security version: '1.0' author: mahipal license: Apache-2.0 nist_csf: - DE.CM-01 - DE.AE-02 - RS.MA-01 - DE.AE-06 mitre_attack: - T1071 - T1105 - T1041 --- # Building Threat Intelligence Enrichment in Splunk ## Overview Splunk's Threat Intelligence Framework in Enterprise Security enables SOC teams to automatically correlate indicators of compromise (IOCs) against security events. The framework ingests threat feeds, normalizes indicators into KV Store collections, and uses lookup-based correlation searches to flag matching events. Splunk Threat Intelligence Management centralizes collection, normalization, and enrichment from multiple sources, reducing triage time by providing analysts with immediate context. ## When to Use - When deploying or configuring building threat intelligence enrichment in splunk 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 Security (ES) 7.x or later - Threat Intelligence Management add-on or Threat Intelligence Framework - API keys for external threat intelligence feeds (MISP, OTX, VirusTotal, AbuseIPDB) - KV Store enabled and properly configured - Admin access for modular input configuration ## Threat Intelligence Framework Architecture ``` External TI Sources (STIX/TAXII, CSV, API) | v Modular Inputs (download and parse feeds) | v KV Store Collections (normalized IOC storage) |-- ip_intel |-- domain_intel |-- file_intel |-- url_intel |-- email_intel | v Threat Intelligence Lookups | v Correlation Searches (match events against IOCs) | v Notable Events (enriched with TI context) ``` ## Configuring Threat Intelligence Sources ### STIX/TAXII Feed Integration ```conf # inputs.conf - TAXII feed configuration [threatlist://taxii_feed_example] description = TAXII 2.1 Threat Feed type = taxii url = https://threatfeed.example.com/taxii2/ collection = threat-indicators-v21 polling_interval = 3600 api_key = disabled = false ``` ### CSV-Based Threat List ```conf # inputs.conf - CSV threat list [threatlist://custom_blocklist] description = Internal threat blocklist type = csv url = https://internal.company.com/threat-feeds/blocklist.csv polling_interval = 1800 disabled = false ``` ### Custom Modular Input for API-Based Feeds ```python # bin/threatfeed_otx.py - OTX AlienVault feed collector import json import sys import requests from splunklib.modularinput import Script, Scheme, Argument, Event class OTXFeedInput(Script): def get_scheme(self): scheme = Scheme("OTX AlienVault Feed") scheme.description = "Collects IOCs from AlienVault OTX" scheme.use_external_validation = False scheme.streaming_mode = Scheme.streaming_mode_xml api_key_arg = Argument("api_key") api_key_arg.data_type = Argument.data_type_string api_key_arg.required_on_create = True scheme.add_argument(api_key_arg) pulse_days_arg = Argument("pulse_days") pulse_days_arg.data_type = Argument.data_type_number pulse_days_arg.required_on_create = False scheme.add_argument(pulse_days_arg) return scheme def stream_events(self, inputs, ew): for input_name, input_item in inputs.inputs.items(): api_key = input_item["api_key"] pulse_days = int(input_item.get("pulse_days", 30)) headers = {"X-OTX-API-KEY": api_key} url = f"https://otx.alienvault.com/api/v1/pulses/subscribed?modified_since={pulse_days}d" try: response = requests.get(url, headers=headers, timeout=60) response.raise_for_status() data = response.json() for pulse in data.get("results", []): for indicator in pulse.get("indicators", []): event = Event() event.stanza = input_name event.data = json.dumps({ "indicator": indicator["indicator"], "type": indicator["type"], "pulse_name": pulse["name"], "pulse_id": pulse["id"], "description": indicator.get("description", ""), "created": indicator.get("created", ""), "threat_source": "OTX", "confidence": pulse.get("adversary", "unknown"), }) ew.write_event(event) except requests.RequestException as e: ew.log("ERROR", f"OTX feed collection failed: {str(e)}") if __name__ == "__main__": sys.exit(OTXFeedInput().run(sys.argv)) ``` ## Building Enrichment Lookups ### KV Store Collection Configuration ```conf # collections.conf [ip_threat_intel] field.ip = string field.threat_type = string field.confidence = number field.source = string field.description = string field.first_seen = time field.last_seen = time field.severity = string [domain_threat_intel] field.domain = string field.threat_type = string field.confidence = number field.source = string field.whois_registrar = string field.whois_created = string [file_hash_intel] field.file_hash = string field.hash_type = string field.malware_family = string field.confidence = number field.source = string field.detection_names = string ``` ### Lookup Table Definitions ```conf # transforms.conf [ip_threat_intel_lookup] external_type = kvstore collection = ip_threat_intel fields_list = ip, threat_type, confidence, source, description, severity [domain_threat_intel_lookup] external_type = kvstore collection = domain_threat_intel fields_list = domain, threat_type, confidence, source [file_hash_intel_lookup] external_type = kvstore collection = file_hash_intel fields_list = file_hash, hash_type, malware_family, confidence, source ``` ## Enrichment Correlation Searches ### IP-Based Threat Intelligence Correlation ```spl | tstats summariesonly=true count from datamodel=Network_Traffic where All_Traffic.action=allowed by All_Traffic.src_ip, All_Traffic.dest_ip, All_Traffic.dest_port, _time span=5m | rename "All_Traffic.*" as * | lookup ip_threat_intel_lookup ip as dest_ip OUTPUT threat_type, confidence, source as ti_source, severity as ti_severity | where isnotnull(threat_type) | lookup asset_lookup ip as src_ip OUTPUT asset_name, asset_owner, asset_priority | eval urgency=case( ti_severity=="critical" AND asset_priority=="critical", "critical", ti_severity=="high" OR asset_priority=="critical", "high", ti_severity=="medium", "medium", true(), "low" ) | eval description="Connection from ".src_ip." (".asset_name.") to known malicious IP ".dest_ip." (".threat_type.") - Source: ".ti_source ``` ### Domain-Based Threat Intelligence Correlation ```spl index=dns sourcetype=stream:dns query_type=A OR query_type=AAAA | lookup domain_threat_intel_lookup domain as query OUTPUT threat_type as domain_threat, confidence as domain_confidence, source as ti_source | where isnotnull(domain_threat) AND domain_confidence > 70 | stats count dc(src_ip) as unique_sources values(src_ip) as source_ips by query, domain_threat, ti_source | eval severity=case(domain_confidence > 90, "critical", domain_confidence > 70, "high", true(), "medium") | eval description="DNS queries to malicious domain ".query." from ".unique_sources." hosts - Threat: ".domain_threat ``` ### File Hash Correlation ```spl index=endpoint sourcetype=sysmon EventCode=1 | lookup file_hash_intel_lookup file_hash as Hashes OUTPUT malware_family, confidence as hash_confidence, source as ti_source | where isnotnull(malware_family) | stats count values(ParentCommandLine) as parent_commands by Computer, User, Image, malware_family, ti_source | eval severity="critical" | eval description="Known malware ".malware_family." executed on ".Computer." by ".User." - Binary: ".Image ``` ## Multi-Source Enrichment Pipeline ```spl index=firewall sourcetype=pan:traffic action=allowed | eval indicators=mvappend(src_ip, dest_ip) | mvexpand indicators | lookup ip_threat_intel_lookup ip as indicators OUTPUT threat_type as ip_threat, confidence as ip_confidence, source as ip_ti_source | lookup geo_ip_lookup ip as indicators OUTPUT country, city, latitude, longitude | lookup whois_lookup ip as indicators OUTPUT org as ip_org, asn as ip_asn | where isnotnull(ip_threat) | stats count values(ip_threat) as threat_types values(ip_ti_source) as intel_sources values(country) as countries values(ip_org) as organizations latest(_time) as last_seen earliest(_time) as first_seen by src_ip, dest_ip, dest_port | eval enrichment_context="Threat: ".mvjoin(threat_types, ", ")." | Geo: ".mvjoin(countries, ", ")." | Org: ".mvjoin(organizations, ", ") ``` ## Threat Intelligence Dashboards ### IOC Coverage Statistics ```spl | inputlookup ip_threat_intel_lookup | stats count by source, threat_type | sort -count | head 20 ``` ### Feed Freshness Monitoring ```spl | inputlookup ip_threat_intel_lookup | eval age_days=round((now() - strptime(last_seen, "%Y-%m-%dT%H:%M:%S")) / 86400, 0) | stats count avg(age_days) as avg_age_days max(age_days) as max_age_days by source | eval status=case(avg_age_days > 30, "STALE", avg_age_days > 7, "AGING", true(), "FRESH") ``` ## References - [Splunk Threat Intelligence Framework Documentation](https://help.splunk.com/en/splunk-enterprise-security-8/administer/8.2/threat-intelligence/overview-of-threat-intelligence-in-splunk-enterprise-security) - [Splunk Lantern - Threat Intelligence Enrichment](https://lantern.splunk.com/Security/UCE/Guided_Insights/Threat_intelligence) - [Integrated Intelligence Enrichment - Splunk Blog](https://www.splunk.com/en_us/blog/security/integrated-intelligence-enrichment-with-threat-intelligence-management.html) - [Cisco Talos Threat Intelligence in Splunk](https://www.splunk.com/en_us/blog/security/cisco-talos-threat-intelligence-splunk-security.html) --- Source attribution: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/building-threat-intelligence-enrichment-in-splunk/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/building-threat-intelligence-enrichment-in-splunk/SKILL.md Attribution basis: Source repository record Fields of work: Data & Analytics, Development & Engineering, Operations Roles: Business Process Analyst, Data Analyst, DevOps / SRE, ML / AI Engineer, Security Engineer Specialties: API, Backend Tools: Tool not specified Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 4590255f54a8a74ff9a5e168966c2ab5eccd199443d2fee7d22dbeb5b43ad358