Extending the Enterprise Trust Policy Framework to Cloud Native Applications

By coordinating policy conversion and data plane label injection between enterprise network and service mesh, cross-domain trust problem of policy extension in cloud-native applications is solved, and unified policy implementation and secure communication between enterprise network and service mesh is realized. .

CN113647056BActive Publication Date: 2024-11-12CISCO TECHNOLOGY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080024924.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-04-03
Filing Date
2020-04-03
Publication Date
2024-11-12
Estimated Expiration
2040-04-03

AI Technical Summary

Technical Problem

The existing technology is difficult to extend the trusted policy framework of an enterprise to cloud-native applications, especially in service mesh environments, resulting in cross-domain trust issues and challenges in policy implementation.

Method used

By coordinating traffic segmentation policies between the enterprise network controller and the service mesh coordinator, use the policy conversion service to convert enterprise policies into a comprehensible form of the service mesh, and inject corresponding tags into the traffic through the data plane conversion service , such as X-SGT and X-VNI, ensure end-to-end implementation of policies throughout the enterprise and service mesh.

Benefits of technology

It realizes the unified policy implementation of cross-domain trust, ensures secure communication between enterprise networks and service mesh, solves the problems of policy separation and trust boundaries, and enhances the credibility of cloud-native applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113647056B_ABST
    Figure CN113647056B_ABST
Patent Text Reader

Abstract

The present technology relates to systems and methods for extending a trusted policy framework of an enterprise network to cloud native applications. The present technology includes sending a first communication by an enterprise network controller to a service mesh coordinator of a service mesh, wherein the first communication notifies the service mesh coordinator of a traffic segmentation policy to be applied to traffic originating from the enterprise network and a layer 7 extension header corresponding to the enterprise network traffic segmentation policy.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. non-provisional patent application No. 16 / 839,485, filed on April 3, 2020, entitled “EXTENDING ENTERPRISE TRUSTED POLICY FRAMEWORK TO CLOUD NATIVE APPLICATIONS,” which application claims priority to U.S. provisional patent application No. 62 / 829,016, filed on April 3, 2019, entitled “EXTENDING ENTERPRISE TRUSTED POLICY FRAMEWORK TO CLOUD NATIVE APPLICATIONS,” the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present technology relates to extending an enterprise's trusted policy framework to cloud-native applications, and more specifically, to extending enterprise traffic segmentation rules to a service mesh. Background Art

[0004] Enterprises often use applications that extend into the cloud. In some cases, these applications consist of a set of microservices that are tied together in a mesh sometimes called a service mesh. The concept of a service mesh is to provide networking and monitoring for highly decomposed and distributed applications by offloading common functions (such as load balancing, circuit breaking, encryption, etc.) from the application to a shared framework. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In order to describe the manner in which the above and other advantages and features of the present disclosure can be obtained, a more particular description of the principles briefly described above will be given by reference to specific embodiments shown in the accompanying drawings. Understanding that these drawings depict only exemplary embodiments of the present disclosure and are not therefore to be considered limiting of its scope, the principles of the present invention are described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0006] Figure 1 illustrates an example enterprise network and cloud-based service mesh according to various embodiments;

[0007] Figure 2A and 2B illustrates an example enterprise network and cloud-based service mesh according to various embodiments;

[0008] Figure 3 illustrates example methods according to various embodiments;

[0009] Figure 4 illustrates example network devices according to various embodiments; and

[0010] Figure 5 An example computing device is illustrated in accordance with various embodiments. DETAILED DESCRIPTION

[0011] Various embodiments of the present disclosure are discussed in detail below. Although specific implementations are discussed, it should be understood that this is for illustrative purposes only. Those skilled in the relevant art will recognize that other components and configurations may be used without departing from the spirit and scope of the present disclosure. Therefore, the following description and drawings are illustrative and should not be interpreted as limiting. Many specific details are described to provide a thorough understanding of the present disclosure. However, in some cases, in order to avoid confusing the description, well-known or traditional details are not described. References to an embodiment or an embodiment in the present disclosure may be references to the same embodiment or any embodiment; and, such references mean at least one embodiment.

