Splunk SOAR

Getting fields from artifact in playbook

chris997
Engager

Hello! This is probably a simple question but I've been kind of struggling with it. I'm building out my first playbook which triggers off of new artifacts. The artifacts include fields for: type, value, tag. What I'm trying to do is have those fields from the artifact passed directly into a custom code block in my playbook. How do I go about accessing those fields?

I've tried using phantom.collect2(container=container, datapath=["artifact:FIELD_NAME*"]) in the code block but it doesn't return anything. I thought maybe I needed to setup custom fields to define type, value and tag in the custom fields settings, but that didn't change anything either. Any help would be appreciated, thank you!

Labels (1)
0 Karma
1 Solution

chris997
Engager

Thanks! I initially tried that call and  wasn't working for me but I ended up realizing it was because I was adding my fields to the "Custom fields" and not the "CEF" settings.

After speaking with the Splunk team it sounds like Custom fields are meant for reference within SOAR, like adding some information into the HUD, whereas CEF is what's actually used to access the artifact data.

I appreciate your reply

View solution in original post

0 Karma

Ar_on88
New Member

Try this:

phantom.collect2(container=container, datapath=["artifact:*.cef.FIELD_NAME"])
0 Karma

chris997
Engager

Thanks! I initially tried that call and  wasn't working for me but I ended up realizing it was because I was adding my fields to the "Custom fields" and not the "CEF" settings.

After speaking with the Splunk team it sounds like Custom fields are meant for reference within SOAR, like adding some information into the HUD, whereas CEF is what's actually used to access the artifact data.

I appreciate your reply

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...