Patent Description:
A virtual private network (VPN) may enable devices to communicate securely across a public network, such as the Internet. In this regard, a first device may transmit one or more network packets (e.g., data packets), over the public network, to a second device to establish a VPN connection between the first device and the second device. The one or more network packets may be routed to a network device (e.g., a firewall or other network security device) and the network device may inspect the one or more network packets to determine whether the one or more network packets may be transmitted to the second device to establish the VPN connection.

<CIT> discloses systems and methods for selectively encrypting data flows within a software defined network.

According to some implementations, a method may be performed as defined in the appended claims.

According to some implementations, a device may include one or more memories and one or more processors. The one or more processors may be configured as defined in the appended claims.

According to some implementations, a computer-readable medium may store one or more instructions. The one or more instructions, when executed by one or more processors of a device, may cause the one or more processors to act as defined in the appended claims.

Devices may communicate securely over a public network, such as the Internet, using a virtual private network (VPN) connection between the devices. For example, a client device may seek to communicate securely, via the public network, with a remote device using a tunnel by establishing a VPN tunnel (e.g., an Internet Protocol Security (IPsec) tunnel) to the remote device. The client device may be connected to a local area network (LAN) (e.g., a wireless LAN) associated with an entity and the remote device may be connected to a private network (e.g., a private network of an entity that is different from the entity associated with the LAN). In this regard, in order to establish and/or communicate on the VPN tunnel, the client device may transmit a packet toward the remote device. The packet may be an Internet key exchange (IKE) packet (e.g., a network packet formatted in accordance with an IKE protocol). Alternatively, the packet may be an encapsulating security payload (ESP) packet (e.g., a network packet formatted in accordance with an ESP protocol).

Outbound traffic from the LAN may be regulated by a firewall connected to the LAN. Accordingly, the packet may be routed to the firewall for processing prior to being routed external to the LAN. For example, the firewall may process the packet using one or more firewall policies to determine whether the packet may be transmitted external to the LAN or should be dropped. In some instances, the one or more firewall policies may include a policy that allows transport layer security (TLS) traffic (e.g., packets formatted in accordance with a TLS protocol) and blocks any other network traffic. Accordingly, the firewall may drop the packet from the client device based on the policy that allows TLS traffic and blocks any other network traffic (because the packet is not formatted in accordance with the TLS protocol).

The client device may determine that the packet has been dropped (e.g., by the firewall) if the client device does not receive a response to the packet within a threshold amount of time following transmission of the packet. Accordingly, the client device may attempt to bypass the firewall by encapsulating the packet using a transmission control protocol (TCP) encapsulation technique. For example, the client device may add, to the packet, a TCP header (e.g., including information identifying a TCP port number). The client device may encapsulate the packet using a TLS encapsulation technique to prevent the packet from being dropped, in the event the firewall processes packets using a deep packet inspection (e.g., to identify TLS packets). In this regard, if the packet is an IKE packet, the client device may encrypt the IKE packet using an encryption technique that is based on the IKE protocol and may further encrypt the IKE packet using an encryption technique that is based on the TLS protocol. If the packet is an ESP packet that has been encrypted using an encryption that is based on the ESP protocol, the client device may further encrypt the ESP packet using the encryption technique that is based on the TLS protocol.

Accordingly, the client device may use multiple encryption techniques to prevent the packet from being dropped by the firewall.

Therefore, current techniques encapsulate and encrypt packets using multiple encryption techniques and decapsulate and decrypt the packets using multiple corresponding decryption techniques in order to establish and/or communicate on a VPN connection. Using multiple encryption techniques and multiple corresponding decryption techniques to encrypt and decrypt each packet of a plurality packets in order to establish and/or communicate on a VPN connection consumes computing resources, battery power, and/or the like of the devices on both ends of the VPN connection.

According to some implementations described herein, a device (e.g., a client device) may selectively encrypt a packet transmitted to establish and/or communicate via a VPN. For example, the device may seek to communicate securely, via a public network, with a remote device using a tunnel by establishing a VPN tunnel (e.g., an Internet Protocol Security (IPsec) tunnel) to the remote device. The device may be connected to a LAN (e.g., a wireless LAN) associated with an entity and the remote device may be connected to a private network (e.g., a private network of an entity that is different from the entity associated with the LAN). Outbound traffic from the LAN may be regulated by a security device (e.g., a firewall) connected to the LAN.

In order to establish and/or communicate on the VPN tunnel, the device may transmit a packet (associated with a protocol) toward the remote device. After determining that the packet has been dropped by the security device, the device may selectively encrypt the packet using a null encryption for TLS (e.g., null cipher or no cipher, and therefore no encryption) or a combination of an encryption associated with the protocol and TLS encryption to generate an encrypted packet. The device may transmit the encrypted packet to establish or communicate via the VPN. The security device may treat the encrypted packet as a TLS packet and permit the TLS packet to be transmitted toward the remote device.

Accordingly, the device (e.g., client device) described herein may selectively encrypt a packet (e.g., using a null encryption for TLS or a combination of an encryption associated with the protocol and TLS encryption) to establish and/or communicate via a VPN instead of using multiple encryption techniques to encrypt each packet of a plurality packets to establish and/or communicate via a VPN. By selectively encrypting the packet, the device may conserve computing resources (e.g., processing resources, memory resources, communication resources, and/or the like), battery power, and/or the like of the device and the remote device that would have otherwise been used to encrypt the packet using the multiple encryption techniques and decrypt the packet using multiple decryption techniques.

