Microsoft NetSecurity reference: Gets IPsec rules that match specified criteria. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Find-NetIPsecRule. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / NetSecurity · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-AsJob
Runs the cmdlet as a background job. Use this parameter to run commands that take a long time to complete.
-CimSession
Runs the cmdlet in a remote session or on a remote computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. The default is the current session on the local computer.
-LocalAddress
Specifies the local IP address of a connection. The cmdlet gets the IPSec rules that are matched to the IP address that you specify. This parameter value is the first end point of an IPsec rule and specifies the computers that are subject to the requirements of the rule. The acceptable values for this parameter are: - Single IPv4 Address: 1.2.3.4 - Single IPv6 Address: fe80::1 - IPv4 Subnet (by network bit count): 1.2.3.4/24 - IPv6 Subnet (by network bit count): fe80::1/48 - IPv4 Subnet (by network mask): 1.2.3.4/255.255.255.0 - IPv4 Range: 1.2.3.4 through 1.2.3.7 - IPv6 Range: fe80::1 through fe80::9
-LocalPort
Specifies the local port of the connection. The cmdlet gets the IPSec rules that are matched to the IP port number that you specify. This parameter value is the first end point of an IPsec rule. The acceptable values for this parameter are:a port, range, and keyword. The value depends on the protocol. Protocol is TCP or UDP. The acceptable values for this parameter are: - Port range: 0 through 65535 - Port number: 80 - Keyword: Any Protocol is ICMPv4 or ICMPv6. The acceptable values for this parameter are: - An ICMP type, code pair: 0, 8 - Type and code: 0 through 255 - Keyword: Any No protocol is set. The acceptable values for this parameter are: - Any - RPC - RPC-EPMap - IPHTTPS IPHTTPS is supported only on Windows Server 2012.
-Protocol
Specifies the protocol for an IPSec rule. The cmdlet gets the IPSec rules that use the protocol that you specify for the connection. The acceptable values for this parameter are: - Protocols by number: 0 through 255 - Protocols by name: TCP, UDP, ICMPv4, or ICMPv6. If a port number is identified by using port1 or port2, you must specify TCP or UDP for this parameter. The values ICMPv4 and ICMPv6 create a rule that exempts ICMP network traffic from the IPsec requirements of another rule.
-RemoteAddress (required)
Specifies the remote address of the TCP connection. The cmdlet gets the IPSec rules that are matched the IP address that you specify. This parameter value is the second end point of an IPsec rule and specifies the computer that is subject to the requirements of the rules. The acceptable values for this parameter are:an IPv4 or IPv6 address, host name, subnet, range, or the following keyword: Any. The acceptable formats for this parameter are: - Single IPv4 Address: 1.2.3.4 - Single IPv6 Address: fe80::1 - IPv4 Subnet (by network bit count): 1.2.3.4/24 - IPv6 Subnet (by network bit count): fe80::1/48 - IPv4 Subnet (by network mask): 1.2.3.4/255.255.255.0 - IPv4 Range: 1.2.3.4 through 1.2.3.7 - IPv6 Range: fe80::1 through fe80::9
-RemotePort
Specifies the remote port of the TCP connection. The cmdlet gets the IPSec rules that are matched to the remote port number that you specify. This parameter value is the second end point of an IPsec rule. The acceptable values for this parameter are:a port, range, and keyword. The value depends on the protocol. Protocol is TCP or UDP. The acceptable values for this parameter are: - Port range: 0 through 65535 - Port number: 80 - Keyword: Any Protocol is ICMPv4 or ICMPv6. The acceptable values for this parameter are: - An ICMP type, code pair: 0, 8 - Type and code: 0 through 255 - Keyword: Any. No protocol is set. The acceptable values for this parameter are: - Any - RPC - RPC-EPMap - IPHTTPS. IPHTTPS is supported only on Windows Server 2012.
-ThrottleLimit
Specifies the maximum number of concurrent operations that can be established to run the cmdlet. If this parameter is omitted or a value of 0 is entered, then Windows PowerShell® calculates an optimum throttle limit for the cmdlet based on the number of CIM cmdlets that are running on the computer. The throttle limit applies only to the current cmdlet, not to the session or to the computer.
Prerequisites
Windows with the NetSecurity module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This is a read-oriented cmdlet; protect any sensitive results and check the documented effects of your selected parameters.
This command finds the IPsec rule that the system uses for conventional web traffic to the specified IP address. The command gets the IPSec rule that matches the TCP connection that has the remote address 131.107.33.200 and that uses the remote port 80. The command returns a WMIv2 IPsec rule object. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.