[0012] Reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. The phrase "in one embodiment" appearing in various places in the specification is not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. In addition, various features are described that may be exhibited by some embodiments but not by others.

[0013] The terms used in this specification generally have their ordinary meanings in the art, in the context of the present disclosure, and in the specific context in which each term is used. Alternative language and synonyms may be used for any one or more terms discussed herein, and special attention should not be paid to whether a term is elaborated or discussed herein. In some cases, synonyms for certain terms are provided. The enumeration of one or more synonyms does not exclude the use of other synonyms. The use of examples anywhere in this specification (including examples of any terms discussed herein) is illustrative only and is not intended to further limit the scope and meaning of the present disclosure or any example terms. Likewise, the present disclosure is not limited to the various embodiments provided in this specification.

[0014] Without limiting the scope of the present disclosure, examples of instruments, devices, methods and related results thereof according to embodiments of the present disclosure are given below. It should be noted that, for the convenience of the reader, titles or subtitles may be used in the examples, which should never limit the scope of the present disclosure. Unless otherwise defined, the technical and scientific terms used herein have the meanings commonly understood by those of ordinary skill in the art to which the present disclosure belongs. In the event of a conflict, this document (including definitions) shall prevail.

[0015] Additional features and advantages of the present disclosure will be set forth in the subsequent description, and in part will be apparent from the description, or may be learned by the practice of the principles disclosed herein. The features and advantages of the present disclosure may be realized and obtained by the means and combinations specifically indicated in the appended claims. These and other features of the present disclosure will become more apparent from the following description and the appended claims, or may be learned by the practice of the principles set forth herein.

[0016] Overview

[0017] The present technology involves extending the policy framework from native enterprise networks to cloud-based service mesh frameworks. The technical details imply that a first communication is sent from the enterprise network controller to the service mesh coordinator to inform the service mesh coordinator of the traffic segmentation policy. These policies can then be applied to traffic originating from within the enterprise network via a layer 7 extension header corresponding to the traffic segmentation policy.

[0018] Example Embodiments

[0019] Various embodiments of the subject technology are directed to integrating enterprise policies into a service mesh. The technology overcomes the challenges of communicating when transitioning from an enterprise network boundary to a cloud-based service mesh boundary of inter-communicating microservices.

[0020] This technology recognizes the need to control how services within a service mesh communicate with each other and with the outside world. As deployed today, the policies defined for the service mesh are separate from the policies defined for enterprise users, devices, and workloads. This technology addresses these issues by providing a mechanism to extend enterprise policies and segmentation semantics into the service mesh.

[0021] The need for this technology becomes particularly important given the need to maintain trust across domains, especially when they span enterprise-controlled networks. The ability to deliver enterprise trust policies to the cloud is one of the important uses of this technology.

[0022] The present technology provides a solution for integrating enterprise policies into a service mesh under two different deployment models, depending on whether the policy translation on the data plane occurs inside or outside the enterprise network. The technology translates the policies and the context used to express and enforce the policies in the enterprise to the service mesh. This can be achieved in part by connecting an enterprise (EN) policy orchestrator with a service mesh orchestrator interface and translating the context from one domain (enterprise to service mesh and vice versa) to another to enable unified end-to-end policies that can be enforced across the enterprise and cloud-based service meshes. The orchestrator policies can also be supplemented with data plane policy information, such as by adding X-SGT or X-VNI tags to HTTP traffic.

[0023] Figure 1 An embodiment of the present technology is illustrated in which the conversion of data plane metadata occurs outside the enterprise network. Figure 2A and 2B ), the enterprise decides to use an available service mesh implementation without any modifications and / or leverages products from third parties that provide container-as-a-service (CaaS) infrastructure. In this scenario, the enterprise has no control over the service mesh infrastructure and can only interact with it through the well-defined APIs of the service mesh orchestrator. In this case, it is not possible to bring the enterprise data plane into the service mesh because the service mesh proxy cannot handle the enterprise-specific data plane.

