Welcome to the Splunk> SOAR Community! SOAR is Splunk's premier Security Automation, Orchestration, and Response ("SOAR") platform. With it, our customers can automate entire or partial workflows for their employees across an infinite number of use-cases.
This GitHub organization represents our efforts to open-source our SOAR Apps so our customers can look at how our code works, make improvements, and generally build a stronger community through the free exchange of ideas.
For more information on SOAR, please have a look at our pages:
If you'd like to chat with fellow Splunk SOAR users, fill out our splunk-usergroups registration form and you'll be invited to our Slack community. Check out channels like #soar, #soar_app_dev, and #soar-app-changes.
If you've found a problem with an app but don't want to contribute a fix, that's ok! All you need to do is go to the Issues section of the app repo and click 'New Issue'. The page that appears will show our convenient issue templates. However, if the app doesn't have an Issues page, that means you need to submit a bug report via Splunk Support.
All you have to do is fill out the form...
...and our community will be able to help review and propose fixes.
Of course, you should definitely check if there is already an open issue and if so, add a thumbs-up reaction to it for visiblity.
Have a feature or an app you'd like to see in SOAR? Head over to the Splunk Ideas portal to make your voice heard! Voting and sharing new ideas is a great way for us to see what's in demand.
If you would like to contribute to our Apps directly, please have a look at our Contribution Guide
All SOAR Apps in this GitHub organization are licensed under the Apache 2.0 license. Please see LICENSE file and CONTRIBUTING documentation for further details.
Certain SOAR Apps may include third-party open source subcomponents with separate copyright notices and license. Your use of the source code for these subcomponents is subject to the terms and conditions of the corresponding license(s) contained in the respective subcomponent directory or source file(s).
Some repositories within this organization include binary (non-source code) blobs obtained from https://pypi.org. These files are subject to separate license terms and conditions, which can be found in the corresponding project subdirectory located therein.