All Apps and Add-ons

How to use Scripted Inputs in Splunk with AllSigned Execution Policy

hvandenb
Path Finder

We’ve found that using scripted inputs helps us to capture specific sources in Windows through the use of PowerShell. Powershell can introduce security complications when execution on machines is not managed, specifically in an Enterprise. To enhance this security we tend to choose a script execution policy that requires the scripts to be signed.

By default Splunk Powershell scripts are not signed so we wrote this article to explain how we did it.

jcoates_splunk
Splunk Employee
Splunk Employee

Thanks for posting this!

0 Karma
Get Updates on the Splunk Community!

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...