[0024] Enterprise networks route and restrict access for users or devices based on a set of policies that govern the network. Sometimes, an enterprise network user or device will need to use an external network to access services, send communications, or complete other necessary tasks. In these cases, the enterprise may have a vested interest in ensuring that its network management policies are enforced outside of the enterprise network.

[0025] To allow policy enforcement on third-party service meshes, the system can supplement data plane traffic with policy tags encoded at application layer 7, and control plane policies from the enterprise network can be translated to make them accessible to the service mesh. An example of an orchestration system that can use these translated policies is ISTIO.

[0026] like Figure 1 As shown, enterprise network 110 includes user devices 120, 121, and 122 and border gateway router 140. Each user device 120, 121, and 122 is connected through edge nodes 130, 131, and 132 before traffic can move to border 140. Enterprise network policies are set by enterprise policy coordinator 100 (such as, for example, CISCO DNA CENTER).

[0027] The service mesh 160 includes a plurality of software services 180, 181, and 182 (microservices) for performing the functions of the cloud-hosted application. The service mesh 160 also includes a service mesh coordinator 150 and a general agent 165 and service agents 170, 171, and 172. In some embodiments, the service agents 170, 171, and 172 can be Envoy agents on the ISTIO control plane.

[0028] The enterprise policy orchestrator 100 can convert enterprise policies into primitives that the service mesh orchestrator 150 understands and uses through the policy conversion service 105. In the current embodiment, the enterprise network 110 applies policies based on the identities and credentials of users 120, 121 and 122 or their devices 125, 126 and 127. However, in order for these policies to be operable by the service mesh 160, the policies on the users or devices (layer 2 or layer 3) need to be converted to policies on the services (layer 7). For example, policy conversion may result in HTTP / S traffic that indicates that it carries a certain X-SGT label value cannot access a specific service 180 in the service mesh 160. This policy conversion also needs to take into account that the return traffic from the service mesh 160 needs to be correctly labeled with enterprise semantics (e.g., adding X-SGT and X-VNI labels to HTTP traffic). Policy conversion must include the correct configuration of the service mesh orchestrator 150 to ensure that these labels are applied correctly. This is required to convert native service mesh traffic back to enterprise encapsulated traffic in the data plane conversion component.

[0029] The data plane switching service 145 can be a data plane component that can convert back and forth between enterprise encapsulated data plane traffic (e.g., VXLAN-GPO) and native service mesh traffic (e.g., HTTP / S). One possible instantiation of this component is in the form of a data plane switching service 145 that accepts enterprise encapsulated traffic, extracts enterprise tags (e.g., VNI and SGT fields carried in the VXLAN-GPO header), and then injects enterprise-specific tags into the original HTTP / S header of the packet (e.g., X-SGT and X-VNI extension tags). If the traffic is HTTP / S, in order to inject the HTTP / S tag, the data plane switching service 145 will also terminate the transport layer security (TLS) connection from the enterprise 110 and create a new TLS connection to the service mesh 160. The reverse path from the service mesh 160 to the enterprise 110 is similar via this data plane component.

[0030] Synergistically, control plane policy translation combined with data plane traffic translation allows enterprise policies on layer 2 or layer 3 entities (users or devices) to be applied to layer 7 entities (services) in service mesh 160. In some embodiments, policy translation service 105 may be a third party service or may be attached to enterprise network policy orchestrator 100. In some embodiments, data plane translation service 145 may be a third party service or may be attached to edge 140.

