Tell us your source SOAR platform and the decision you need to make. An initial discussion can define the right assessment scope.
Service tabs · swipe to explore →
Splunk SOAR Governance Check
Splunk SOAR teams also need a regular service interval. SPG reviews available app, playbook, dependency, and risk evidence before a connector or workflow change reaches production.
What is installed, what depends on it, and what might break?
Discuss this service
What this inspection covers
The SOAR governance process for apps, playbooks, and change evidence.
- Inventory the selected Splunk SOAR apps and playbooks.
- Review app and connector dependencies, vulnerability signals, and workflow findings where evidence exists.
- Prioritize changes for the SOAR owner and approval team.
A scoped readiness view and tenant-specific findings report.
Findings reflect available source data; a clean report is not a guarantee that a production change is risk-free.
Explore the evidence and report options
Choose the platform or report filters below when you are ready to inspect the technical detail.
Service scope
Selected: splunk_soar. Readiness reports use the current tenant's data and show gaps when no evidence is available.
Evidence report and filters
The screen, JSON, and PDF use the same service scope and filters. Sign in to download tenant evidence.
Workflow
For technical teams · API / Delivery Hooks
The existing authenticated SPG API accepts request_type=service_report with this service and platform scope. Browser downloads use the same report builder.
Tell us your source SOAR platform and the decision you need to make. An initial discussion can define the right assessment scope.