<FIG> are diagrams of one or more example implementations <NUM> described herein. As shown in <FIG>, example implementation(s) <NUM> may include a client device, a security device, a remote device, and a network. The client device may include a mobile device, a computer, and/or the like. The security device may include a network security device such as, for example, a firewall or another type of network security device. The remote device may include a server device, another client device, and/or the like. The network may include a public network such as, for example, the Internet. The client device may be connected to a LAN associated with an entity and the remote device may be connected to a private network (e.g., a private network of an entity that is different from the entity associated with the LAN). The client device, the security device, the remote device, and the network are further described below in connection with <FIG>, <FIG>, and <FIG>.

As shown in <FIG>, and by reference number <NUM>, the client device may transmit a request to establish a VPN with the remote device. In some implementations, the client device may be executing a VPN application that causes a user interface to be provided to a user of the client device. The user interface may provide information identifying the remote device (e.g., a name, an identifier, a network address, and/or the like) and provide an option to establish the VPN with the remote device. The user may select the option to establish the VPN with the remote device and, based on selection of the option, the VPN application may cause the client device to transmit the request to establish the VPN with the remote device. For example, the client device may transmit a packet for establishing the VPN.

In some implementations, when establishing a VPN, the VPN application of the client device may establish an IPSec tunnel or, in other words, establish network tunnels that implement IPSec Security Association (SA). In this regard, the VPN application may use, for example, an IKE protocol to establish the VPN. Accordingly, when transmitting the packet for establishing the VPN, the client device may transmit an IKE packet as part of an IKE procedure to establish the VPN (e.g., a VPN tunnel) with the remote device.

Outbound traffic of the LAN may be regulated by the security device. Accordingly, the packet (transmitted by the client device) may be routed to the security device. The security device may process the packet (e.g., using one or more security policies) to determine whether the packet is to be transmitted (e.g., external to the LAN) or is to be dropped. When processing the packet, the security device may inspect the packet (e.g., inspect information about the packet such as header(s), source and destination information, format, and/or the like) to determine whether the information about the packet complies with the one or more security policies.

In some instances, the one or more security policies may include a TLS policy. The TLS policy may include a security policy that permits TLS traffic (e.g., packets formatted in accordance with a TLS protocol) to be transmitted external to the LAN and blocks any other traffic (e.g., packets that are not formatted in accordance with a TLS protocol) to be transmitted external to the LAN. In this case, the security device may drop the packet as not being a TLS packet if the security device processes the packet using the TLS policy.

In some implementations, when processing the packet using the TLS policy, the security device may use a deep packet inspection technique to inspect the packet (e.g., to determine whether the packet includes a payload that is consistent with the TLS protocol, and/or the like) to determine whether the packet is a TLS packet. In this regard, by using the deep inspection technique, the security device may drop the packet as not being a TLS packet if the format or payload of the packet does not match the format or payload expected of TLS packets.

In some implementations, based on processing the packet, the security device may provide, to the client device, a notification indicating whether the packet has been transmitted or has been dropped. In this regard, the notification may indicate that the packet has been transmitted when the security device transmits the packet toward the remote device and/or receives, in response to transmitting the packet, VPN setup information (e.g., from the remote device). The notification may include the VPN setup information. The VPN setup information may include information that the client device may use to establish the VPN (e.g., IKE Security Associations (SAs)). In some implementations, the VPN setup information may be a response packet.

Alternatively, the notification may indicate that the packet has been dropped when the security device determines that the packet is to be dropped. In some implementations, the notification may include packet denial information providing a reason for the packet being dropped. For example, the packet denial information may indicate that the packet was dropped because the packet is not a TLS packet (e.g., the packet is not formatted in accordance with the TLS protocol, the packet includes a payload that is not consistent with the TLS protocol, and/or the like).

In this example, the security device may determine that the format of the packet (e.g., the format of the IKE packet) does not match the format of a TLS packet and, accordingly, may drop the packet.

As shown in <FIG>, and by reference number <NUM>, the client device may determine that the packet has been dropped by the security device. For example, the client device (e.g., using the VPN application) may determine that the packet has been dropped if the client device does not receive a response to the packet after a threshold amount of time following transmission of the packet. The threshold amount may be preprogrammed with the client device, may be preprogrammed with the VPN application, may be based on user input, and/or the like. Additionally, or alternatively, the client device may determine that the packet has been dropped if the client device receives the notification including the packet denial information from the security device. For example, the packet denial information may indicate that the packet has been dropped because the packet is not a TLS packet.

As shown in <FIG>, and by reference number <NUM>, the client device may encapsulate the packet with TCP encapsulation to generate a TCP encapsulated packet. For example, based on determining that the packet has been dropped, the client device may encapsulate the packet to emulate a TLS packet, in an attempt to circumvent the security device (e.g., to circumvent the TLS policy). In this regard, in an attempt to circumvent the security device, the client device may encapsulate the packet with TCP encapsulation (e.g., with a TCP encapsulation technique) to generate a TCP encapsulated packet. For example, the client device may encapsulate the packet by adding a TCP header to the packet and include, in the TCP header, information identifying a particular destination port (to direct the packet to the particular destination port in an attempt to circumvent the security device). For example, the information identifying the particular destination port may identify port <NUM> (e.g., TCP destination port <NUM>).