[0031] Therefore, in Figure 1In the example, enterprise policy orchestrator 100 can convert enterprise policies into primitives that can be understood and operated by service mesh 160. Data plane conversion service 145 is used to convert data plan traffic encapsulation into HTTP traffic so that it can be understood by service mesh 160 (or conversely, convert HTTP traffic into properly encapsulated data plan traffic back to enterprise network 110). This conversion takes advantage of the data plane conversion that occurs between enterprise encapsulation and native service mesh traffic.

[0032] Figure 2A and 2B An embodiment of the present technology is illustrated in which the conversion of policies in the data plane occurs within the enterprise network. In this embodiment, a proxy is used at the edge of the enterprise network that encapsulates enterprise traffic with HTTP / S labels.

[0033] The enterprise network policy coordinator 100 injects a proxy 190, 191 or 192 at each edge node 130, 131 and 132 to convert back and forth between enterprise encapsulated HTTP / S traffic and native service mesh HTTP / S traffic. The possible instantiation of these proxies in the enterprise network 110 is in the form of injecting enterprise specific tags (such as X-SGT and X-VNI extension tags) in the original HTTP / S header of the packet and abandoning the intermediate step of enterprise encapsulated data plane traffic (such as VXLAN-GPO) with SGT / VNI fields in full. The reverse path from the service mesh 160 to the enterprise 110 is similar. This embodiment does not require a data plane conversion service 145 at the boundary 140 or elsewhere in the system.

[0034] Figure 2B Enterprise metadata is added to the traffic at each edge node 130, 131, and 132. The metadata encapsulated in the traffic at the edges 130, 131, and 132 can provide further context to the traffic and allow for more nuanced policy application. This metadata encapsulation is possible because data plane transitions occur at the edge in the enterprise network 110. The metadata can include specific information about any user 120, 121, and 122 or device 125, 126, or 127 (work environment, past device behavior, security permissions, etc.), general activity on the enterprise network 110, or other relevant activity for policy application.

[0035] Figure 3 Example methods according to various embodiments are illustrated.

[0036] The method begins when an enterprise network policy orchestrator 100 in an enterprise network 110 sends 300 at least one policy to a service mesh orchestrator 150 on a service mesh 160. These policies pass through a policy transformation service 105 before reaching the service mesh orchestrator 150 on the service mesh 160. The transformation takes enterprise-specific policies and converts them into a public API that the service mesh 160 can understand and execute.

[0037] On service mesh 160, service mesh coordinator 150 takes the received policies and coordinates them between proxy 165 and service proxies 170, 171, and 172. It sets up the proxies to understand labels embedded in traffic from enterprise network 110, such as X-SGT and X-VNI labels, and applies the policies according to the policies of enterprise network 110.

[0038] After the policy has been transferred from the enterprise to the service grid, edge nodes 130, 131, and 132 receive (310) traffic from devices 125, 126, and 127 on enterprise network 110. Figure 1 , 2A In the system described in 2B , the traffic is HTTP / S traffic, but other network traffic can also be received and processed by edge nodes 130 , 131 , and 132 .

[0039] Edge nodes 130, 131, and 132 proceed to forward (320) the network traffic to proxy 165 (and / or service proxy 170, 171, or 172), which understands at least one policy previously communicated by enterprise network policy orchestrator 100. In various embodiments, this forwarding process may be performed in different ways.

[0040] Traffic can be delivered to the native enterprise edge 140 ( Figure 1 ). In this embodiment, edge nodes 130, 131, and 132 forward traffic along the VXLAN and populate the SGT or VNI field with appropriate policy specifications. Data plane switching service 145 uses the SGT / VNI field and encapsulates HTTP / S traffic X-SGT / X-VNI tags for use by proxy 165 (and / or service proxy 170, 171, or 172).

