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!

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...

Get the T-shirt to Prove You Survived Splunk University Bootcamp

As if Splunk University, in Las Vegas, in-person, with three days of bootcamps and labs weren’t enough, now ...

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...