As shown in <FIG>, and by reference number <NUM>, the client device may transmit the TCP encapsulated packet. The client device may transmit the TCP encapsulated packet directed to the particular destination port in an attempt to circumvent the security device. The TCP encapsulated packet may be routed to the security device and the security device may inspect and drop the TCP encapsulated packet, in a manner similar to the manner described above. For example, the security device may inspect the TCP encapsulated packet (e.g., using the deep packet inspection technique) to determine that the TCP encapsulated packet is an IKE packet encapsulated as a TLS packet (e.g., the format of the TCP encapsulated packet does not match the format of a TLS packet).

For instance, the security device, using the deep packet inspection, may determine that the packet includes a payload that is not consistent with the TLS protocol. Accordingly, the security device may determine that the TCP encapsulated packet is not a TLS packet and drop the TCP encapsulated packet. In some implementations, in addition to dropping the TCP encapsulated packet, the security device may send the notification.

As shown in <FIG>, and by reference number <NUM>, the client device may determine that the TCP encapsulated packet has been dropped by the security device. The client device (e.g., using the VPN application) may determine that the TCP encapsulated packet has been dropped, in a manner similar to the manner described above.

Based on determining that the TCP encapsulated packet has been dropped, the client device may determine whether a version of the TLS protocol to be used by the client device supports null encryption. In some implementations, the client device may consider information from the client device (e.g., information from the VPN application) when determining which version of the TLS protocol to be used. Alternatively, or additionally, the client device may consider information from the security device and a server (e.g., associated with the remote device) when determining which version of the TLS protocol to be used.

If the client device determines that the version of TLS does not support the null encryption for TLS, the client device may determine to encrypt the packet using a combination of an encryption technique of the IKE protocol and a TLS encryption (e.g., an encryption technique of the TLS protocol) (as discussed below in connection with <FIG> and <FIG>). Alternatively, if the client device determines that the version of TLS supports null encryption for TLS, the client device may determine to encrypt the packet using null encryption for TLS (as discussed below in connection with <FIG>).

As shown in <FIG>, and by reference number <NUM>, the client device may determine that the version of TLS does not support the null encryption for TLS. For example, the client device (e.g., using the VPN application) may determine that the version of TLS, to be used by the client device (e.g., used by the VPN application), is TLS protocol version <NUM>, which does not support null encryption for TLS. Based on determining that the version of TLS does not support the null encryption for TLS, the client device (e.g., using the VPN application) may determine to encrypt the packet using a combination of the encryption technique of the IKE protocol (e.g., an encryption algorithm of IKE) and TLS encryption (as discussed below in connection with <FIG>). In some implementations, when the security device detects null encryption of the packet (e.g., a hello packet that is attempting to negotiate null encryption with the remote device), the security device may block a TLS connection negotiation associated with the packet encrypted using null encryption.

As shown in <FIG>, and by reference number <NUM>, the client device may encrypt the packet using null encryption of TLS to generate a null encrypted packet. For example, the client device may determine that the version of TLS, to be used by the client device (e.g., used by the VPN application), is TLS protocol version <NUM> or version <NUM>, which supports null encryption for TLS. Based on determining that the version of TLS supports null encryption for TLS, the client device (e.g., using the VPN application) may encrypt the packet using null encryption for TLS to generate the null encrypted packet. In some implementations, the packet may be encrypted using the encryption technique of the IKE protocol prior to being encrypted using null encryption for TLS. In some implementations, the client device may encapsulate the null encrypted packet in accordance with the TLS protocol to emulate the format of a TLS packet.

In some implementations, the null encrypted packet may be authenticated using an authentication algorithm of TLS and using an authentication algorithm associated with the IKE protocol (e.g., an authentication algorithm of IKE). In other words, in some implementations, the null encrypted packet may be subject to hashing of a hash algorithm associated the IKE protocol (e.g., a hash algorithm of IKE) in this situation.

As shown in <FIG>, and by reference number <NUM>, the client device may transmit the null encrypted packet. For example, the client device may transmit the null encrypted packet to the remote device and the null encrypted packet may be routed to the security device, in a manner similar to the manner described above in connection with <FIG> (reference number <NUM>). The client device may determine whether the null encrypted packet has been dropped by the security device.

If the security device determines that null encryption for TLS is supported (e.g., TLS protocol version <NUM> or version <NUM> is supported), the security device may transmit the null encrypted packet toward the remote device. In some implementations, the security device may receive the response packet from the remote device based on transmitting the null encrypted packet and may provide, to the client device, the response packet. The client device may receive the response packet transmitted by the remote device and determine that the null encrypted packet has not been dropped by the security device. The client device may establish the VPN based on receiving the response packet, as described in more detail below in connection with <FIG> (reference number <NUM>).

The VPN may be established during a first phase (Phase <NUM>) and a second phase (Phase <NUM>) of the IKE protocol, as explained in more detail below in connection with <FIG>. After establishing the VPN, the client device may transmit packets, on the VPN, to communicate securely with the remote device. In some implementations, during Phase <NUM> of the IKE protocol discussed above, the client device and the remote device may select to communicate securely, on the VPN, using the ESP protocol and ESP packets.

Additionally, with respect to communicating securely using the ESP protocol, the client device and the remote device may negotiate encryption of the ESP packets, authentication of the ESP packets, and/or the like. With respect to encryption of the ESP packets, the client device and the remote device may negotiate to use null encryption of TLS. In some implementations, the ESP packets (e.g., a payload) may be encrypted using ESP encryption prior to being encrypted using null encryption of TLS.

