Example of Creating and Using IP Security Policy (IPSec) in Windows

IPSec is an open standard framework that ensures secure and secure communication over IP networks by using cryptographic security services. The IPSec implementation of Windows is based on standards developed by the Internet Engineering Task Force (IETF) IPSec working group.

IPsec establishes trust and security from the source IP address to the destination IP address. Only computers that must understand that communications are secure are the computers that send and receive. Each computer assumes that the medium in which it is communicating is not secure and therefore handles security on its own terminal.

The IPSec policy is used to configure IPSec security services. Supports most communication protocols such as TCP, UDP, ICMP, EGP, etc., providing various levels of protection for communications in existing networks. Policies can be configured based on the security needs of computers, domains, and sites.

IPSec policies consist of regular IPSec policy settings and rules. The following is a straightforward introduction to the creation and use of IPSec policies from a command line perspective.

Copy the code
The code is as follows: REM 1. Create a policy netsh ipsec static add policy name="An IP policy" </p><p>REM 2. Create Filter operation netsh ipsec static add filteraction name="block" action=blockREM netsh ipsec static add filteraction name="allow" action=permit</p><p>REM 3.Create filter list netsh ipsec static add filterlist name= "A filter list" </p><p>REM 4. Create filter netsh ipsec static add filter filterlist="a filter list" srcaddr=any dstaddr=me dstport=8080 description="8080 port access control" protocol =TCP mirrored=yes</p><p>REM 5. Create a policy rule netsh ipsec static add rule name="a filter rule" policy="an IP policy" filterlist="a filter list" filteraction="block" </p><p>REM 6. Activation policy netsh ipsec static set policy name="an IP policy" assign=y

If you want to continue to understand the IPSec settings, you can refer to the Microsoft technical documentation http: //technet.microsoft.com/cc725926