Hi, I was wondering if it is possible to incorporate threat intelligence data without using enterprise security?
I've done it using Splunk ES, and it was pretty easy. But what if I don't have ES and only Splunk Core in my environment?
Hi @elend
Yes, you can incorporate threat intelligence data into Splunk Core without using Enterprise Security (ES), while ES provides built-in functionalities (like the Threat Intelligence Framework and notable event correlation), in Splunk Core you willneed to manually onboard and implement threat intel feeds. You could do this a number of ways:
Ingest: Import your threat intelligence feeds (such as CSV, STIX, TAXII, or public IoCs) into Splunk as a new index (e.g., threatintel) from a forwarder that has access to the threat intel feeds.
Lookups: Load feed data as lookups either manually or using an API mechanism.
Scheduled Inputs: Use an existing (Splunkbase) or custom modular inputs to pull threat data from external sources and index it in Splunk.
Then you will need to utilize the onboarded Threat intel data, Use SPL to search and correlate your indexed logs with threat indicators. e.g. using lookup commands to match source IPs, domains, or hashes in your events against those in your threat intel lookup. You can then have alerts based on matches between your event data and the imported threat indicators.
This obviously requires more manual effort than the out of the box ES implementation but can produce a fully functional threat intel processing in Splunk. You won’t have the automated enrichment, risk scoring, or notable events provided by ES, but you can replicate many basic use cases with SPL and alerts if you're able/willing to put it together,.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
thankyou for the response. do you have some techinal reference about that points? i want to try it
Since there is no ready-made full framework for this, there is no reference since you will have to zip-tie and duct-tape it yourself.
There are some addons and apps which can ingest specific kinds of data (typically they are made by TI service vendors; and their quality... vary greatly, to be diplomatic about it) but for other ones you will have to start from scratch and implement everything on your own.
After all, it's not that you're paying for ES for nothing 😉
Hi @elend
Ultimately this really depends on what sources you are using for your threat intel, e.g. do they provide an API? Is it Internal? Does a Splunkbase app already exist for the vendor's feed?
This will drive the best approach and then lead to the technical implementation, but will always require a lot more manual work than using Enterprise Security, which is more of a turnkey solution for what you are trying to produce.
Because of the complexity involved here and the amount of unknowns, this would typically be something that you would need to consult with Splunk or a Splunk Partner to produce, unless you already have the technical abilities in-house. Whilst we could provide some example SPL, this would just be boilerplate and not really transferable to your environment without knowing a lot more information about your data, volumes, sources, TTP feeds etc
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing
Hi @elend
Yes, you can incorporate threat intelligence data into Splunk Core without using Enterprise Security (ES), while ES provides built-in functionalities (like the Threat Intelligence Framework and notable event correlation), in Splunk Core you willneed to manually onboard and implement threat intel feeds. You could do this a number of ways:
Ingest: Import your threat intelligence feeds (such as CSV, STIX, TAXII, or public IoCs) into Splunk as a new index (e.g., threatintel) from a forwarder that has access to the threat intel feeds.
Lookups: Load feed data as lookups either manually or using an API mechanism.
Scheduled Inputs: Use an existing (Splunkbase) or custom modular inputs to pull threat data from external sources and index it in Splunk.
Then you will need to utilize the onboarded Threat intel data, Use SPL to search and correlate your indexed logs with threat indicators. e.g. using lookup commands to match source IPs, domains, or hashes in your events against those in your threat intel lookup. You can then have alerts based on matches between your event data and the imported threat indicators.
This obviously requires more manual effort than the out of the box ES implementation but can produce a fully functional threat intel processing in Splunk. You won’t have the automated enrichment, risk scoring, or notable events provided by ES, but you can replicate many basic use cases with SPL and alerts if you're able/willing to put it together,.
🌟 Did this answer help you? If so, please consider:
Your feedback encourages the volunteers in this community to continue contributing