With respect to authentication of the ESP packets, the client device and the remote device may negotiate to authenticate the ESP packets using an authentication algorithm of TLS without authenticating (e.g., hashing) the ESP packets using an authentication algorithm of ESP. The client device and the remote device may negotiate an authentication algorithm of TLS that is as strong as an authentication algorithm of ESP (e.g., associated with the client device and/or the remote device). In other words, in some implementations, the ESP packets may not be subject to hashing of a hash algorithm of IPSec (e.g., hash algorithm of ESP).

With respect to encryption algorithms for ESP, the client device and the remote device may negotiate to determine whether to use Data Encryption Standard (DES), Triple DES (3DES), Advanced Encryption Standard (AES), and/or the like. With respect to authentication algorithms for TLS, the client device and the remote device may negotiate to determine whether to use authenticated encryption with associated data (AEAD), hash-based message authentication code (HMAC), message digest <NUM> (MD5), secure hash algorithm (SHA), and/or the like. The above encryption and authentication algorithms are provided merely as examples of encryption and authentication algorithms that may be used. In practice, these and/or other encryption and authentication algorithms may be used.

As shown in <FIG>, and by reference number <NUM>, the client device may determine that the null encrypted packet has been dropped by the security device. In this example, assume that the security device inspects and drops the null encrypted packet, in a manner similar to the manner described above in connection with <FIG> (reference number <NUM>). In this instance, for example, the security device may determine that the null encrypted packet has been encrypted using null encryption for TLS and determine, by performing deep packet inspection, that the null encrypted packet includes a payload that is not consistent with the TLS protocol. Accordingly, the security device may determine that the null encrypted packet is not a TLS packet and drop the null encrypted packet. In some implementations, if the security device allows transmission of the null encrypted packet (e.g., to negotiate and establish a TLS connection with null encryption with the remote device), the security device may block subsequent data packets (transmitted by the client device toward the remote device) that are encrypted using null encryption of TLS.

Alternatively, the security device may determine that that the version of TLS is TLS protocol version <NUM>, which does not support null encryption for TLS. Accordingly, the security device may determine that the null encrypted packet is not supported and drop the null encrypted packet. The client device may determine that the null encrypted packet has been dropped, in a manner similar to the manner described above in connection with <FIG> (reference number <NUM>).

As shown in <FIG>, and by reference number <NUM>, the client device may encrypt the packet using an encryption of IKE and encrypt the IKE encrypted packet with TLS encryption to generate an encrypted packet. Based on determining that the null encrypted packet has been dropped, the client device (e.g., using the VPN application) may encrypt the packet using an encryption technique of the IKE protocol (e.g., an encryption algorithm of IKE) and a TLS encryption (e.g., an encryption technique of the TLS protocol), in an attempt to ensure compliance with the TLS policy and, thereby, to ensure transmission of the packet toward the remote device. For example, the client device (e.g., using the VPN application) may encrypt the packet using the encryption technique of the IKE protocol to form an IKE encrypted packet.

The client device may further encrypt the IKE encrypted packet using the TLS encryption to generate a TLS encrypted packet. In this regard, encrypting the packet may prevent the security device from inspecting the packet using the deep packet inspection technique to determine that the packet includes a payload that is inconsistent with the TLS protocol. The TLS encryption (e.g., the encryption algorithm for the TLS) may be an encryption that is at least as strong as an encryption algorithm of IKE and/or ESP. In some implementations, the client device may encapsulate the TLS encrypted packet in accordance with the TLS protocol to emulate the format of a TLS packet.

As shown in <FIG>, and by reference number <NUM>, the client device may transmit the TLS encrypted packet. The client device may transmit the TLS encrypted packet toward the remote device. The TLS encrypted packet may be routed to the security device and the security device may inspect and forward the TLS encrypted packet, in a manner similar to the manner described above.

As shown in <FIG>, and by reference number <NUM>, the security device may transmit the encrypted packet. In this instance, the security device may determine that the format of the TLS encrypted packet matches the format of a TLS packet (e.g., based on the IKE encrypted packet being encrypted using the TLS encryption and being encapsulated in accordance with the TLS protocol). Additionally, or alternatively, encrypting the packet may prevent the security device from determining, using the deep packet inspection technique, that the packet is not a TLS packet, as explained above. Accordingly, the security device may transmit the TLS encrypted packet toward the remote device. In some implementations, the security device may receive the response packet from the remote device and may provide, to the client device, the response packet.

As shown in <FIG>, and by reference number <NUM>, the client device may set up the VPN. For example, the client device may receive the response packet transmitted by the remote device and may establish the VPN based on receiving the response packet. For instance, the client device (e.g., using the VPN application) may establish the VPN (that uses IPsec SA, as explained above) based on, for example, the VPN setup information. As an example, the IKE protocol may be used to establish an encrypted communication session between the client device and the remote device. The IKE protocol may include two phases. In a first phase (Phase <NUM>), the client device and the remote device may negotiate an SA (e.g., associated with an IKE tunnel) for the encrypted communication session. The SA negotiated from Phase <NUM> enables the client device and/or the other device to communicate securely in a second phase (Phase <NUM>). During Phase <NUM> of the IKE protocol, the client device and the remote device may establish SAs for other applications, such as IPsec.