[0041] In other embodiments, traffic may be injected by the enterprise network policy 100 into a proxy process at the edge 130, 131, or 132 ( Figure 2A and 2BIn this embodiment, traffic is immediately populated with HTTP / S tags (X-SGT or X-VNI tags) and may not be passed along the VXLAN with the SGT / VNI fields populated.

[0042] Proxy 165 processes (330) the incoming traffic based on any policies received by the service mesh. This processing may be influenced by information that the enterprise encapsulates in the data based on the policy, or in some embodiments, by information added to the traffic by metadata ( Figure 2B ). The proxy will route the traffic through service proxy 170, 171, or 172 to the appropriate service 180, 181, or 182 and apply the appropriate restrictions.

[0043] To satisfy the service request, service grid 160, service grid coordinator 150, and service proxies 170, 171, and 172 work together to allow services 180, 181, and 182 to satisfy all, some, or none of the service requirements. Data is received from services 180, 181, and 182 at service proxies 170, 171, and 172, respectively, and this traffic restores the X-SGT / X-VNI header from the service request. The response moves back through the system, with reverse transformation and conversion taking place at the same entity that the service request underwent transformation and conversion.

[0044] Figure 4 An exemplary network device 410 suitable for implementing the present invention is shown. It may be Figure 1 , 2A 462 is a part of any device included in or 2B, which can send or receive data through the network. Network device 410 includes a main central processing unit (CPU) 462, an interface 468 and a bus 415 (e.g., a PCI bus). It preferably performs its functions under the control of software including an operating system and any appropriate application software. CPU 462 may include one or more processors 463, such as processors from the Motorola series of microprocessors or the MIPS series of microprocessors. In an alternative embodiment, processor 463 is a specially designed hardware for controlling the operation of router 410. In a specific embodiment, memory 461 (e.g., non-volatile RAM and / or ROM) also forms a part of CPU 462. However, there are many different ways in which memory can be coupled to the system.

[0045] Interfaces 468 are typically provided as interface cards (sometimes referred to as "line cards"). Typically, they control the sending and receiving of data packets over the network, and sometimes support other peripheral devices used with router 410. Interfaces that may be provided include Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, and the like. In addition, various ultra-high-speed interfaces may be provided, such as fast token ring interfaces, wireless interfaces, Ethernet interfaces, Gigabit Ethernet interfaces, ATM interfaces, HSSI interfaces, POS interfaces, FDDI interfaces, and the like. Typically, these interfaces may include ports suitable for communicating with appropriate media. In some cases, they may also include independent processors and, in some cases, volatile RAM. Independent processors may control communication-intensive tasks such as packet switching, media control, and management. By providing separate processors for communication-intensive tasks, these interfaces allow the main microprocessor 462 to effectively perform routing calculations, network diagnostics, security functions, and the like.

[0046] Although Figure 4 The system shown is a specific network device of the present invention, and it is by no means the only network device architecture that can implement the present invention. For example, an architecture with a single processor that handles communications as well as routing calculations, etc. is often used. In addition, other types of interfaces and media can also be used with routers.

[0047] Regardless of the configuration of the network device, it can employ one or more memories or memory modules (including memory 461) that are configured to store program instructions for general network operations and mechanisms for roaming, route optimization, and routing functions described herein. For example, program instructions can control the operation of an operating system and / or one or more applications. One or more memories can also be configured to store tables such as mobile binding, registration, and association tables.

[0048] Figure 5 An example of a computing system 500 is shown, which may be, for example, Figure 1 , 2A 2B, wherein the components of the system communicate with each other using connection 505. Connection 505 can be a physical connection via a bus, or a direct connection to processor 510, such as in a chipset architecture. Connection 505 can also be a virtual connection, a network connection, or a logical connection.

[0049] In some embodiments, computing system 500 is a distributed system, where the functionality described in the present disclosure may be distributed across a data center, multiple data centers, a peer-to-peer network, etc. In some embodiments, one or more of the described system components represent a number of such components, each of which performs some or all of the functionality for which the component is described. In some embodiments, a component may be a physical or virtual device.

[0050] The example system 500 includes at least one processing unit (CPU or processor) 510 and connections 505 that couple various system components including system memory 515 (e.g., read only memory (ROM) 520 and random access memory (RAM) 525) to the processor 510. The computing system 500 may include a cache with high-speed memory 512 that is directly connected to, adjacent to, or integrated as part of the processor 510.

[0051] Processor 510 may include any general purpose processor and hardware services or software services configured to control processor 510, such as services 532, 534, and 536 stored in storage device 530, as well as special purpose processors where software instructions are incorporated into the actual processor design. Processor 510 may essentially be a completely independent computing system, containing multiple cores or processors, buses, memory controllers, caches, etc. Multi-core processors may be symmetric or asymmetric.

[0052] To enable user interaction, the computing system 500 includes an input device 545, which can represent any number of input mechanisms, such as a microphone for voice, a touch-sensitive screen for gesture or graphic input, a keyboard, a mouse, motion input, voice, etc. The computing system 500 may also include an output device 535, which may be one or more of a variety of output mechanisms known to those skilled in the art. In some cases, a multimodal system may enable a user to provide multiple types of input / output to communicate with the computing system 500. The computing system 500 may include a communication interface 540, which may generally govern and manage user input and system output. There is no restriction on the operation of any particular hardware configuration, so the basic functionality here can be easily replaced with improved hardware or firmware configurations as they are being developed.

[0053] The storage device 530 may be a non-volatile storage device and may be a hard disk or other type of computer-readable medium that can store computer-accessible data, such as a magnetic tape, a flash memory card, a solid-state memory device, a digital versatile disk, a cassette, a random access memory (RAM), a read-only memory (ROM), and / or some combination of these devices.

[0054] Storage device 530 may include software services, servers, services, etc., which cause the system to perform functions when processor 510 executes code defining such software. In some embodiments, hardware services that perform specific functions may include software components stored in computer-readable media in combination with the necessary hardware components (e.g., processor 510, connection 505, output device 535, etc.) to perform the functions.

[0055] For clarity of explanation, in some cases, the technology may be presented as including separate functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or a combination of hardware and software.

[0056] Any steps, operations, functions or processes described herein may be performed or implemented by hardware and software services or combinations of services, either alone or in combination with other devices. In some embodiments, a service may be software that resides in a memory of one or more servers of a client device and / or a content management system and performs one or more functions when a processor executes software associated with the service. In some embodiments, a service is a program or a collection of programs that perform a specific function. In some embodiments, a service may be considered a server. The memory may be a non-transient computer-readable medium.

[0057] In some embodiments, computer-readable storage devices, media, and memories may include cables or wireless signals containing bit streams, etc. However, when referred to, non-transitory computer-readable storage media explicitly excludes media such as energy, carrier signals, electromagnetic waves, and signals themselves.

[0058] The method according to the above example can be implemented using computer executable instructions stored or otherwise available from a computer readable medium. Such instructions may include, for example, instructions and data that cause or otherwise configure a general-purpose computer, a special-purpose computer, or a special-purpose processing device to perform a specific function or functional group. The part of the computer resources used can be accessed through a network. The computer executable instructions can be, for example, binary, intermediate format instructions, such as assembly language, firmware, or source code. Examples of computer readable media that can be used to store instructions, information used, and / or information created during the method according to the described examples include disks or optical disks, solid-state storage devices, flash memory, USB devices provided with non-volatile memory, network storage devices, etc.

[0059] Devices implementing methods according to these disclosures may include hardware, firmware, and / or software, and may take any of a variety of form factors. Typical examples of such form factors include servers, laptops, smart phones, small form factor personal computers, personal digital assistants, etc. The functions described herein may also be embodied in peripheral devices or add-on cards. As a further example, such functions may also be implemented on different chips or circuit boards between different processes executed in a single device.

[0060] Instructions, media for transmitting such instructions, computing resources for executing them, and other structures for supporting such computing resources are the means for providing the functionality described in these disclosures.

[0061] Although various examples and other information are used to explain aspects within the scope of the appended claims, limitations to the claims should not be implied based on specific features or arrangements in such examples, as a person of ordinary skill will be able to derive a variety of implementations using these examples. In addition, although some subject matter may have been described in language specific to examples of structural features and / or method steps, it should be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or actions. For example, such functionality may be distributed differently or performed in components other than those identified herein. Instead, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.

Claims

1. At least one non-transitory computer-readable medium comprising instructions stored thereon, the instructions enabling at least one processor to perform the following operations: sending, by an enterprise network controller of an enterprise network, a first communication to a service mesh coordinator of a cloud-based service mesh, wherein the first communication notifies the service mesh coordinator of a traffic segmentation policy to be applied in the service mesh to traffic originating from the enterprise network and a layer 7 extension header corresponding to the traffic segmentation policy; and A second communication is sent by the enterprise network controller to the data plane switching service, wherein the second communication instructs the data plane switching service to convert a layer 2 or layer 3 field of the network traffic destined for the service mesh to the layer 7 extension header before forwarding the network traffic to the service mesh.

2. The at least one non-transitory computer readable medium of claim 1, wherein: The layer 2 or layer 3 fields include an SGT field and a VNI field, which are converted into an extension header for HTTP(S) network traffic.

3. The at least one non-transitory computer-readable medium of claim 1 , wherein the second communication further instructs the data plane switching service to: receiving layer 7 network traffic from the service mesh; Detect the layer 7 extension header: encapsulating the network traffic into a VXLAN tunnel between an enterprise edge network device of the enterprise network and the data plane switching service; and Creates a layer 2 or layer 3 field based on a detected layer 7 extension header.

4. A method for extending an enterprise trusted policy framework to a cloud native application, comprising: sending, by an enterprise network controller of an enterprise network, a first communication to a service mesh coordinator of a cloud-based service mesh, wherein the first communication notifies the service mesh coordinator of: a traffic segmentation policy to be applied in the service mesh to traffic originating from the enterprise network, and a layer 7 extension header corresponding to the traffic segmentation policy; as well as A second communication is sent by the enterprise network controller to the data plane switching service, wherein the second communication instructs the data plane switching service to convert a layer 2 or layer 3 field of the network traffic destined for the service mesh to the layer 7 extension header before forwarding the network traffic to the service mesh.

5. The method of claim 4, wherein the layer 2 or layer 3 field includes an SGT field and a VNI field, which are converted into an extension header for HTTP(S) network traffic.

6. The method of claim 4, wherein the second communication further instructs the data plane switching service to: receiving layer 7 network traffic from the service mesh; Detect the layer 7 extension header: encapsulating the network traffic into a VXLAN tunnel between an enterprise edge network device of the enterprise network and the data plane switching service; and Creates a layer 2 or layer 3 field based on a detected layer 7 extension header.

7. A system for extending an enterprise trusted policy framework to cloud native applications, comprising: An enterprise network controller of an enterprise network, the enterprise network controller being configured to: sending a first communication that notifies a service mesh coordinator of a cloud-based service network of a traffic segmentation policy to be applied to traffic originating from an enterprise network and a layer 7 extension header corresponding to the traffic segmentation policy; as well as A second communication is sent, wherein the second communication instructs the data plane switching service to convert a layer 2 or layer 3 field of the network traffic destined for the service mesh to the layer 7 extension header before forwarding the network traffic to the service mesh.

8. The system of claim 7, wherein the layer 2 or layer 3 field includes an SGT field and a VNI field, which are converted into an extension header for HTTP(S) network traffic.

9. The system of claim 7, wherein the second communication further instructs the data plane switching service to: receiving layer 7 network traffic from the service mesh; Detect the layer 7 extension header: encapsulating the network traffic into a VXLAN tunnel between an enterprise edge network device of the enterprise network and the data plane switching service; and Creates a layer 2 or layer 3 field based on a detected layer 7 extension header.