Discover, share, and install apps and add-ons with the Splunk community on Splunkbase. Publish your own or add others to your Splunk platform instance.
Streamline your security operations with a SOAR system that integrates orchestration, playbook automation, and case management to enhance threat response.
Access and share apps and add-ons with the Splunk community on Splunkbase. Publish your own apps, or download and install others on your Splunk platform instance.
The Machine Agent must be installed running on the host on which the script executes. To see a list of installed Machine Agents for your application, click View machines with machine-agent installed in the bottom left corner of the remediation script configuration window.
To be able to run remediation scripts, the Machine Agent must be connected to a SaaS Controller via SSL. Remediation script execution is disabled if the Machine Agent connects to a SaaS Controller on an unsecured (non-SSL) HTTP connection.
The Machine Agent and the APM agent must be on the same host.
The Machine Agent OS user must have full permissions to the script file and the log files generated by the script and/or its associated child processes.
The script must be placed in <agent install directory>\local-scripts .
The script must be available on the host on which it executes.
Processes spawned from the scripts must be daemon processes.