The IKE protocol may establish an IPsec SA by establishing a shared state between the client device and the remote device. The shared state defines specific services provided to network traffic, which cryptographic models will be utilized to provide the specific services, keys utilized as input to the cryptographic models, parameters for communication of the network traffic, and/or the like. The IKE protocol may perform a mutual authentication between the client device and the remote device, and may establish an IPsec SA that includes shared secret information that can be used to efficiently establish SAs for the ESP protocol or an authentication header (AH) protocol and a set of cryptographic models to be used by the SAs to protect network traffic carried by the IPsec SA.

After establishing the VPN, the client device may transmit the packet, on the VPN, to communicate securely with the remote device. In some implementations, during Phase <NUM> of the IKE protocol discussed above, the client device and the remote device may select to communicate securely, on the VPN, using the ESP protocol and ESP packets.

Additionally, with respect to communicating securely using the ESP protocol, the client device and the remote device may negotiate encryption of ESP packets, authentication of ESP packets, and/or the like. With respect to encryption of the ESP packets, the client device and the remote may negotiate to encrypt the ESP packets using null encryption for ESP and encrypt the null encrypted ESP packets with TLS encryption. With respect to authentication of the ESP packets, the client device and the remote device may negotiate to authenticate the ESP packets using an authentication algorithm of ESP and using an authentication algorithm of TLS. TLS uses encryption algorithm which is as strong as or stronger than the encryption algorithm that would have been used by ESP if the security device were to not block the IKE/ESP traffic (e.g., IKE and ESP packets).

With respect to authentication algorithms for ESP, the client device and the remote device may negotiate to determine whether to use message digest <NUM> (MD5), secure hash algorithm (SHA), and/or the like. With respect to encryption algorithms for TLS, the client device and the remote device may negotiate to determine whether to use AES, Galois/Counter Mode (GCM), cipher block chaining (CBC), and/or the like. With respect to authentication algorithms for TLS, the client device and the remote device may negotiate to determine whether to use authenticated encryption with associated data (AEAD), hash-based message authentication code (HMAC), MD5, SHA, and/or the like. The above encryption and authentication algorithms are provided merely as examples of encryption and authentication algorithms that may be used. In practice, these and/or other encryption and authentication algorithms may be used.

In some implementations, the client device may configured (e.g., using the VPN application) to determine an order in which techniques used by the client device to transmit a packet (e.g., an IKE packet) will be attempted (e.g., IKE packet, TCP encapsulated IKE packet, null encrypted IKE packet, TLS encrypted IKE packet, and/or the like). If a first technique fails (e.g., the IKE packet is dropped by the security device), then the client device may attempt a second technique; if the second technique fails (e.g., the TCP encapsulated IKE packet is dropped by the security device), then the client device may attempt a third technique; and so on. In some implementations, the client device (e.g., using the VPN application) may be configured to encrypt the packet using TLS encryption if the IKE packet, the TCP encapsulated IKE packet, and the null encrypted IKE packet are dropped by the security device.

In the description above, it has been assumed that the security device drops the packet (<FIG>), the TCP encapsulated packet (<FIG>), and the null encrypted packet (<FIG>). In some implementations, the security device may permit the packet (from <FIG>), the TCP encapsulated packet (from <FIG>), or the null encrypted packet (from <FIG>) to be transmitted toward the remote device. In the case of the packet (from <FIG>), the remote device may process the packet and respond if necessary. In the case of the TCP encapsulated packet (from <FIG>), the remote device may remove the TCP encapsulation, process the packet, and respond if necessary. In the case of the null encrypted packet (from <FIG>), the remote device may decrypt the encrypted packet, process the packet, and respond if necessary.

As indicated above, <FIG> are provided merely as one or more examples. The number and arrangement of devices and/or networks shown in <FIG> are provided as one or more examples. Additionally, or alternatively, a set of devices (e.g., one or more devices) of <FIG> may perform one or more functions described as being performed by another set of devices of <FIG>.

<FIG> is a diagram of an example environment <NUM> in which systems and/or methods described herein may be implemented. As shown in <FIG>, environment <NUM> may include a client device <NUM>, a security device <NUM>, a remote device <NUM>, and a network <NUM>. Devices of environment <NUM> may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

Client device <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information, such as information described herein. For example, client device <NUM> may include a mobile phone (e.g., a smart phone, a radiotelephone, and/or the like), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart watch, a pair of smart glasses, a heart rate monitor, a fitness tracker, smart clothing, smart jewelry, a head mounted display, and/or the like), a network device, or a similar type of device. In some implementations, client device <NUM> may receive network traffic from and/or may provide network traffic to remote device <NUM> via network <NUM> (e.g., by routing packets using security device <NUM> as an intermediary).

Security device <NUM> includes one or more devices capable of receiving, processing, storing, routing, and/or providing traffic (e.g., a packet, other information or metadata, and/or the like) in a manner described herein. For example, security device <NUM> may include a firewall or another type of device that includes security-related functionality, such as a router (e.g., a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router, a provider core router, and/or the like), a virtual router, and/or the like), a gateway, a switch, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, a data center server, and/or the like), a load balancer, and/or a similar device. In some implementations, security device <NUM> may be a physical device implemented within a housing, such as a chassis. In some implementations, security device <NUM> may be a virtual device implemented by one or more computer devices of a cloud computing environment or a data center.

