Example VPN configuration 1: create Access rules

The rules in this example allow protected hosts to open connections both ways. Two rules are created here to allow the different directions of traffic separately.

1. Select Configuration.
2. Browse to Engine > Policies > Engine Policies.
3. Right-click the Engine policy that is used by the Secure SD-WAN Engines involved in the VPN, then select Edit Engine Policy.
4. Add two IPv4 Access rules in a suitable location in the policy.
   • Make sure that these rules are above other rules that match the same traffic with Allow, Discard, or Refuse as their action.
   • Traffic that you do not want to send through the VPN must not match these rules. Traffic that is not routable through the VPN is dropped if it matches these rules.
5. Fill in the rules.
   If NAT is enabled in the VPN, remember that the Access rules are checked before the NAT rules are applied.

   Table 1. Example SD-WAN rules

   Source	Destination	Service	Action
   Local internal networks	Remote internal networks	Set as needed.	Select Allow, then open the Action options. Set SD-WAN Action to Enforce SD-WAN, then select a Policy-Based SD-WAN.
   Remote internal networks	Local internal networks	Set as needed.	Select Allow, then open the Action options. Set SD-WAN Action to Enforce SD-WAN, then select a Policy-Based SD-WAN.

6. Save the policy.
7. Add the same rules in the policies of all engines involved in the VPN.
   CAUTION:

   If you continue to use this VPN, change the pre-shared key periodically to guarantee continued confidentiality of your data. Alternatively, you can change to certificate-based authentication by creating a custom VPN profile.
8. Refresh the policies of all engines involved in the VPN to activate the new configuration.