Splunk SOAR

Integration HTTP https://splunkbase.splunk.com/app/5904

marq198
Observer

Hi, 

I ran the HTTP splunk integrations with https://splunkbase.splunk.com/app/5904 
I have a problem sending a put request to splunk ES according to the
https://docs.splunk.com/Documentation/ES/latest/API/NotableEventAPIreference#.2Fservices.2Fnotable_update 

I don't know what the body and header should look like, the connection works for me because it returns that I have access, Status Code: 400 Data from server: \"ValueError: One of comment, newOwner, status, urgency, disposition is required".
\
Anyone encountered this probleme ?

Labels (1)
0 Karma

phanTom
SplunkTrust
SplunkTrust

@marq198 you know the Splunk app has an "update_notable" action?

You say you don't know what the header or body should look like? I would ask shy you're trying this without that information, it's kind of important 😁.

See if you can use the Splunk app otherwise I would recommend reading up on how to interact with the Splunk API and then you should be able to make it work: https://docs.splunk.com/Documentation/Splunk/9.2.0/RESTTUT/RESTTutorialIntro 

-- Hope this helps, if so consider leaving some Karma. Even better is if this fixed your issue, that you mark as a solution for others to find. Happy SOARing!! ---
0 Karma

marq198
Observer

I know how the header and body should look like, while in this integration it does not work, did you use it ?

according to the SOAR integration documentation, it can be delivered in json format so it provides such a format

body:

{"ruleUIDs":"xxx","newOwner":"xxx","comment": "test","status":"5","disposition":"disposition:2"}

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