Methods and systems for application and policy based network traffic isolation and data transfer
A method includes allocating an identifier to each of a plurality of policies each comprising a network-isolation identifier associated with a VXWAN directive and transmitting each of the plurality of policies to one or more devices in a network.
1. A centrally controllable multi-tenant controller for controlling a plurality of assets across a plurality of distributed computing environments wherein the controller is configured to:
receive from a first network tenant on a network:
an indication of a partner network tenant with which to establish a IPSEC VPN TUNNEL, and
at least one of:
a site associated with the partner network tenant to which a IPSEC VPN TUNNEL is to be established,
source prefixes or specific IP addresses at a tenant site from to which application traffic is allowed to travel over the IPSEC VPN TUNNEL, or
destination prefixes or specific IP addresses for application traffic that can travel over the IPSEC VPN TUNNEL;
receive an indication from the partner network tenant of agreement to establish the IPSEC VPN TUNNEL;
instruct one or more devices of the first network and the partner network to establish an IPSEC data tunnel between themselves, wherein only traffic between the source and destination prefixes or specific IP addresses that were specified by the first network tenant and the partner network tenant is allowed to pass through the IPSEC VPN TUNNEL, wherein a most restrictive subset of the source and destination prefixes or specific IP addresses are applied for determining the traffic allowed to pass through the IPSEC VPN TUNNEL, and wherein a policy string defines a business policy based on a first virtual extensible wide area network (VXWAN) network-isolation identifier or a second VXWAN network-isolation identifier; and
determine whether to allow the traffic to pass through the IPSEC VPN TUNNEL based on the policy string.
2. The multi-tenant controller of claim 1 , wherein the network comprises connectivity that is at least one of: hybrid, physical, or logical.
3. The multi-tenant controller of claim 1 further configured to:
perform application analysis on the application traffic on a per session basis.
4. The multi-tenant controller of claim 1 , wherein the policy string comprises a policy string format.
5. The multi-tenant controller of claim 4 , wherein the policy string format is standardized.
6. The multi-tenant controller of claim 1 , wherein the application traffic is encrypted.
7. A method for controlling a plurality of assets across a plurality of distributed computing environments, the method comprising:
receiving, from a first network tenant on a network:
an indication of a partner network tenant with which to establish a IPSEC VPN TUNNEL, and
at least one of:
a site associated with the partner network tenant to which a IPSEC VPN TUNNEL is to be established,
source prefixes or specific IP addresses at a tenant site from which application traffic is allowed to travel over the IPSEC VPN TUNNEL, or
destination prefixes or specific IP addresses for application traffic that can travel over the IPSEC VPN TUNNEL;
receive an indication from the partner network tenant of agreement to establish the IPSEC VPN TUNNEL;
instruct one or more devices of the first network and the partner network to establish an IPSEC data tunnel between themselves, wherein only traffic between the source and destination prefixes or specific IP addresses that were specified by the first network tenant and the partner network tenant is allowed to pass through the IPSEC VPN TUNNEL, wherein a most restrictive subset of the source and destination prefixes or specific IP addresses are applied for determining the traffic allowed to pass through the IPSEC VPN TUNNEL, and wherein a policy string defines a business policy based on a first virtual extensible wide area network (VXWAN) network-isolation identifier or a second VXWAN network-isolation identifier; and
determine whether to allow the traffic to pass through the IPSEC VPN TUNNEL based on the policy string.
8. The method of claim 7 , wherein the network comprises connectivity that is at least one of: hybrid, physical, or logical.
9. The method of claim 7 further comprising:
performing application analysis on the application traffic on a per session basis.
10. The method of claim 7 , wherein the policy string comprises a policy string format.
11. The method of claim 10 , wherein the policy string format is standardized.
12. The method of claim 7 , wherein the application traffic is encrypted.
13. A non-transitory computer-readable medium storing instructions that adapt at least one processor to:
receive from a first network tenant on a network:
an indication of a partner network tenant with which to establish a IPSEC VPN TUNNEL, and
at least one of:
a site associated with the partner network tenant to which a IPSEC VPN TUNNEL is to be established,
source prefixes or specific IP addresses at a tenant site from to which application traffic is allowed to travel over the IPSEC VPN TUNNEL, or
destination prefixes or specific IP addresses for application traffic that can travel over the IPSEC VPN TUNNEL;
receive an indication from the partner network tenant of agreement to establish the IPSEC VPN TUNNEL;
instruct one or more devices of the first network and the partner network to establish an IPSEC data tunnel between themselves, wherein only traffic between the source and destination prefixes or specific IP addresses that were specified by the first network tenant and the partner network tenant is allowed to pass through the IPSEC VPN TUNNEL, wherein a most restrictive subset of the source and destination prefixes or specific IP addresses are applied for determining the traffic allowed to pass through the IPSEC VPN TUNNEL, and wherein a policy string defines a business policy based on a first virtual extensible wide area network (VXWAN) network-isolation identifier or a second VXWAN network-isolation identifier; and
determine whether to allow the traffic to pass through the IPSEC VPN TUNNEL based on the policy string.
14. The non-transitory computer-readable medium of claim 13 , wherein the network comprises connectivity that is at least one of: hybrid, physical, or logical.
15. The non-transitory computer-readable medium of claim 13 , wherein the stored instructions further adapt the at least one processor to:
perform application analysis on the application traffic on a per session basis.
16. The non-transitory computer-readable medium of claim 13 , wherein the policy string comprises a policy string format.
17. The non-transitory computer-readable medium of claim 16 , wherein the policy string format is standardized.