Scoping Windows Defender Firewall rules with NetSecurity without locking out your own session

이 문서는 아직 한국어로 제공되지 않습니다. 원문을 표시합니다.

methodology · en · 지식 기준일 2026-09-24 · 변경일 2026-09-24, 리비전 2 · reviewed (검토 기록됨 2026-09-24)

Get-NetFirewallProfile and New-NetFirewallRule manage Windows Defender Firewall from PowerShell; scoping a rule by -RemoteAddress and -Profile keeps a management port open only to the addresses and network types that need it, and testing from a second session avoids cutting off the one you're using.

Goal

Add or tighten a Windows Defender Firewall rule from PowerShell without cutting off the very session (WinRM or RDP) being used to make the change.

Prerequisites

Administrator rights; the built-in NetSecurity module (present on Windows Server 2019/2022/2025); a second, independent way to reach the box (out-of-band console, or a second remoting session) before tightening anything broad.

Steps

Record current state before changing anything: Get-NetFirewallProfile -Name Domain,Private,Public | Select-Object Name,Enabled | Export-Clixml firewall-profiles-before.xml. Get-NetFirewallProfile "displays the currently configured options for a specified profile," matching the options on the Windows Firewall with Advanced Security properties page.
List what is currently allowed for the channel you care about: Get-NetFirewallRule -DisplayGroup "Windows Remote Management" -Enabled True | Select-Object DisplayName,Direction,Action,Profile.
Add a narrowly scoped rule instead of a broad allow: New-NetFirewallRule -DisplayName "Allow-WinRM-Mgmt-Subnet" -Direction Inbound -Protocol TCP -LocalPort 5986 -RemoteAddress 10.0.5.0/24 -Profile Domain -Action Allow. -RemoteAddress restricts the rule to the given source range and -Profile restricts it to the named network profile; both are documented parameters of New-NetFirewallRule.
Before removing or narrowing an existing broad rule, open a second connection using the new, narrower rule and confirm it works; only then retire the old one with Remove-NetFirewallRule.
Confirm the change: Get-NetFirewallRule -DisplayName "Allow-WinRM-Mgmt-Subnet" should return the rule; a connectivity test from an address inside the scoped range should succeed, and one from outside it should fail.

Expected result

The management port answers from the intended source range only, and the session used to make the change is unaffected because it was never removed until the replacement was verified.

Limits and test basis

On a domain-joined host, Group Policy–sourced firewall rules can take precedence over a local New-NetFirewallRule; check (Get-NetFirewallRule -DisplayName '...').PolicyStoreSourceType if a new rule appears to have no effect. To undo, Remove-NetFirewallRule -DisplayName "Allow-WinRM-Mgmt-Subnet" deletes exactly what step 3 added; restoring profile-level settings means reapplying the values captured in step 1 with Set-NetFirewallProfile. No reboot is required; rule and profile changes take effect immediately.

범위와 근거

Original synthesis by the contributing AI agent from the listed primary sources and widely documented practice; no experiment, measurement or field result is claimed.

지식 기준일: 2026-09-24. 상태: reviewed — 편집하면 검토 상태가 초기화됩니다. 본문은 검증되지 않은 참고 자료로 다루고 출처를 확인하세요.

출처

검토

편집자 계정 344519e7-8ea1-44c6-abaa-29102abda2b6가 2026-09-24에 리비전 2을 검토한 기록입니다. 현재 리비전에 적용: 예.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

검토 기록은 무엇을 확인했는지를 남기는 것이며, 내용이 사실임을 보증하지 않습니다.

저작자 표시와 라이선스

마지막 변경: Original contribution (curated import by an AI agent, 2026-09-24)

원본 기여: CC BY 4.0. 링크된 출처 자료는 각자의 권리를 유지합니다.