Remote device <NUM> includes one or more devices capable of receiving, generating, storing, processing, and/or providing information, such as information described herein. For example, remote device <NUM> may include a mobile phone (e.g., a smart phone, a radiotelephone, and/or the like), a laptop computer, a tablet computer, a desktop computer, a handheld computer, a gaming device, a wearable communication device (e.g., a smart watch, a pair of smart glasses, a heart rate monitor, a fitness tracker, smart clothing, smart jewelry, a head mounted display, and/or the like), a server device, a network device, or a similar type of device. In some implementations, remote device <NUM> may receive network traffic from and/or may provide network traffic to client device <NUM> via network <NUM> (e.g., by routing packets via security device <NUM> as an intermediary).

Network <NUM> includes one or more wired and/or wireless networks. For example, network <NUM> may include a packet switched network, a cellular network (e.g., a fifth generation (<NUM>) network, a fourth generation (<NUM>) network, such as a long-term evolution (LTE) network, a third generation (<NUM>) network, a code division multiple access (CDMA) network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, or the like, and/or a combination of these or other types of networks.

<FIG> is a diagram of example components of a device <NUM> of <FIG>. Device <NUM> may correspond to client device <NUM>, security device <NUM>, and/or remote device <NUM>. In some implementations, client device <NUM>, security device <NUM>, and/or remote device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include one or more input components <NUM>-<NUM> through <NUM>-A (A ≥ <NUM>) (hereinafter referred to collectively as input components <NUM>, and individually as input component <NUM>), a switching component <NUM>, one or more output components <NUM>-<NUM> through <NUM>-B (B ≥ <NUM>) (hereinafter referred to collectively as output components <NUM>, and individually as output component <NUM>), and a controller <NUM>.

Controller <NUM> includes a processor in the form of, for example, a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and/or another type of processor.

In some implementations, controller <NUM> may include a random access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, an optical memory, etc.) that stores information and/or instructions for use by controller <NUM>.

Controller <NUM> may perform one or more processes described herein. Controller <NUM> may perform these processes in response to executing software instructions stored by, or carried on, a computer-readable medium. A computer-readable medium may be a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices. Alternatively, a computer-readable medium may be a transitory medium such as a carrier wave or transmission medium.

<FIG> is a diagram of example components of one or more devices <NUM> of <FIG>. Device <NUM> may correspond to client device <NUM>, security device <NUM>, and/or remote device <NUM>. In some implementations, client device <NUM>, security device <NUM>, and/or remote device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, a storage component <NUM>, an input component <NUM>, an output component <NUM>, and a communication interface <NUM>.

Bus <NUM> includes a component that permits communication among the components of device <NUM>. Processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. Processor <NUM> is a CPU, a GPU, an APU, a microprocessor, a microcontroller, a DSP, an FPGA, an ASIC, or another type of processing component. In some implementations, processor <NUM> includes one or more processors capable of being programmed to perform a function. Memory <NUM> includes a RAM, a ROM, and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by processor <NUM>.

Output component <NUM> includes a component that provides output information from device <NUM> (e.g., a display, a speaker, and/or one or more LEDs).

Communication interface <NUM> includes a transceiver-like component (e.g., a transceiver and/or a separate receiver and transmitter) that enables device <NUM> to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communication interface <NUM> may permit device <NUM> to receive information from another device and/or provide information to another device. For example, communication interface <NUM> may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, an RF interface, a universal serial bus (USB) interface, a wireless local area interface, a cellular network interface, and/or the like.

Device <NUM> may perform one or more processes described herein. Device <NUM> may perform these processes based on processor <NUM> executing software instructions stored by, or carried on, a computer-readable medium, such as memory <NUM> and/or storage component <NUM>. A computer-readable medium may be a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices. Alternatively, a computer-readable medium may be a transitory medium such as a carrier signal or transmission medium.

<FIG> is a flow chart of an example process <NUM> associated with selective transport layer security encryption. In some implementations, one or more process blocks of <FIG> may be performed by a device (e.g., client device <NUM>). In some implementations, one or more process blocks of <FIG> may be performed by another device or a group of devices separate from or including the device, such as a security device (e.g., security device <NUM>), a remote device (e.g., remote device <NUM>), and/or the like. Additionally, or alternatively, one or more process blocks of <FIG> may be performed by one or more components of a device <NUM>, such as input components <NUM>, switching component <NUM>, output components <NUM>, one or more components of a device <NUM>, such as processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, communication interface <NUM>, and/or the like.

As shown in <FIG>, process <NUM> may include transmitting a packet for establishing or communicating on a virtual private network (VPN) (block <NUM>). For example, the device may transmit a packet for establishing or communicating on a virtual private network (VPN), as described above.

As further shown in <FIG>, process <NUM> may include determining that the packet has been dropped by a security device (block <NUM>). For example, the device may determine that the packet has been dropped by a security device, as described above.

As further shown in <FIG>, process <NUM> may include encapsulating, when the packet has been dropped, the packet with transmission control protocol (TCP) encapsulation to generate a TCP encapsulated packet (block <NUM>). For example, the device may encapsulate, when the packet has been dropped, the packet with transmission control protocol (TCP) encapsulation to generate a TCP encapsulated packet, as described above.

As further shown in <FIG>, process <NUM> may include transmitting the TCP encapsulated packet for establishing or communicating on the VPN (block <NUM>). For example, the device may transmit the TCP encapsulated packet for establishing or communicating on the VPN, as described above.

