Who’s afraid of PowerShell security?

Hello together,

many people are afraid of using Powershell remoting, because they think it is very unsafe.

Just take a moment and read this:

The improvements in WMF 5.0 (or WMF 4.0 with KB3000850) make PowerShell the worst tool of choice for a hacker when you enable script block logging and system-wide transcription. Hackers will leave fingerprints everywhere, unlike popular CMD utilities. For this reason, PowerShell should be the only tool you allow for remote administration. These features allow you to answer the classic questions who, what, when, where, and how for activities on your servers.

Technet Link



PowerShell Remoting Security Considerations

New security documentation from the PowerShell team. This is a start, and it will continue to be updated. Give this link to your InfoSec people who need more information.

https://msdn.microsoft.com/en-us/powershell/scripting/setup/winrmsecurity

PowerShell ♥ the Blue Team

Whitepaper by Lee Holmes “Scripting Security and Protection Advances in Windows 10” (PowerShell 5).

Give this to your InfoSec people, your manager, and your grandmother. Then implement it.

https://blogs.msdn.microsoft.com/powershell/2015/06/09/powershell-the-blue-team/


Best regards,

David

SCCM 1606 – UserVoice

Hi everyone,

SCCM 1606 with its new features has been announced:

Link Here

In a short:

  • ConfigMgr as a managed installer for easier application whitelisting on Windows 10
  • Cloud Proxy Service
  • Grace period for application and software update deployments
  • Multiple device management points for Windows 10 Anniversary Edition devices
  • Intune: Device categories

Do you like it?
Don´t forget to share thoughts via the UserVoice:
https://configurationmanager.uservoice.com/

Best regards,

David