Getting Data In

Not receiving CrowdStrike Intel Indicators events

damode
Motivator

Followed this guide properly but not getting any Falcon Indicator events in Splunk and getting the following message in log file

 

 

2020-10-16 14:37:04,341 INFO pid=488 tid=MainThread file=splunk_rest_client.py:_request_handler:105 | Use HTTP connection pooling
2020-10-16 14:37:05,289 INFO pid=488 tid=MainThread file=base_modinput.py:log_info:295 | Authentication status code: 201
2020-10-16 14:37:05,289 INFO pid=488 tid=MainThread file=base_modinput.py:log_info:295 | Successfully Retrieved Authentication Token
2020-10-16 14:37:05,563 ERROR pid=488 tid=MainThread file=base_modinput.py:log_error:309 | Get error when collecting events.
Traceback (most recent call last):
  File "/opt/splunk/etc/apps/TA-crowdstrike-intel-indicators/bin/ta_crowdstrike_intel_indicators/aob_py2/modinput_wrapper/base_modinput.py", line 128, in stream_events
    self.collect_events(ew)
  File "/opt/splunk/etc/apps/TA-crowdstrike-intel-indicators/bin/crowdstrike_intel_indicators.py", line 77, in collect_events
    input_module.collect_events(self, ew)
  File "/opt/splunk/etc/apps/TA-crowdstrike-intel-indicators/bin/input_module_crowdstrike_intel_indicators.py", line 157, in collect_events
    indicators = intel['resources']
KeyError: 'resources'

 

Please advise. Thanks.

 

Labels (1)
0 Karma

MaverickT
Communicator

Which "CloudStrike cloud environment" do you have selected? In my case it didn't work until "EU Cloud" was selected. After switching to "US Commercial" it started working.

Currently using EU Cloud is not beneficiary, since all requests are (at least currently) redirected to US commercial anyway.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...