Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 16 additions & 9 deletions reference/docs-conceptual/learn/security-features.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: PowerShell has several features designed to improve the security of your scripting environment.
ms.date: 09/23/2021
ms.date: 10/27/2021
title: PowerShell security features
---
# PowerShell security features
Expand Down Expand Up @@ -59,6 +59,10 @@ AppLocker contains new capabilities and extensions that enable you to create rul
apps from running based on unique identities of files and to specify which users or groups can run
those apps.

For more information about AppLocker and Windows Defender Application Control (WDAC), see
[Application Controls for Windows][WDAC] and
[WDAC and AppLocker feature availability][availability].

### Security Servicing Criteria

PowerShell follows the [Microsoft Security Servicing Criteria for Windows][mssec].
Expand All @@ -72,15 +76,18 @@ The table below outlines the features that meet the servicing criteria and those
| Constrained language mode - with AppLocker | Defense in Depth |
| Execution Policy | Defense in Depth |

> [!NOTE]
> There is a corner-case scenario in AppLocker where you only have **Deny** rules and constrained
> language mode is not used to enforce the policy that allows you to bypass the execution policy.
> Beginning in PowerShell 7.2, a change was made to ensure AppLocker rules take precedence
> over a `Set-ExecutionPolicy -ExecutionPolicy Bypass` command.
### Changes in PowerShell 7.2

For more information about AppLocker and Windows Defender Application Control (WDAC), see
[Application Controls for Windows][WDAC] and
[WDAC and AppLocker feature availability][availability].
- There was a corner-case scenario in AppLocker where you only have **Deny** rules and constrained
mode is not used to enforce the policy that allows you to bypass the execution policy. Beginning
in PowerShell 7.2, a change was made to ensure AppLocker rules take precedence over a
`Set-ExecutionPolicy -ExecutionPolicy Bypass` command.

- PowerShell 7.2 now disallows the use of te `Add-Type` cmdlet in a **NoLanguage** mode PowerShell
session on a locked down machine.

- PowerShell 7.2 now disallows scripts from using COM objects in AppLocker system lock down
conditions. Cmdlet that use COM or DCOM internally are not affected.

<!-- link references -->
[applocker]: /windows/security/threat-protection/windows-defender-application-control/applocker/what-is-applocker
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: What's New in PowerShell 7.2
description: New features and changes released in PowerShell 7.2
ms.date: 09/23/2021
ms.date: 10/27/2021
---

# What's New in PowerShell 7.2
Expand Down Expand Up @@ -143,6 +143,8 @@ Install-Module -Name PSDesiredStateConfiguration -Repository PSGallery -MaximumV
- Improve detection of mutable value types (#12495)
- Restrict `New-Object` in **NoLanguage** mode under lock down (#14140)
- Enforce AppLocker Deny configuration before Execution Policy Bypass configuration (#15035)
- Change `FileSystemInfo.Target` from a **CodeProperty** to an **AliasProperty** that points to
`FileSystemInfo.LinkTarget` (#16165)

<!-- reference links -->

Expand Down