02-14-2018 06:57 AM - edited 02-14-2018 06:58 AM
Hi all,
In my environment, some developers use NuGet in Visual Studio, and in certain cases, commands will call out and download PowerShell scripts.
Obviously I want generally to block PowerShell script downloads, but in special cases I need to allow them when they come from specific places. Unfortunately for my devs, since we wholesale block .ps1 files, sometimes their NuGet package processes end up causing the traffic to hit the Block-Continue page on our firewalls, which prevents their package downloads from completing properly.
What is considered best practice in this type of scenario? New Policy object(s)?
