Splunk Configuration Instructions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 274
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We're trying to try out this tool, which looks like it could be very useful. We have data in a Splunk instance, which our CASCADE server is successfully authenticating against.
I understand that the next step for us is to normalise our sensor data using the CAR data model. However this appears to be easier said than done, because:
- Our Splunk instance doesn't have the CAR Data Model created.
- Our Splunk instance doesn't have any of the tags created which are used by the CASCADE server. (See example query below)
- Our Splunk instance also doesn't understand the 'export' command, which I assume is a custom search command. (See example query below)
Example query:
tag=dm-process-create ( exe="sc.exe" AND command_line="* start *") | fields command_line current_directory duration exe fqdn hostname image_path integrity_level md5_hash parent_command_line parent_exe parent_image_path pid ppid sha1_hash sha256_hash sid terminal_session_id user | export add_timestamp=f add_offset=t segmentation=none
Are we missing something here - do we need to manually create the data models and tags, or are configuration scripts / a Splunk app available? What about the missing 'export' command?
Thank you in advance.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files or tests; start by reviewing the project's existing setup documentation and the Splunk integration entry points. Use the example query and its missing CAR data model, tags, and export command as the scope. Done means documenting the required Splunk configuration or clearly identifying the available setup resources.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100