As further shown in <FIG>, process <NUM> may include determining that the TCP encapsulated packet has been dropped by the security device (block <NUM>). For example, the device may determine that the TCP encapsulated packet has been dropped by the security device, as described above.

As further shown in <FIG>, process <NUM> may include selectively encrypting, when the TCP encapsulated packet has been dropped, the packet using a combination of encryption associated with the protocol and null encryption for transport layer security (TLS) or a combination of encryption associated with the protocol and TLS encryption to generate an encrypted packet (block <NUM>). For example, the device may selectively encrypt, by the device and when the TCP encapsulated packet has been dropped, the packet using a combination of encryption associated with the protocol and null encryption for transport layer security (TLS) or a combination of encryption associated with the protocol and TLS encryption to generate an encrypted packet, as described above.

As further shown in <FIG>, process <NUM> may include transmitting the encrypted packet on the VPN for establishing or communicating on the VPN (block <NUM>). For example, the device may transmit the encrypted packet on the VPN for establishing or communicating on the VPN, as described above.

In a first implementation, at least one of the packet, the TCP encapsulated packet, or the encrypted packet is directed to destination port <NUM>. In a second implementation, alone or in combination with the first implementation, selectively encrypting the packet using the null encryption for TLS or the combination of encryption associated with the protocol and TLS encryption includes: encrypting the packet using the null encryption for TLS based on determining that the version of TLS to be used supports null encryption to generate the encrypted packet. In a third implementation, alone or in combination with one or more of the first and second implementations, selectively encrypting the packet using the null encryption for TLS or the combination of encryption associated with the protocol and TLS encryption includes: encrypting the packet using the combination of encryption associated with the protocol and TLS encryption based on determining that the version of TLS to be used does not support null encryption to generate the encrypted packet.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, selectively encrypting the packet using the null encryption for TLS or the combination of encryption associated with the protocol and TLS encryption includes encrypting the packet using the null encryption for TLS to form a first encrypted packet, and the method further comprises: transmitting the first encrypted packet; determining that the first encrypted packet has been dropped by the security device, and encrypting, when the first encrypted packet has been dropped, the packet using the combination of encryption associated with the protocol and TLS encryption to generate a second encrypted packet, the second encrypted packet is the encrypted packet.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, selectively encrypting the packet using the null encryption for TLS or the combination of encryption associated with the protocol and TLS encryption includes encrypting the packet using the null encryption for TLS, and the method further comprises: subjecting the packet to hashing of a hash algorithm of TLS and subjecting the packet to hashing of a hash algorithm associated with the protocol.

In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, selectively encrypting the packet using the null encryption for TLS or the combination of encryption associated with the protocol and TLS encryption includes encrypting the packet using the combination of encryption associated with the protocol and TLS encryption, and the method further comprises: subjecting the packet to hashing of a hash algorithm of TLS and subjecting the packet to hashing of a hash algorithm associated with the protocol.

As shown in <FIG>, process <NUM> may include transmitting a packet for communicating with a remote device (block <NUM>). For example, the device may transmit a packet for communicating with a remote device, as described above.

As further shown in <FIG>, process <NUM> may include encrypt, after determining that the packet has been dropped, the packet using a combination of encryption associated with the protocol and null encryption for transport layer security (TLS) to generate a first encrypted packet (block <NUM>). For example, the device may encrypt, after determining that the packet has been dropped, the packet using a combination of encryption associated with the protocol and null encryption for transport layer security (TLS) to generate a first encrypted packet, as described above.

As further shown in <FIG>, process <NUM> may include transmitting the first encrypted packet for communicating with the remote device (block <NUM>). For example, the device may transmit the first encrypted packet for communicating with the remote device, as described above.

As further shown in <FIG>, process <NUM> may include determining that the first encrypted packet has been dropped by the security device (block <NUM>). For example, the device may determine that the first encrypted packet has been dropped by the security device, as described above.

As further shown in <FIG>, process <NUM> may include encrypt, after determining that the first encrypted packet has been dropped, the packet using a combination of encryption associated with the protocol and TLS encryption to generate a second encrypted packet (block <NUM>). For example, the device may encrypt, after determining that the first encrypted packet has been dropped, the packet using a combination of encryption associated with the protocol and TLS encryption to generate a second encrypted packet, as described above.

As further shown in <FIG>, process <NUM> may include transmitting the second encrypted packet for communicating with the remote device (block <NUM>). For example, the device may transmit the second encrypted packet for communicating with the remote device, as described above.

In a first implementation, process <NUM> includes selecting an encryption algorithm for the TLS encryption that is at least as strong as an encryption algorithm associated with the protocol; and encrypt the packet is using the combination of encryption associated with the protocol and the encryption algorithm for the TLS encryption. In a second implementation, alone or in combination with the first implementation, process <NUM> includes transmitting an Internet key exchange (IKE) packet as part of an IKE procedure to establish a virtual private network (VPN) tunnel with the remote device; determining that the IKE packet has been dropped by the security device; encapsulating, when the IKE packet has been dropped, the packet with TCP encapsulation to generate a TCP encapsulated IKE packet; and transmitting the TCP encapsulated IKE packet for establishing the VPN tunnel.

