Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sample Json files for expected Input format or Any Examples on how to use json as input ? #1546

Open
satadda opened this issue Jan 17, 2025 · 3 comments

Comments

@satadda
Copy link

satadda commented Jan 17, 2025

I am trying to use hayabusa with a json input file but didn't any example or what is expected format of the json? I see lot of examples/samples for evtx files. Any sample json files?

@satadda satadda changed the title Example on how to use json as input? Sample Json files for expected Input format or Any Examples on how to use json as input ? Jan 17, 2025
@fukusuket
Copy link
Collaborator

@satadda The following JSON can be used as a sample :)

@satadda
Copy link
Author

satadda commented Jan 19, 2025

Thanks @fukusuket. This helped me to some extent.

I am new to this threating hunting and trying to understand how hayabusa works. Do all fields as in the splunk output json required for successful analysis? If not is there any list of mandatory fields?

The input data I have is in csv format with following columns and events in the rows:

Timestamp DeviceName InitiatingProcessParentCreationTime InitiatingProcessId InitiatingProcessFileName InitiatingProcessCommandLine ProcessCreationTime ProcessId FileName ProcessCommandLine

I am trying to convert this csv formatted data into JSON format to use hayabusa for analysis. Do you think this is the right way to go? Let me know if you have any suggestions on this

@fukusuket
Copy link
Collaborator

@satadda
Currently, JSON exported from the Splunk REST API is partially supported, but probably not for other output formats. Therefore, at this point, exporting JSON from the REST API is the only way to go!
#1083 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants