Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 258/260 feeds/APIs · 416/439 docs · checked 14:46 UTC Customize Public modeDiscuss ChangeIntel on Discord

PowerShell remoting security

This page's changes and edits · All guidance changes

Microsoft's edit ·

Freshness update - part 3 (#12568)

Microsoft's commit message in MicrosoftDocs/PowerShell-Docs · commit a9cf20c · +3 −3 lines · also on GitHub

11 ---
22 description: This document covers security concerns, recommendations, and best practices when using PowerShell Remoting.
3 −ms.date: 03/24/2025
3 +ms.date: 12/09/2025
44 title: Security considerations for PowerShell Remoting using WinRM
55 ---
66
⋯ 106 unchanged lines
113113
114114 - Basic authentication provides no encryption.
115115 - NTLM authentication uses an RC4 cipher with a 128-bit key.
116 −- The `etype` in the TGS ticket determines Kerberos authentication encryption. This is AES-256
117 − on modern systems.
116 +- The `etype` in the TGS ticket determines Kerberos authentication encryption. Modern systems use
117 + the AES-256 algorithm.
118118 - CredSSP encryption uses the TLS cipher suite negotiated in the handshake.
119119
120120 ## Making the second hop
⋯ 28 unchanged lines

Microsoft's Markdown source from MicrosoftDocs/PowerShell-Docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 08:53 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Oct 14:46 UTC · 258 of 260 readable · 256 fully read · documentation 416/439 current