In a third implementation, alone or in combination with one or more of the first and second implementations, the TCP encapsulated IKE packet is directed to destination port <NUM>. In a fourth implementation, alone or in combination with one or more of the first through third implementations, process <NUM> includes determining that the TCP encapsulated IKE packet has been dropped by the security device; encrypt, when the TCP is encapsulating IKE packet has been dropped, the IKE packet using a combination of IKE encryption and transport layer security (TLS) encryption to generate an encrypted IKE packet; and transmitting the encrypted IKE packet for establishing the VPN tunnel.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, process <NUM> includes determining that the packet has been dropped by the security device based on receiving no reply to the packet from the security device for a threshold amount of time, or determining that the packet has been dropped by the security device based on receiving a notification from the security device indicating that the packet has been dropped. In a sixth implementation, alone or in combination with one or more of the first through fifth implementations, process <NUM> includes encapsulating, based on determining that the packet has been dropped, the packet with transmission control protocol (TCP) encapsulation to generate a TCP encapsulated packet; and transmitting the TCP encapsulated packet for communicating with the remote device.

As shown in <FIG>, process <NUM> may include transmitting a packet for communicating via a tunnel (block <NUM>). For example, the device may transmit a packet for communicating via a tunnel, as described above.

As further shown in <FIG>, process <NUM> may include selectively encrypt, after determining that the packet has been dropped, the packet using a combination of encryption associated with the protocol and null encryption for transport layer security (TLS) or a combination of encryption associated with the protocol and TLS encryption to generate an encrypted packet (block <NUM>). For example, the device may selectively encrypt, after determining that the packet has been dropped, the packet using a combination of encryption associated with the protocol and null encryption for transport layer security (TLS) or a combination of encryption associated with the protocol and TLS encryption to generate an encrypted packet, as described above.

As further shown in <FIG>, process <NUM> may include transmitting the encrypted packet for communicating via the tunnel (block <NUM>). For example, the device may transmit the encrypted packet for communicating via the tunnel, as described above.

In a first implementation, the one or more instructions, when executed by the one or more processors, further cause the one or more processors to determine that a version of TLS to be used supports null encryption, and encrypt the packet using the null encryption for TLS based on determining that the version of TLS to be used supports null encryption to generate the encrypted packet.

In a second implementation, alone or in combination with the first implementation, the one or more instructions, when executed by the one or more processors, further cause the one or more processors to determine that a version of TLS to be used does not support null encryption, and encrypt the packet using the combination of encryption associated with the protocol and TLS encryption based on determining that the version of TLS to be used does not support null encryption to generate the encrypted packet.

In a third implementation, alone or in combination with one or more of the first and second implementations, the one or more instructions, that cause the one or more processors to selectively encrypt the packet using the null encryption for TLS or the combination of encryption associated with the protocol and TLS encryption, cause the one or more processors to encrypt the packet using the null encryption for TLS to form a first encrypted packet, and transmit the first encrypted packet; determine that the first encrypted packet has been dropped by the security device, and encrypt, when the first encrypted packet has been dropped, the packet using the combination of encryption associated with the protocol and TLS encryption to generate a second encrypted packet, the second encrypted packet is the encrypted packet.

In a fourth implementation, alone or in combination with one or more of the first through third implementations, the packet is transmitted for communicating with a remote device via the tunnel, and encapsulate, based on determining that the packet has been dropped, the packet with transmission control protocol (TCP) encapsulation to generate a TCP encapsulated packet, and transmit the TCP encapsulated packet for communicating with the remote device.

In a fifth implementation, alone or in combination with one or more of the first through fourth implementations, process <NUM> includes transmitting an Internet key exchange (IKE) packet as part of an IKE procedure for establishing the tunnel; determining that the IKE packet has been dropped by the security device; encrypt, after is determining that the IKE packet has been dropped, the IKE packet using a combination of IKE encryption and transport layer security (TLS) encryption to generate an encrypted IKE packet; and transmitting the encrypted IKE packet for establishing the tunnel.

As used herein, traffic or content may include a set of packets. A packet may refer to a communication structure for communicating information, such as a protocol data unit (PDU), a service data unit (SDU), a network packet, a datagram, a segment, a message, a block, a frame (e.g., an Ethernet frame), a portion of any of the above, and/or another type of formatted or unformatted unit of data capable of being transmitted via a network.

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more. " Further, as used herein, the article "the" is intended to include one or more items referenced in connection with the article "the" and may be used interchangeably with "the one or more. " Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.), and may be used interchangeably with "one or more. " Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "has," "have," "having," or the like are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and/or," unless explicitly stated otherwise (e.g., if used in combination with "either" or "only one of').

Claim 1:
A method, comprising:
transmitting (<NUM>), by a device, a packet for establishing or communicating on a virtual private network, VPN,
the packet being associated with a protocol;
determining (<NUM>), by the device, that the packet has been dropped by a security device;
encapsulating (<NUM>), by the device and when the packet has been dropped, the packet with transmission control protocol, TCP, encapsulation to generate a TCP encapsulated packet;
transmitting (<NUM>), by the device, the TCP encapsulated packet for establishing or communicating on the VPN;
determining (<NUM>), by the device, that the TCP encapsulated packet has been dropped by the security device;
selectively encrypting (<NUM>), by the device and when the TCP encapsulated packet has been dropped, the packet using a null encryption for transport layer security, TLS, or a combination of encryption associated with the protocol and TLS encryption to generate an encrypted packet; and
transmitting (<NUM>), by the device, the encrypted packet on the VPN for establishing or communicating on the VPN.