Smart security for zero trust in mobile networks using packet forwarding control protocols with security platform

By using a perimeter security platform employing PFCP, Radius, and Diameter protocols at the perimeter of mobile networks to monitor and apply security policies, the complexity of deploying security platforms within mobile networks is resolved, achieving context-based intelligent security and enhanced network protection.

CN121925819APending Publication Date: 2026-04-24PALO ALTO NETWORKS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480062014.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-11-30
Filing Date
2024-09-30
Publication Date
2026-04-24

Smart Images

  • Figure CN121925819A_ABST
    Figure CN121925819A_ABST
Patent Text Reader

Abstract

Techniques for applying intelligent security for zero trust in a mobile network using a packet forwarding control protocol (PFCP) with a perimeter security platform are disclosed. In some embodiments, a system / process / computer program product for applying smart security for zero trust in a mobile network using a perimeter security platform (e.g., using a PFCP protocol) includes deploying a security platform in a 5G and / or 4G / LTE mobile network environment, and monitoring the PFCP message at a security platform in a separate 5G network and / or 4G / LTE network (e.g., with a CUP architecture). In particular, the security platform is configured to process a PFCP message including a PFCP session setup request / response message and / or a PFCP session modification request / response message to extract contextual information that can include user equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Persistent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN, and / or RAT type information. The security platform is further configured to apply security policies (e.g., enforce one or more security rules) based on the contextual information.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to other applications This application claims priority to U.S. Provisional Patent Application No. 63 / 546,724, filed October 31, 2023, entitled “INTELLIGENT SECURITY FOR ZEROTRUST IN MOBILE NETWORKS WITH SECURITY PLATFORMS,” which is incorporated herein by reference for all purposes. Background Technology

[0002] Firewalls generally protect networks from unauthorized access while allowing authorized communication to pass through. A firewall is typically a device or collection of devices that provides firewall functionality for network access, or software running on a device such as a computer. For example, a firewall can be integrated into the operating system of a device (e.g., a computer, smartphone, or other type of network-enabled device). Firewalls can also be integrated into computer servers, gateways, network / routing devices (e.g., network routers), or data devices (e.g., security devices or other types of specialized devices) or implemented as software on these devices.

[0003] Firewalls typically deny or allow network traffic based on sets of rules. These sets of rules are usually called policies. For example, a firewall can filter inbound traffic by applying a set of rules or policies. A firewall can also filter outbound traffic by applying a set of rules or policies. Firewalls can also perform basic routing functions. Attached Figure Description

[0004] Various embodiments of the invention are disclosed in the following detailed description and accompanying drawings.

[0005] Figure 1A This is a block diagram of a first example service deployment architecture for applying zero-trust intelligent security to 5G and 4G mobile networks using the PFCP protocol and a perimeter security platform, according to some embodiments.

[0006] Figure 1B This is a block diagram of a second example service deployment architecture for applying a 5G mobile network service deployment architecture for zero-trust intelligent security in 5G and 4G mobile networks using the PFCP protocol and a perimeter security platform, according to some embodiments.

[0007] Figure 1C This is a block diagram of a third example service deployment architecture for applying a 4G mobile network service deployment architecture for zero-trust intelligent security in a mobile network using the PFCP protocol and leveraging a perimeter security platform, according to some embodiments.

[0008] Figure 2A This is a protocol diagram of the Radius billing message flow in a 5G network according to some embodiments.

[0009] Figure 2B This is a protocol diagram of the Radius billing update message flow in a 5G network according to some embodiments.

[0010] Figure 2C This is a block diagram of a first example service deployment architecture for applying a zero-trust intelligent security 5G mobile network in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0011] Figure 2D This is a block diagram of a second example service deployment architecture for applying a zero-trust intelligent security 5G mobile network in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0012] Figure 2E This is a protocol diagram of the Radius message flow in a 4G / LTE network according to some embodiments.

[0013] Figure 2F This is a protocol diagram of the Radius billing update message flow in a 4G / LTE network according to some embodiments.

[0014] Figure 2G This is a block diagram of a first example service deployment architecture for applying a zero-trust smart security 4G mobile network in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0015] Figure 3A This is a protocol diagram of the Diameter billing message flow in a 5G network according to some embodiments.

[0016] Figure 3B This is a protocol diagram of the Radius billing update message flow in a 5G network according to some embodiments.

[0017] Figure 3C This is a block diagram of a first example service deployment architecture for applying a perimeter security platform to a 5G mobile network with zero-trust intelligent security, based on some embodiments of the Diameter protocol.

[0018] Figure 3D This is a protocol diagram of the Diameter billing message flow on the SGi interface in a 4G / LTE network according to some embodiments.

[0019] Figure 3EThis is a protocol diagram of the Diameter billing update message flow in a 4G / LTE network according to some embodiments.

[0020] Figure 3F This is a block diagram of a first example service deployment architecture for applying a perimeter security platform to a 4G mobile network with zero-trust intelligent security, based on some embodiments of the Diameter protocol.

[0021] Figure 4A This is a functional diagram of hardware components for applying smart security for zero trust in a network device in a mobile network using a perimeter security platform, according to some embodiments.

[0022] Figure 4B This is a functional diagram of the logical components of a network device for applying zero-trust smart security in a mobile network using a perimeter security platform, according to some embodiments.

[0023] Figure 5 This is a flowchart illustrating the process of applying intelligent security for zero trust in a mobile network using the PFCP protocol according to some embodiments.

[0024] Figure 6 This is a flowchart illustrating the process of applying intelligent security for zero trust in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0025] Figure 7 This is a flowchart illustrating the process of applying intelligent security for zero trust in mobile networks using the Diameter protocol and a perimeter security platform, according to some embodiments. Detailed Implementation

[0026] This invention can be implemented in numerous ways, including as a process; an apparatus; a system; a composition of matter; a computer program product embodied on a computer-readable storage medium; and / or a processor, such as a processor configured to execute instructions stored on and / or provided by memory coupled to the processor. In this specification, these embodiments or any other form of the invention may be referred to as technology. Generally, the order of steps of the disclosed process can be varied within the scope of the invention. Unless otherwise stated, components described as configured to perform a task (such as processors or memory) can be implemented as general components temporarily configured to perform a task at a given time or manufactured as specific components to perform a task. As used herein, the term 'processor' refers to one or more devices, circuits, and / or processing cores configured to process data (such as computer program instructions).

[0027] The following detailed description of one or more embodiments of the invention, together with the accompanying drawings illustrating the principles of the invention, provides for the purpose of illustrating these embodiments. The invention has been described in conjunction with these embodiments, but is not limited to any particular embodiment. The scope of the invention is limited only by the claims, and the invention includes many alternatives, modifications, and equivalents. To provide a thorough understanding of the invention, numerous specific details are set forth in the following description. These details are provided for illustrative purposes, and the invention may be practiced without some or all of these specific details. For the purpose of clarity, technical materials known in the art related to the invention have not been described in detail so as not to unnecessarily obscure the invention.

[0028] Firewalls typically protect networks from unauthorized access while allowing authorized communication to pass through. A firewall is usually a device, a collection of devices, or software running on a device that provides firewall functionality for network access. For example, a firewall can be integrated into the operating system of a device (e.g., a computer, smartphone, or other type of network-enabled device). Firewalls can also be integrated into various types of devices or security devices (such as computer servers, gateways, network / routing devices (e.g., network routers), or data devices (e.g., security devices or other types of dedicated devices)) or executed as software applications on various types of devices or security devices.

[0029] Firewalls typically deny or allow network traffic based on a set of rules. These sets of rules are often called policies (e.g., network policies or network security policies). For example, a firewall can filter inbound traffic by applying a set of rules or policies to prevent unwanted external traffic from reaching a protected device. A firewall can also filter outbound traffic by applying a set of rules or policies (e.g., allow, block, monitor, notify, or log, and / or other actions that can be specified in firewall / security rules or firewall / security policies, which may be triggered based on various criteria such as those described herein). Firewalls can also apply antivirus protection, malware detection / prevention, or intrusion protection by applying a set of rules or policies.

[0030] Security devices (e.g., security apparatuses, security gateways, security services, and / or other security devices) may include various security functions (e.g., firewalls, anti-malware, intrusion prevention / detection, proxies, and / or other security functions), networking functions (e.g., routing, quality of service (QoS), workload balancing of network-related resources, and / or other networking functions), and / or other functions. For example, routing functions may be based on source information (e.g., source IP address and port), destination information (e.g., destination IP address and port), and protocol information.

[0031] Basic packet filtering firewalls (such as packet-filtering firewalls or first-generation firewalls, which are stateless packet-filtering firewalls) filter network traffic by examining individual packets transmitted over the network. Stateless packet-filtering firewalls typically examine each packet itself and apply rules based on the examined packet (e.g., using a combination of packet source and destination address information, protocol information, and port number).

[0032] Application firewalls can also perform application-layer filtering (e.g., using application-layer filtering firewalls or second-generation firewalls, which operate at the application level of the TCP / IP stack). Application-layer filtering firewalls or application firewalls can generally identify certain applications and protocols (e.g., web browsing using Hypertext Transfer Protocol (HTTP), Domain Name System (DNS) requests, file transfer using File Transfer Protocol (FTP), and various other types of applications and other protocols such as Telnet, DHCP, TCP, UDP, and TFTP (GSS)). For example, application firewalls can block unauthorized protocols attempting to communicate on standard ports (e.g., application firewalls can generally be used to identify unauthorized / out-of-policy protocols attempting to sneak through using non-standard ports used for that protocol).

[0033] Stateful firewalls can also perform state-based packet inspection, where each packet is examined within the context of a series of packets associated with a flow / packet stream of packets traveling through the network (e.g., a stateful firewall or a third-generation firewall). This firewall technique is generally referred to as stateful packet inspection because it maintains a record of all connections traversing the firewall and is able to determine whether a packet is the start of a new connection, part of an existing connection, or an invalid packet. For example, the state of a connection itself can be one of the criteria for triggering rules within a policy.

[0034] Advanced or next-generation firewalls can perform stateless and stateful packet filtering and application-layer filtering as discussed above. Next-generation firewalls can also perform additional firewall technologies. For example, certain newer firewalls, sometimes referred to as advanced or next-generation firewalls, can also identify users and content. In particular, some next-generation firewalls are expanding the list of applications they can automatically identify to thousands of applications. Examples of such next-generation firewalls are commercially available from Palo Alto Networks Ltd. (e.g., Palo Alto Networks' PA series next-generation firewalls, Palo Alto Networks' VM series virtualization next-generation firewalls, and CN series container next-generation firewalls).

[0035] For example, Palo Alto Networks' next-generation firewall enables enterprises and service providers to use a variety of identification technologies to identify and control applications, users, and content, not just ports, IP addresses, and packets. These identification technologies include: App-ID for accurate application identification. TM (e.g., APP-ID), User-ID used for user identification (e.g., by user or user group). TM (e.g., User-ID), and Content-ID used for real-time content scanning (e.g., controlling web browsing and restricting data and file transfers). TM (For example, Content-ID). These identification technologies allow enterprises to reliably achieve application purposes using business-related concepts, rather than following traditional methods provided by conventional port-blocking firewalls. Furthermore, dedicated hardware for next-generation firewalls (e.g., dedicated hardware implemented as dedicated devices) generally provides a higher level of performance for application auditing compared to software running on general-purpose hardware. Dedicated hardware for next-generation firewalls, such as security devices provided by Palo Alto Networks Ltd., utilizes dedicated, function-specific processing tightly integrated with a single-channel software engine to maximize network throughput while minimizing latency in Palo Alto Networks' PA series of next-generation firewalls.

[0036] A review of technologies for applying intelligent security for zero trust in mobile networks using perimeter security platforms.

[0037] For devices in mobile networks (e.g., 4G / LTE, 5G and beyond), there are technical and security challenges related to service provider networks.

[0038] For example, some mobile network service providers and / or enterprises with private mobile networks prefer not to have their security platforms located within their mobile core networks (e.g., 4G / 5G core networks).

[0039] Furthermore, compared to security platforms deployed within mobile core networks (e.g., 4G / 5G core networks), many security operations teams (e.g., IT / security administrators) have more comfort and control over perimeter security platform deployments, which may be more complex and / or present additional complexities and / or technical challenges when deployed within mobile core networks (e.g., 4G / 5G core networks).

[0040] Therefore, new and improved security technologies are needed for devices communicating in such service provider network environments (e.g., mobile networks, including various 4G / LTE, 5G and beyond mobile networks).

[0041] Specifically, what is needed are new and improved solutions for monitoring such network traffic and for applying intelligent security for zero trust in mobile network environments using perimeter security platforms, such as for devices (e.g., UEs) communicating through service provider networks (e.g., including applying context-based and / or enhanced security in mobile networks based on subscriber ID / International Mobile Subscriber Identity (IMSI), equipment ID / International Mobile Equipment Identity (IMEI), network slice ID / Single Network Slice Selection Assistance Information (S-NSSAI), IP-to-Mobile Subscriber Traffic Mapping and / or other context-based information to facilitate enhanced security in such mobile network environments).

[0042] Therefore, the disclosed technology facilitates the application of systems / processes / computer programs for intelligent security targeting zero trust in mobile networks using perimeter security platforms, as will now be further described below.

[0043] For example, various technologies are disclosed for applying smart security based on mobile network identity (e.g., 4G and / or 5G mobile identity) on the perimeter of a mobile network using one or more interfaces (such as a 4G SGi interface and / or a 5G N6 interface, as will be further described below).

[0044] In some embodiments, system / process / computer program products for applying zero-trust intelligent security in mobile networks using a perimeter security platform (e.g., using the PFCP protocol) include deploying the security platform in a 5G and / or 4G / LTE mobile network environment and monitoring PFCP messages at the security platform in a standalone 5G and / or 4G / LTE network (e.g., with a CUPS architecture). Specifically, the security platform is configured to process PFCP messages, including PFCP session establishment request / response messages and / or PFCP session modification request / response messages, to extract contextual information, which may include User Equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Permanent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN, and / or RAT type information. The security platform is also configured to apply security policies (e.g., enforce one or more security rules) based on the contextual information.

[0045] In some embodiments, system / process / computer program products for applying intelligent security for zero trust in mobile networks using a perimeter security platform (e.g., using the Radius protocol) include deploying the security platform in a 5G and / or 4G / LTE mobile network environment and monitoring Radius messages at the security platform in a separate 5G and / or 4G / LTE network. Specifically, the security platform is configured to process Radius messages including charging request (start) / charging response (start) and charging request (temporary update) / charging response (temporary update) messages to extract contextual information, which may include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Radius message include: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – APN). The security platform is also configured to apply security policies (e.g., enforce one or more security rules) based on the contextual information.

[0046] In some embodiments, system / process / computer program products for applying zero-trust intelligent security in mobile networks using a perimeter security platform (e.g., using the Diameter protocol) include deploying the security platform in a 5G and / or 4G / LTE mobile network environment and monitoring Diameter messages at the security platform in a standalone 5G and / or 4G / LTE network. Specifically, the security platform is configured to process Diameter messages including charging request (start) / charging response (start) and charging request (provisional) / charging response (provisional) messages to extract contextual information, which may include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Diameter message include: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – APN). The security platform is also configured to apply security policies (e.g., enforce one or more security rules) based on the contextual information.

[0047] In some embodiments, a system / process / computer program product for applying zero-trust intelligent security in a mobile network using a perimeter security platform (e.g., using Packet Forwarding Control Protocol (PFCP)) includes monitoring network traffic on the mobile network at the security platform to identify new sessions, wherein the security platform is located at the perimeter of the mobile network; determining metadata associated with the new session by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes Packet Forwarding Control Protocol (PFCP); and enforcing security policies on the new session at the security platform based on the metadata to apply context-based security in the mobile network. In this example embodiment, the security platform may be configured to process PFCP messages to extract metadata from the network traffic via one or more interfaces. The security platform may be located at one or more interfaces at the perimeter of the mobile network (e.g., one or more interfaces selected from SGi, Sxb, N4, and N6). Meta information may include User Equipment (UE) IP information, International Mobile Subscription Identity (IMSI) information, Subscription Permanent Identifier (SUPI) information, IMEI / PEI information, S-NSSAI information, APN / DNN information, RAT type information, user location information, and / or any combination of the above. Similarly, the security platform can be configured with multiple security policies to apply vulnerability protection, intrusion prevention, antivirus, anti-spyware, DNS security, denial-of-service (DoS) protection, and / or cloud-based security. The security platform can also be configured to automatically block new sessions from accessing resources based on security policies.

[0048] In some embodiments, a system / process / computer program product for applying intelligent zero-trust security in a mobile network using a perimeter security platform (e.g., using the Radius and Diameter protocols) includes monitoring network traffic on the mobile network at the security platform to identify new sessions, wherein the security platform is located at the perimeter of the mobile network; determining metadata associated with the new session by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes one or more of the following: the Radius protocol and the Diameter protocol; and enforcing security policies on the new session at the security platform based on the metadata to apply context-based security in the mobile network. In this example embodiment, the security platform may be configured to process Radius and / or Diameter messages to extract metadata from the network traffic via one or more interfaces. The security platform may be located at one or more interfaces at the perimeter of the mobile network (e.g., one or more interfaces selected from SGi, N6, Gx, Gy, and Sd). Meta information may include User Equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Permanent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN, RAT type information, and / or any combination of the above. Similarly, the security platform can be configured with multiple security policies to apply vulnerability protection, intrusion prevention, antivirus, anti-spyware, DNS security, denial-of-service (DoS) protection, and / or cloud-based security. The security platform can also be configured to automatically block new sessions from accessing resources based on security policies.

[0049] For example, the disclosed techniques for applying zero-trust smart security in mobile networks using a perimeter security platform facilitate the provision of smart security (e.g., based on extracted subscriber IDs) in 5G mobile network environments using an N6 security platform at the perimeter.

[0050] As another example, the disclosed techniques for applying zero-trust smart security in mobile networks using a perimeter security platform facilitate the provision of smart security (e.g., based on extracted device IDs) in 4G / LTE mobile network environments using an SGi security platform at the perimeter.

[0051] As yet another example, the disclosed technology for applying zero-trust smart security in mobile networks using a perimeter security platform facilitates the identification and prevention of known and unknown threats at the 5G subscriber / user and / or 5G equipment / device level via the N6 interface in 5G mobile network environments and via the SGi interface in 4G / LTE mobile network environments.

[0052] As yet another example, the disclosed technology for applying zero-trust smart security in mobile networks using a perimeter security platform facilitates application security at the 5G subscriber / user and / or 5G equipment / device level in 5G mobile network environments via the N6 interface and in 4G / LTE mobile network environments via the SGi interface.

[0053] As a final example, the disclosed techniques for applying zero-trust smart security in mobile networks using a perimeter security platform facilitate URL filtering at the 5G subscriber / user and / or 5G equipment / device level via the N6 interface in 5G mobile network environments and via the SGi interface in 4G / LTE mobile network environments.

[0054] Furthermore, service providers and enterprises can leverage publicly available perimeter security platforms in mobile networks to apply zero-trust technologies within mobile networks, thereby enabling subscriber ID-based security at the perimeter of IP-based external networks (e.g., similar to the Internet).

[0055] Therefore, according to some embodiments, new and improved security solutions are disclosed that facilitate the application of zero-trust security (e.g., network-based security) in mobile networks (e.g., 4G / 5G / later mobile network versions) on various interfaces (e.g., SGi, N6, etc.) and protocols (e.g., PFCP, Radius, Diameter, etc.) and using perimeter security platforms (e.g., firewalls (FW) / next-generation firewalls (NGFW), network sensors acting on behalf of firewalls, or other (virtual) devices / components capable of implementing security policies using the disclosed technologies, including, for example, Palo Alto Networks' PA series next-generation firewalls, Palo Alto Networks' VM series virtualized next-generation firewalls and CN series container next-generation firewalls, and / or other commercially available virtual-based or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies) in mobile network environments.

[0056] The following will further describe these and other embodiments and examples of applying intelligent security for zero trust in mobile networks using perimeter security platforms.

[0057] An example system architecture for applying intelligent security for zero trust in mobile networks using a perimeter security platform.

[0058] Therefore, in some embodiments, the disclosed techniques for applying zero-trust smart security in mobile networks using a perimeter security platform (e.g., one or more security functions / platforms capable of using a firewall (FW) / next-generation firewall (NGFW), network sensors acting on behalf of the firewall, or another (virtual) device / component capable of implementing security policies using the disclosed techniques, such as PANOS implemented on a commercially available virtual / physical NGFW solution from Palo Alto Networks Ltd., or another security platform / NFGW (including, for example, Palo Alto Networks' PA series next-generation firewalls, Palo Alto Networks' VM series virtualized next-generation firewalls and CN series container next-generation firewalls, and / or other commercially available virtual-based or container-based firewalls that can be similarly implemented and configured to perform the disclosed techniques) are configured to be implemented through various interfaces (e.g., RESTful...). API, SGi, N6 and / or other interfaces in core 4G / LTE, 5G and later mobile networks) provide DPI capabilities (e.g., including stateful auditing) for user / subscriber sessions (e.g., user / subscriber traffic) to apply security to traffic in the mobile network based on policies (e.g., Layer 7 security and / or other security policy enforcement), as further described below.

[0059] Specifically, as will now be described with respect to various system embodiments, a security platform can be used in mobile networks (including 4G / LTE, 5G, and later mobile networks) to apply context-based security, as will be described below with respect to various embodiments. In example implementations, the security platform can be used in mobile networks to apply context-based security based on one or more of the following: subscriber / user, including IMSI, IMEI, RAT type, network slice, DNN / APN, location, user IP, and / or other contextual information. The security platform can be deployed on, for example, SGi and / or Sxb interfaces in 4G / LTE networks and N4 and / or N6 interfaces in 5G networks.

[0060] Using the PFCP protocol, we leverage the perimeter security platform to apply intelligent security for zero trust in mobile networks.

[0061] The following will describe various implementations of smart security for zero trust in mobile networks using the PFCP protocol and a perimeter security platform.

[0062] In an example implementation, using the PFCP protocol to apply smart security for zero trust in mobile networks with a perimeter security platform includes deploying the security platform in a 5G and / or 4G / LTE mobile network environment and monitoring PFCP messages at the security platform in a standalone 5G and / or 4G / LTE network (e.g., with a CUPS architecture). Specifically, the security platform is configured to process PFCP messages, including PFCP session establishment request / response messages and / or PFCP session modification request / response messages, to extract contextual information, which may include User Equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Permanent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN, and / or RAT type information. The security platform is also configured to apply security policies (e.g., enforce one or more security rules) based on the contextual information.

[0063] Figure 1A This is a block diagram of a first example service deployment architecture for applying zero-trust intelligent security to 5G and 4G mobile networks using the PFCP protocol and a perimeter security platform, according to some embodiments.

[0064] Specifically, Figure 1A This is a first example of a service deployment architecture for 5G and 4G mobile networks, which includes a security platform 102 (e.g., one or more security functions / platforms capable of using a firewall (FW) / next-generation firewall (NGFW), a network sensor acting on behalf of the firewall, or another (virtual) device / component capable of implementing security policies using the disclosed technologies, including, for example, Palo Alto Networks' PA series next-generation firewalls, Palo Alto Networks' VM series virtualized next-generation firewalls, and CN series container next-generation firewalls, and / or other commercially available virtual-based or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies), for applying context-based security in mobile networks (e.g., SGi and / or other interfaces in 4G / LTE networks, and N6 and / or other interfaces in 5G networks) through various interfaces in mobile networks (e.g., 4G / LTE or later mobile networks), as further described below.

[0065] As described in this article, IMSI is a concept referred to by the ITU-T as "International Mobile Subscription Identity". IMSI is a 14 or 15-digit number.

[0066] As mentioned in this article, the SUPI is a globally unique 5G "subscription permanent identifier" assigned to each subscriber in a 5G system. According to 3GPP TS 23.003 Release 16.9.0, the SUPI type can indicate IMSI, Network Access Identifier (NAI), Global Line Identifier (GLI), or Global Cable Identifier (GCI).

[0067] As mentioned in this article, the International Mobile Equipment Identity (IMEI) can be found at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx It is defined in 3GPP TS 23.003, which is available at specificationId=729.

[0068] like Figure 1A As shown, the 5G and 4G mobile network environments may also include 5G radio access network (RAN) access as shown at 106A, EUTRAN access as shown at 106B, and / or other networks such as Wi-Fi access and fixed access (not shown) to facilitate subscriber data communications (e.g., using user equipment (UE), such as smartphones, laptops, computers (which may be in a fixed location), and Internet of Things (IoT) devices and / or other cellular-enabled computing devices / equipment as shown at 104, and / or other network-enabled devices, including access to various applications, web services, content hosts, etc. and / or other networks via packet data network (PDN) (e.g., Internet) 120).

[0069] Also Figure 1A As shown, the UPF and PGW-U 112 communicate with the PDN (Internet) 120. Specifically, the security platform 102 is located at the perimeter of the 5G and 4G mobile network environment between the UPF and PGW-U 112 and the PDN (Internet) 120 via the N6 interface. The security platform 102 also communicates with the Session Management Function (SMF) and the Packet Gateway Control Plane (PGW-C) 113 (e.g., control plane communication with the security platform 102 via the N4 interface to access UE IP, IMEI, IMSI and / or other contextual information, as will be further described below).

[0070] refer to Figure 1AThe security platform 102 at the N6 and N4 interfaces monitors network traffic communications, wherein the security platform is located at the perimeter of the 5G and 4G mobile core networks. As shown, the security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of the 5G and 4G mobile networks. The security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in the mobile network (e.g., N4, N6 and / or other interfaces in the 5G mobile network, and SGi (not shown) and / or other interfaces in the 4G mobile network), as similarly described above and further described below.

[0071] In this example implementation, a security platform deployed at the perimeter of a mobile network based on 4G / LTE and 5G technologies can be used to execute the disclosed technologies for application at the security platform 102, such as... Figure 1A As shown in the diagram. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network (e.g., 4G / LTE or later mobile networks) through various interfaces (e.g., N4, N6 and / or other interfaces in 5G mobile networks, and SGi (not shown) and / or other interfaces in 4G mobile networks), as further described below.

[0072] In some embodiments, security platform 102 is also configured to provide the following DPI capability: DPI of PFCP traffic via the N6 interface. In an example implementation, the security platform is configured to provide, for example, DPI capability of PFCP messages (e.g., including identification UE IP, IMSI / SUPI, IMEI / PEI, S-NSSAI, APN / DNN and / or RAT type information, etc.) via the N6 and / or other interfaces between UPF and PGW-U 112 and PDN 120, to apply context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement), as further described below.

[0073] Specifically, in this example implementation, the security platform is configured to add entries for the UE IP and contextual information (such as IMSI, IMEI, S-NSSAI) associated with the subscriber / user to a data storage device (not shown) (e.g., a database, such as SQL or other commercially available databases). If, based on monitoring of the PFCP protocol via the N6 / SGi interface, any of the following events occur, the security platform removes the entries for the UE IP and associated contextual information from the database: (1) a PFCP session deletion request / response message for the PFCP control session is deleted; and (2) (one or more) user / subscriber session timeout messages (e.g., such timeouts can be configurable).

[0074] More specifically, in this example implementation, the security platform is configured to monitor PFCP messages, including the following: (1) PFCP session establishment procedures (e.g., according to 3GPP TS 29.244 v 18.3.0 (e.g., which is available at https: / / portal.3gpp.org / desktopmodules / Specifications / SpecificationDetails.aspx)). (1) The PFCP session establishment procedure (which is publicly available at specificationId=3111) shall be used to establish a PFCP session between the CP function and the UP function and to configure rules in the UP function so that the UP function can respond to incoming packets); (2) The PFCP session modification procedure (e.g., the PFCP session modification procedure shall be used to modify an existing PFCP session, such as configuring new rules, modifying existing rules, or deleting existing rules); and (3) The PFCP session deletion procedure (e.g., the PFCP session deletion procedure shall be used to delete an existing PFCP session between the CP function and the UP function) to facilitate the extraction of the contextual information described above.

[0075] Additionally, security platform 102 can also interface with cloud security service 122 (e.g., commercially available cloud-based security services such as WildFire). TM (WF) A cloud-based malware analysis environment, provided by Palo Alto Networks Ltd., is a commercially available cloud security service that includes automated security analysis of malware samples and analysis by security experts, or can utilize similar solutions from another vendor for network communication, such as via the Internet. For example, cloud security service 122 can be used to provide security platforms with dynamic anti-signatures against malware, DNS, URL, CNC malware, and / or other malware, and to receive malware samples for further security analysis.

[0076] Figure 1B This is a block diagram of a second example service deployment architecture for applying a 5G mobile network service deployment architecture for zero-trust intelligent security in 5G and 4G mobile networks using the PFCP protocol and a perimeter security platform, according to some embodiments.

[0077] Specifically, in this second example of a service deployment architecture for a 5G mobile network with security platform 102, security platform 102 is used at the N6 and N4 interfaces to monitor network traffic communications, wherein the security platform is located at the perimeter of the 5G mobile core network. As shown, security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of the 5G mobile network. Security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in the mobile network (e.g., N4, N6, and / or other interfaces in the 5G mobile network), as similarly described above and further described below.

[0078] In this example implementation, the disclosed technologies for applications at the security platform can be executed using a security platform deployed at the perimeter of a 5G-based mobile network, such as... Figure 1B As shown in the diagram. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network (e.g., via the N4 interface of UPF 112 and SMF 113, the N6 interface of UPF 112, and / or other interfaces in the 5G mobile network) through various interfaces in the mobile network (e.g., 5G or later mobile networks), as further described below.

[0079] In some embodiments, the security platform 102 is also configured to provide the following DPI capability: DPI of PFCP traffic via the N6 interface. In an example implementation, the security platform is configured to provide DPI capability (e.g., including PFCP messages such as identification UE IP, IMSI / SUPI, IMEI / PEI, S-NSSAI, APN / DNN and / or RAT type information, etc.) via the N6 interface and / or other interfaces between the UPF and PGW-U 112 and the PDN 120, to apply context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement), as further described below.

[0080] Figure 1CThis is a block diagram of a third example service deployment architecture for applying a 4G mobile network service deployment architecture for zero-trust intelligent security in a mobile network using the PFCP protocol and leveraging a perimeter security platform, according to some embodiments.

[0081] like Figure 1C As shown, the 4G mobile network environment may also include 4G radio access network (RAN) access as shown at 106C and / or other networks such as Wi-Fi access and fixed access (not shown) to facilitate subscriber data communications (e.g., using user equipment (UE), such as smartphones, laptops, computers (which may be in a fixed location), and Internet of Things (IoT) devices and / or other cellular-enabled computing devices / equipment as shown at 104, and / or other network-enabled devices, including access to various applications, web services, content hosts, etc., and / or other networks via packet data network (PDN) (e.g., Internet) 120).

[0082] Specifically, in this third example of a service deployment architecture for a 4G mobile network with a security platform 102, the security platform 102 at the SGi and Sxb interfaces monitors network traffic communications, wherein the security platform is located at the perimeter of the 4G mobile core network. As shown, the security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of the 4G mobile network. The security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in the mobile network (e.g., SGi, Sxb, and / or other interfaces in the 4G mobile network), as similarly described above and further described below.

[0083] In this example implementation, a security platform deployed at the perimeter of a 4G-based mobile network can be used to execute the disclosed technologies for application at security platform 102, such as... Figure 1C As shown in the illustration. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network (e.g., via the Sxb interface of PGW-C 113, via the SGi interface of PGW-U 112 and PDN 120, and / or other interfaces in the 4G mobile network) through various interfaces in the mobile network (e.g., 4G or later mobile networks), as further described below.

[0084] In some embodiments, security platform 102 is also configured to provide the following DPI capability: DPI of PFCP traffic via the N6 interface. In an example implementation, the security platform is configured to provide, for example, DPI capability of PFCP messages (e.g., including identification UE IP, IMSI / SUPI, IMEI / PEI, S-NSSAI, APN / DNN and / or RAT type information, etc.) via the N6 and / or other interfaces between UPF and PGW-U 112 and PDN 120, to apply context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement), as further described below.

[0085] Using the Radius protocol, we leverage the perimeter security platform to apply intelligent security for zero trust in mobile networks.

[0086] Various implementations of applying intelligent security for zero trust in mobile networks using the Radius protocol and a perimeter security platform will now be described below.

[0087] In an example implementation, using the Radius protocol, applying smart security for zero trust in mobile networks using a perimeter security platform includes deploying the security platform in 5G and / or 4G / LTE mobile network environments and monitoring Radius messages at the security platform in a separate 5G and / or 4G / LTE network. Specifically, the security platform is configured to process Radius messages including charging request (start) / charging response (start) and charging request (temporary update) / charging response (temporary update) messages to extract contextual information, which can include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Radius message include: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – APN). The security platform is also configured to apply security policies based on the contextual information (e.g., enforcing one or more security rules).

[0088] Example vendor-specific attributes (VSAs) include the following: (1) 3GPP-IMSI; (2) 3GPP-IMEISV; (3) 3GPP-RAT-Type; and (4) 3GPP-User-LocationInfo.

[0089] Specifically, in this example implementation, the security platform is configured to add entries for the UE IP and contextual information (such as IMSI, IMEI, and APN) associated with the subscriber / user to a data storage device (not shown) (e.g., a database, such as SQL or other commercially available databases). If, based on monitoring of the Radius protocol via the N6 / SGi interface, any of the following events occur, the security platform removes the entries for the UE IP and associated contextual information from the database: (1) observing / receiving a billing request (stop) / billing response (stop) message; and (2) observing / receiving one or more user / subscriber session timeout messages (e.g., such timeouts can be configurable).

[0090] Figure 2A This is a protocol diagram of the Radius billing message flow in a 5G network according to some embodiments.

[0091] According to 3GPP TS 29.561 Release 17.9.0 (e.g., publicly available at https: / / www.etsi.org / deliver / etsi_ts / 129500_129599 / 129561 / 17.09.00_60 / ts_129561v170900p.pdf), RADIUS charging should be used in accordance with IETF RFC 2866, IETF RFC 3162, and IETF RFC 4818. The RADIUS charging client functionality can reside in the SMF. The RADIUS charging client can send information to the DN-AAA server, which is identified during DNN provisioning. The DN-AAA server can store this information and use it to automatically identify users. This information is reliable because the 3GPP network has authenticated the subscriber (i.e., USIM card and possibly other authentication methods).

[0092] Figure 2B This is a protocol diagram of the Radius billing update message flow in a 5G network according to some embodiments.

[0093] Figure 2C This is a block diagram of a first example service deployment architecture for applying a zero-trust intelligent security 5G mobile network in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0094] Specifically, Figure 2CThis is a first example of a service deployment architecture for 5G and 4G mobile networks, which includes a security platform 102 (e.g., one or more security functions / platforms capable of using a firewall (FW) / next-generation firewall (NGFW), a network sensor acting on behalf of the firewall, or another (virtual) device / component capable of implementing security policies using the disclosed technologies, including, for example, Palo Alto Networks' PA series next-generation firewalls, Palo Alto Networks' VM series virtualized next-generation firewalls, and CN series container next-generation firewalls, and / or other commercially available virtual-based or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies), for applying context-based security in mobile networks (e.g., SGi and / or other interfaces in 4G / LTE networks, and N6 and / or other interfaces in 5G networks) through various interfaces in mobile networks (e.g., 4G / LTE or later mobile networks), as further described below.

[0095] like Figure 2C As shown, the 5G network environment may also include 5G radio access network (RAN) access as shown at 106A and / or other networks such as Wi-Fi access and fixed access (not shown) to facilitate subscriber data communications (e.g., using user equipment (UE), such as smartphones, laptops, computers (which may be in a fixed location), and Internet of Things (IoT) devices and / or other cellular-enabled computing devices / equipment as shown at 104, and / or other network-enabled devices, including access to various applications, web services, content hosts, etc., and / or other networks via packet data network (PDN) (e.g., Internet) 120).

[0096] Also Figure 2C As shown, UPF 112 communicates with DN-AAA (Radius server) 115 of a data network, which also includes an enterprise IT data center 118 and the Internet 120. Specifically, security platform 102 is located at the perimeter of the 5G mobile network environment between UPF 112 and DN-AAA (Radius server) 115 of the data network via an N6 interface (e.g., including Radius messages via the N6 interface). UPF 112 also communicates with SMF 113 (e.g., control plane communication with security platform 102 via an N4 interface to access UE IP, IMEI, IMSI, and / or other contextual information, as described further below).

[0097] refer to Figure 2CThe security platform 102 at the N6 and N4 interfaces monitors network traffic communications, with the security platform positioned at the perimeter of the 5G mobile core network. As shown, the security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of the 5G mobile network. The security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in the mobile network (e.g., N4, N6, and / or other interfaces in the 5G mobile network, and SGi (not shown) and / or other interfaces in the 4G mobile network).

[0098] In this example implementation, the disclosed technologies for applications at the security platform can be executed using a security platform deployed at the perimeter of a 5G-based mobile network, such as... Figure 2C As shown in the diagram. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network (e.g., 4G / LTE or later mobile networks) through various interfaces (e.g., N4, N6 and / or other interfaces in 5G mobile networks, and SGi (not shown) and / or other interfaces in 4G mobile networks), as further described below.

[0099] In some embodiments, the security platform 102 is also configured to provide DPI capabilities for Radius traffic via the N6 interface. In an example implementation, the security platform is configured to provide DPI capabilities for, for example, Radius messages (e.g., including identification UE IP, IMSI / SUPI, IMEI / PEI, S-NSSAI, APN / DNN, and / or RAT type information, etc.) via the N6 and / or interfaces between the UPF and DN-AAA (Radius server) 115 to apply context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement), as further described below.

[0100] Specifically, in this example implementation, the security platform is configured to monitor and process Radius messages, including charging request (start) / charging response (start) and charging request (temporary update) / charging response (temporary update) messages, to extract contextual information. This contextual information can include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Radius message include the following: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – the APN). The security platform is also configured to apply security policies based on the contextual information (e.g., enforcing one or more security rules).

[0101] More specifically, in this example implementation, the security platform is configured to add entries for the UE IP and contextual information (such as IMSI, IMEI, and APN) associated with the subscriber / user to a data storage device (not shown) (e.g., a database, such as SQL or other commercially available databases). If, based on monitoring of the Radius protocol via the N6 / SGi interface, any of the following events occur, the security platform removes the entries for the UE IP and associated contextual information from the database: (1) observing / receiving a billing request (stop) / billing response (stop) message; and (2) observing / receiving one or more user / subscriber session timeout messages (e.g., such timeouts can be configurable).

[0102] Additionally, security platform 102 can also interface with cloud security service 122 (e.g., commercially available cloud-based security services such as WildFire). TM (WF) A cloud-based malware analysis environment, provided by Palo Alto Networks Ltd., is a commercially available cloud security service that includes automated security analysis of malware samples and analysis by security experts, or can utilize similar solutions from another vendor for network communication, such as via the Internet. For example, cloud security service 122 can be used to provide security platforms with dynamic anti-signatures against malware, DNS, URL, CNC malware, and / or other malware, and to receive malware samples for further security analysis.

[0103] Figure 2D This is a block diagram of a second example service deployment architecture for applying a zero-trust intelligent security 5G mobile network in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0104] Specifically, in this second example of a service deployment architecture for a 5G mobile network with a security platform 102, the security platform 102 at the N6 interface is used to monitor network traffic communication, wherein the security platform is located on the perimeter of the 5G mobile core network, as similarly described above. Figure 2C As described herein, security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of a 5G mobile network. Security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in motion (e.g., N4, N6 and / or other interfaces in a 5G mobile network, and SGi (not shown) and / or other interfaces in a 4G mobile network).

[0105] In this example implementation, a security platform deployed at the perimeter of a 5G-based mobile network can be used to execute the disclosed technologies for applications at the security platform, such as... Figure 2D As shown in the illustration. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network (e.g., via the N6 interface of UPF112 and SMF 113 and / or other interfaces in the 5G mobile network) through various interfaces in the mobile network (e.g., 5G or later mobile networks), as further described below.

[0106] In some embodiments, security platform 102 is also configured to provide the following DPI capability: DPI of Radius traffic via the N6 interface. In an example implementation, the security platform is configured to provide DPI capability (e.g., including identifying, for example, UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Radius message, such as the UE IP, IMSI, IMEI, APN, RAT type, and / or user location information via the N6 interface and / or other interfaces between UPF 112 and the DN-AAA (Radius server) 115 of the data network) to apply context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement) as further described below).

[0107] Figure 2E This is a protocol diagram of the Radius message flow in a 4G / LTE network according to some embodiments.

[0108] According to 3GPP TS 29.061 Release 17.6.0 (e.g., publicly available at https: / / www.etsi.org / deliver / etsi_ts / 129000_129099 / 129061 / 17.06.00_60 / ts_129061v170600p.pdf), RADIUS charging should be used in accordance with IETF RFC 2866, IETF RFC 2869, IETF RFC 3162, and IETF RFC 4818. The RADIUS charging client functionality can reside in the GGSN / P-GW. The RADIUS charging client can send information to the charging server, which is identified during APN provisioning. The charging server can store this information and use it to automatically identify users. This information is reliable because the packet domain network has authenticated the subscriber (i.e., SIM card and possibly other authentication methods).

[0109] Figure 2F This is a protocol diagram of the Radius billing update message flow in a 4G / LTE network according to some embodiments.

[0110] Figure 2G This is a block diagram of a first example service deployment architecture for applying a zero-trust smart security 4G mobile network in a mobile network using the Radius protocol and a perimeter security platform, according to some embodiments.

[0111] Specifically, in this first example of a service deployment architecture for a 4G mobile network with a security platform 102, the security platform 102 at the SGi interface is used to monitor network traffic communications, wherein the security platform is located at the perimeter of the 4G mobile core network. As shown, the security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of the 4G mobile network. The security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in the mobile network (e.g., SGi, Sxb, and / or other interfaces in the 4G mobile network), as similarly described above and further described below.

[0112] In this example implementation, a security platform deployed at the perimeter of a 4G-based mobile network can be used to execute the disclosed technologies for application at the security platform, such as... Figure 2GAs shown in the illustration. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network via various interfaces in the mobile network (e.g., the SGi interface of the DN-AAA (Radius server) 115 of the data network via the P-GW112, and / or other interfaces in the 4G mobile network), as further described below.

[0113] In some embodiments, security platform 102 is also configured to provide the following DPI capability: DPI of Radius traffic via the SGi interface. In an example implementation, the security platform is configured to provide DPI capabilities (e.g., including identifying, for example, UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Radius message, such as the UE IP, IMSI, IMEI, APN, RAT type, and / or user location information via the SGi interface and / or other interfaces between P-GW 112 and DN-AAA (Radius server) 115 of the data network) to apply context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement) as further described below).

[0114] Using the Diameter protocol, a perimeter security platform is leveraged to apply intelligent security for zero-trust applications in mobile networks. Complete.

[0115] Various implementations of smart security for zero trust in mobile networks using the Diameter protocol and a perimeter security platform will now be described.

[0116] In an example implementation, using the Diameter protocol, applying smart security for zero trust in mobile networks using a perimeter security platform includes deploying the security platform in 5G and / or 4G / LTE mobile network environments, and monitoring Diameter messages at the security platform in standalone 5G and / or 4G / LTE networks. Specifically, the security platform is configured to process Diameter messages including charging request (start) / charging response (start) and charging request (provisional) / charging response (provisional) messages to extract contextual information, which can include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Diameter message include: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – APN). The security platform is also configured to apply security policies based on the contextual information (e.g., enforcing one or more security rules).

[0117] Specifically, in this example implementation, the security platform is deployed at the perimeter of a 5G and 4G / LTE network, a standalone 5G network, or a 4G / LTE network environment, and is configured to monitor Diameter messages.

[0118] More specifically, the security platform is configured to process Diameter messages, including charging request (start) / charging response (start) and charging request (provisional) / charging response (provisional) messages, to extract contextual information, including, for example, UE IP, IMSI, IMEI, APN, RAT type, and / or user location. Examples of attribute value pairs (AVPs) required in the Diameter message include the following: (1) Framed-IP-Address – the UE's IPv4 address; (2) Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and (3) called-station-id – APN. The security platform is also configured to apply security policies (e.g., enforce one or more security rules) based on the contextual information.

[0119] Example vendor-specific attributes (VSAs) include the following: (1) 3GPP-IMSI; (2) 3GPP-IMEISV; (3) 3GPP-RAT-Type; and (4) 3GPP-User-LocationInfo.

[0120] Specifically, in this example implementation, the security platform is configured to add entries for the UE IP and contextual information (such as IMSI, IMEI, and APN) associated with the subscriber / user to a data storage device (not shown) (e.g., a database, such as SQL or other commercially available databases). If, based on monitoring of the Radius protocol via the N6 / SGi interface, any of the following events occur, the security platform removes the entries for the UE IP and associated contextual information from the database: (1) observing / receiving a receive billing request (stop) / billing response (stop) message; and (2) observing / receiving one or more user / subscriber session timeout messages (e.g., such timeouts can be configurable).

[0121] Figure 3A This is a protocol diagram of the Diameter billing message flow in a 5G network according to some embodiments.

[0122] Figure 3B This is a protocol diagram of the Radius billing update message flow in a 5G network according to some embodiments.

[0123] Figure 3C This is a block diagram of a first example service deployment architecture for applying a perimeter security platform to a 5G mobile network with zero-trust intelligent security, based on some embodiments of the Diameter protocol.

[0124] Specifically, Figure 3C This is a first example of a service deployment architecture for a 5G mobile network, which includes a security platform 102 (e.g., one or more security functions / platforms capable of using a firewall (FW) / next-generation firewall (NGFW), a network sensor acting on behalf of the firewall, or another (virtual) device / component capable of implementing security policies using the disclosed technologies, including, for example, Palo Alto Networks' PA series next-generation firewalls, Palo Alto Networks' VM series virtualized next-generation firewalls, and CN series container next-generation firewalls, and / or other commercially available virtual-based or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies), for applying context-based security in the mobile network (e.g., 4G / LTE or later mobile networks) through various interfaces (e.g., SGi and / or other interfaces in 4G / LTE networks, and N6 and / or other interfaces in 5G networks), as further described below.

[0125] like Figure 3CAs shown, the 5G network environment may also include 5G radio access network (RAN) access as shown at 106A and / or other networks such as Wi-Fi access and fixed access (not shown) to facilitate subscriber data communications (e.g., using user equipment (UE), such as smartphones, laptops, computers (which may be in a fixed location), and Internet of Things (IoT) devices and / or other cellular-enabled computing devices / equipment as shown at 104, and / or other network-enabled devices, including access to various applications, web services, content hosts, etc., and / or other networks via packet data network (PDN) (e.g., Internet) 120).

[0126] Also Figure 3C As shown, UPF 112 communicates with DN-AAA (Radius Server) 115 of a data network, which also includes an enterprise IT data center 118 and the Internet 120. Specifically, security platform 102 is located at the perimeter of the 5G mobile network environment between UPF 112 and DN-AAA (Diameter Server) 115 of the data network via an N6 interface (e.g., including Diameter messages via the N6 interface). Security platform 102 also communicates with SMF 113 via an N6 interface (e.g., including Diameter messages via the N6 interface).

[0127] refer to Figure 3C The network traffic communication is monitored using a security platform 102 at the N6 interface, wherein the security platform is located at the perimeter of the 5G mobile core network. As shown, the security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communication at the perimeter of the 5G mobile network. The security platform 102 is configured to perform the disclosed techniques for applying context-based security through various interfaces in the mobile network (e.g., N6 and / or other interfaces in the 5G mobile network, and SGi (not shown) and / or other interfaces in the 4G mobile network), as similarly described above and further described below.

[0128] In this example implementation, the disclosed technologies for applications at the security platform can be executed using a security platform deployed at the perimeter of a 5G-based mobile network, such as... Figure 3CAs shown in the diagram. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network (e.g., 4G / LTE or later mobile networks) through various interfaces (e.g., N6 and / or other interfaces in 5G mobile networks, and SGi (not shown) and / or other interfaces in 4G mobile networks), as further described below.

[0129] In some embodiments, the security platform 102 is also configured to provide DPI capabilities for Diameter traffic via the N6 interface. In an example implementation, the security platform is configured to provide DPI capabilities for, for example, Diameter messages (e.g., including identification UE IP, IMSI, IMEI, APN, RAT type, and / or user location, etc.) via the N6 and / or other interfaces between the UPF / SMF and DN-AAA (Diameter server) 115, thereby applying context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement), as further described below.

[0130] Specifically, in this example implementation, the security platform is deployed at the perimeter of a 5G and 4G / LTE network, a standalone 5G network, or a 4G / LTE network environment, and is configured to monitor Diameter messages.

[0131] More specifically, in this example implementation, the security platform is configured to add entries for the UE IP and contextual information (such as IMSI, IMEI, and APN) associated with the subscriber / user to a data storage device (not shown) (e.g., a database, such as SQL or other commercially available databases). If, based on monitoring of the Radius protocol via the N6 / SGi interface, any of the following events occur, the security platform removes the entries for the UE IP and associated contextual information from the database: (1) observing / receiving a receive billing request (stop) / billing response (stop) message; and (2) observing / receiving (one or more) user / subscriber session timeout messages (e.g., such timeouts can be configurable).

[0132] Additionally, security platform 102 can also interface with cloud security service 122 (e.g., commercially available cloud-based security services such as WildFire). TM(WF) A cloud-based malware analysis environment, provided by Palo Alto Networks Ltd., is a commercially available cloud security service that includes automated security analysis of malware samples and analysis by security experts, or can utilize similar solutions from another vendor for network communication, such as via the Internet. For example, cloud security service 122 can be used to provide security platforms with dynamic anti-signatures against malware, DNS, URL, CNC malware, and / or other malware, and to receive malware samples for further security analysis.

[0133] Figure 3D This is a protocol diagram of the Diameter billing message flow on the SGi interface in a 4G / LTE network according to some embodiments.

[0134] According to 3GPP TS 29.061 Release 17.6.0 (available for example at https: / / www.etsi.org / deliver / etsi_ts / 129000_129099 / 129061 / 17.06.00_60 / ts_129061v170600p.pdf), Diameter billing should be used in accordance with RFC 7155. The Diameter billing client functionality can reside in the P-GW. The Diameter billing client can send information to the billing server, which is identified during APN provisioning. The billing server can store this information and use it to automatically identify users. This information can be trusted because the PS access network has authenticated the subscriber (i.e., SIM card and possibly other authentication methods).

[0135] Figure 3E This is a protocol diagram of the Diameter billing update message flow in a 4G / LTE network according to some embodiments.

[0136] Figure 3F This is a block diagram of a first example service deployment architecture for applying a perimeter security platform to a 4G mobile network with zero-trust intelligent security, based on some embodiments of the Diameter protocol.

[0137] Specifically, in this first example of a service deployment architecture for a 4G mobile network with a security platform 102, the security platform 102 at the SGi interface is used to monitor network traffic communications, wherein the security platform is located at the perimeter of the 4G mobile core network. As shown, the security platform 102 (e.g., a (virtual) device / apparatus, each including a firewall (FW), a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies using the disclosed techniques) monitors / filters network traffic communications at the perimeter of the 4G mobile network. The security platform 102 is configured to perform the disclosed techniques for use through various interfaces in the mobile network (e.g., SGi, such as...) Figure 3F As shown above), Gx, Gy, and / or Sd (e.g., the Gx, Gy, and / or Sd interfaces can be used by various deep packet inspection (DPI) solutions for a variety of use cases, including non-security use cases such as Quality of Service (QoS), bandwidth management and / or subscriber association and management, and / or other interfaces in 4G mobile networks), as similarly described above and as further described below.

[0138] In this example implementation, the disclosed technologies for application at the security platform can be executed using a security platform deployed at the perimeter of a 4G-based mobile network, such as... Figure 3F As shown in the illustration. Specifically, the security platform 102 can be configured to apply context-based security in a mobile network via various interfaces in the mobile network (e.g., the SGi interface of the Diameter server 115 via the P-GW112 and the data network, and / or other interfaces in the 4G mobile network), as further described below.

[0139] In some embodiments, the security platform 102 is also configured to provide the following DPI capability: DPI of Diameter traffic via the SGi interface. In an example implementation, the security platform is configured to provide DPI capabilities (e.g., including identifying UE IP, IMSI, IMEI, APN, RAT type, and / or user location of Diameter messages via the SGi and / or other interfaces between the P-GW 112 and the Diameter server 115, thereby applying context-based security traffic based on policies (e.g., Layer 7 security and / or other security policy enforcement)), as further described below.

[0140] Therefore, service providers and / or enterprises can use the disclosed technologies and security platforms to apply intelligent security for zero trust in mobile networks using perimeter security platforms.

[0141] The following sections will describe various example use cases of applying smart security for zero trust in mobile networks using the perimeter security platform.

[0142] Example use cases of applying intelligent security for zero trust in mobile networks using a perimeter security platform.

[0143] The disclosed security platform, which uses security policy enforcement, provides enhanced security technologies for mobile / service provider networks, including the application of context-based security using various protocols and interfaces (e.g., and data storage devices). It can be applied to various additional example use case scenarios to promote enhanced security of mobile networks (e.g., 4G / 5G / 6G and beyond), as will now be described with respect to various example use cases.

[0144] As a first example use case, a security platform or similar device is configured to apply user and / or device identity-based security in an enterprise 5G network environment.

[0145] As a second example use case, a security platform or similar device is configured to apply advanced L7 security controls to critical infrastructure devices connected to a 5G network environment.

[0146] As a third example use case, mobile network service providers use the technologies disclosed by the security platform to provide advanced threat prevention services to 5G customers in the manufacturing vertical.

[0147] Example physical and logical implementations of embodiments of the security platform will now be described further below.

[0148] Example hardware components for applying intelligent security for zero trust in mobile networks using a perimeter security platform.

[0149] Figure 4AThis is a functional diagram of the hardware components of a network device for applying zero-trust smart security in a mobile network using a perimeter security platform, according to some embodiments. The examples shown represent physical / hardware components that can be included in network device 450 (e.g., a device, gateway, or server capable of implementing the security platform disclosed herein). Specifically, network device 450 includes a high-performance multi-core CPU 452 and RAM 454. Network device 450 also includes a storage device 460 (e.g., one or more hard disks or solid-state storage units) capable of storing policies and other configuration information, as well as signatures. In one embodiment, storage device 460 stores information (e.g., UE IP, IMSI, IMEI, APN, RAT type, and / or user location information, and / or other protocol-related / extracted message parameters, such as those described herein with respect to various embodiments) extracted from monitored traffic through various interfaces (e.g., SGi, N4, N6, and / or other interfaces) monitored to implement disclosed security policy enforcement techniques for applying context-based security through these interfaces, including disclosed techniques for applying zero-trust smart security in mobile networks using perimeter security platforms as described herein. Network device 450 may also include one or more optional hardware accelerators. For example, network device 450 may include a cryptographic engine 456 configured to perform encryption and decryption operations, and one or more FPGAs 458 configured to perform signature matching, act as a network processor, and / or perform other tasks.

[0150] Example logic components for applying intelligent security for zero trust in mobile networks using a perimeter security platform.

[0151] Figure 4B This is a functional diagram of the logical components of a network device for applying zero-trust smart security in a mobile network using a perimeter security platform, according to some embodiments. The illustrated example represents a logical component that can be included in network device 400 (e.g., a data device capable of implementing the disclosed security platform and performing the disclosed techniques for applying zero-trust smart security in a mobile network using the perimeter security platform, and / or applying other context-based security through various interfaces in the mobile network). As shown, network device 400 includes a management plane 402 and a data plane 404. In one embodiment, the management plane is responsible for managing user interactions, such as by providing a user interface for configuring policies and viewing log data. The data plane is responsible for managing data, such as by performing packet processing and session responses.

[0152] Suppose a mobile device attempts to access a resource (e.g., a remote website / server, MEC service, IoT device, or other resource) using an encrypted session protocol (such as SSL). Network processor 406 is configured to monitor packets from the mobile device and provide the packets to data plane 404 for processing. Flow 408 identifies the packets as part of a new session and creates a new session flow. Based on flow lookup, subsequent packets are identified as belonging to that session. If applicable, SSL decryption is applied by SSL decryption engine 410 using various techniques described herein. Otherwise, processing by SSL decryption engine 410 is omitted. Application ID (APP ID) module 412 is configured to determine what type of traffic the session involves (e.g., PFCP, Radius, and / or Diameter traffic) and / or various monitored interfaces (such as SGi, N4, N6, and / or other interfaces, as described above relative to...). Figure 1A-3F(Similarly described above) other network protocols between traffic flows, and identify the context associated with the traffic flow (e.g., identifying UE IP, IMSI, IMEI, APN, RAT type and / or user location information, and / or other protocol-related / extracted message parameters as described herein). For example, APP ID 412 can identify GET requests in received data and determine that the session requires PFCP, Diameter, or Radius decoder 414. For each type of protocol, there is a corresponding decoder 414. In one embodiment, the application identifier is performed by the application identifier module (e.g., the APP ID component / engine), and the user identifier is performed by another component / engine. Based on the determination made by APP ID 412, packets are sent to the appropriate decoder 414. Decoder 414 is configured to assemble packets (e.g., which may be received out of order) into the correct order, perform tokenization, and extract information (e.g., to extract various information exchanged in PFCP, Radius, and / or Diameter traffic through various interfaces, as similarly described above and further described below). Decoder 414 also performs signature matching to determine what should occur on the packet. SSL encryption engine 416 performs SSL encryption using various techniques as described herein, and then forwards the packet using forwarding component 418 as shown. Also as shown, policy 420 is received and stored in management plane 402. In one embodiment, policy enforcement is applied based on monitored, decrypted, identified, and decoded session traffic flows, as described herein with respect to various embodiments (e.g., a policy can include one or more rules that can be specified using domain names and / or host / server names, and the rules can apply one or more signatures or other matching criteria or heuristics, such as parameters / information extracted from the DPI of monitored PFCP, Radius, and / or Diameter traffic and / or monitored PFCP, Radius, and / or Diameter and / or (one or more) other protocol traffic, for security policy enforcement of subscriber / IP flows on the service provider network, such as SGi / N4 / N6 / other interfaces, as described above with respect to various embodiments). Figure 1A-3F (Similarly described).

[0153] As also shown in Figure 4, an interface (I / F) communicator 422 is provided for security platform manager / management communications. In some cases, network device 400 is used to monitor network communications of other network elements on a service provider network, and data plane 404 supports decoding of such communications (e.g., network device 400, including I / F communicator 422 and decoder 414, can be configured to monitor and / or communicate on, for example, reference point interfaces (such as SGi, N4, N6, and / or other interfaces where wired and wireless network traffic flows). Therefore, network device 400 including I / F communicator 422 can be used to implement the disclosed techniques for applying intelligent security for zero trust in mobile networks by leveraging perimeter security platforms in mobile networks, as described above and as will be further described below.

[0154] Additional example procedures will now be described for applying disclosed techniques for zero-trust smart security in mobile networks using a perimeter security platform.

[0155] An example process for applying intelligent security for zero trust in mobile networks using a perimeter security platform.

[0156] Figure 5 This is a flowchart illustrating the process of applying intelligent security for zero trust in a mobile network using the PFCP protocol, according to some embodiments. In some embodiments, such as Figure 5 The process 500 shown is comprised of the components included above relative to... Figure 1A-1C The described embodiments are performed using security platforms and technologies similar to those described above. In one embodiment, process 500 is performed by, as described above, relative to... Figure 4A The data device 450 described above, as relative to... Figure 4B The network device 400 described herein, virtual devices (e.g., Palo Alto Networks' VM series virtualized next-generation firewall, CN series container next-generation firewall, and / or other commercially available virtual or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies), SDN security solutions, cloud security services, and / or combinations or hybrid implementations as described herein.

[0157] At position 502, the security platform monitors network traffic on the mobile network to identify new sessions. For example, the security platform (e.g., a firewall, a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies) is deployed at the perimeter of the mobile network (e.g., 4G and / or 5G or later mobile networks), and in some cases, the security platform is able to monitor various protocols on the mobile network, such as the PFCP protocol (e.g., via SGi, Sxb, N4, N6, and / or other interfaces) and / or other protocols, as described above relative to... Figure 1A-1C Described similarly.

[0158] At 504, the execution involves extracting metadata from the PFCP traffic at the security platform via one or more interfaces to determine the metadata associated with the new session. For example, the security platform can be configured to process PFCP messages including PFCP session establishment request / response messages and / or PFCP session modification request / response messages to extract contextual information, which may include User Equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Permanent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN, and / or RAT type information, as described above relative to... Figure 1A-1C Described similarly.

[0159] At point 506, metadata-based enforcement of security policies is performed on the new session at the security platform to apply context-based security in the mobile network. For example, security policy enforcement can include allowing or blocking the session based on the policy, or performing another action, such as those described similarly above.

[0160] Figure 6 This is another flowchart illustrating the process of applying intelligent security for zero trust in mobile networks using a perimeter security platform based on the Radius protocol, according to some embodiments. In some embodiments, such as Figure 6 The process 600 shown is comprised of the components included above relative to... Figure 2A-2G The described embodiments are performed using security platforms and technologies similar to those described above. In one embodiment, process 600 is performed by the security platform and technologies described above relative to... Figure 4A The described data device 450, on the above relative to Figure 4B The network device 400 described herein, virtual devices (e.g., Palo Alto Networks' VM series virtualized next-generation firewall, CN series container next-generation firewall, and / or other commercially available virtual or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies), SDN security solutions, cloud security services, and / or combinations or hybrid implementations as described herein.

[0161] At 602, the security platform monitors network traffic on the mobile network to identify new sessions. For example, the security platform (e.g., a firewall, a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies) is deployed at the perimeter of the mobile network (e.g., 4G and / or 5G or later mobile networks), and in some cases, the security platform is able to monitor various protocols on the mobile network, such as the Radius protocol (e.g., via SGi, N6, Gx, Gy, Sd and / or other interfaces) and / or other protocols, such as those mentioned above relative to... Figure 2A-2G Described similarly.

[0162] At 604, the execution involves extracting metadata from the Radius traffic at the security platform via one or more interfaces to determine the metadata associated with the new session. For example, the security platform can be configured to process Radius messages including charging request (start) / charging response (start) and charging request (temporary update) / charging response (temporary update) messages to extract contextual information, which can include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Radius message include: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – the APN), as described above relative to... Figure 2A-2G Described similarly.

[0163] At point 606, metadata-based enforcement of security policies is performed on the new session at the security platform to apply context-based security in the mobile network. For example, security policy enforcement can include allowing or blocking the session or performing another action based on the policy, as described similarly above.

[0164] Figure 7 This is another flowchart illustrating the process of applying intelligent security for zero trust in mobile networks using a perimeter security platform, based on some embodiments of the Diameter protocol. In some embodiments, such as Figure 7 The process 700 shown is comprised of the components included above relative to... Figures 3A-3F The described embodiments are performed using security platforms and technologies similar to those described above. In one embodiment, process 700 is performed by the security platform and technologies described above relative to... Figure 4A The described data device 450, on the above relative to Figure 4BThe network device 400 described herein, virtual devices (e.g., Palo Alto Networks' VM series virtualized next-generation firewall, CN series container next-generation firewall, and / or other commercially available virtual or container-based firewalls that can be similarly implemented and configured to perform the disclosed technologies), SDN security solutions, cloud security services, and / or combinations or hybrid implementations as described herein.

[0165] At 702, the security platform monitors network traffic on the mobile network to identify new sessions. For example, the security platform (e.g., a firewall, a network sensor acting on behalf of the firewall, or another device / component capable of implementing security policies) is deployed at the perimeter of the mobile network (e.g., 4G and / or 5G or later mobile networks), and in some cases, the security platform is able to monitor various protocols on the mobile network, such as the Diameter protocol (e.g., via SGi, N6, Gx, Gy, Sd and / or other interfaces) and / or other protocols, such as those mentioned above relative to... Figures 3A-3F Described similarly.

[0166] At 704, the execution involves extracting metadata from Diameter traffic at the security platform via one or more interfaces to determine the metadata associated with the new session. For example, the security platform can be configured to process Diameter messages including charging request (start) / charging response (start) and charging request (temporary) / charging response (temporary) messages to extract contextual information, which can include UE IP, IMSI, IMEI, APN, RAT type, and / or user location information (e.g., examples of attribute value pairs (AVPs) requested in the Diameter message include: Framed-IP-Address – the UE's IPv4 address; Framed-IPv6-Prefix – the IPv6 prefix assigned to the UE; and called-station-id – the APN), as described above relative to... Figures 3A-3F Described similarly.

[0167] At point 706, metadata-based enforcement of security policies is performed on new sessions at the security platform to apply context-based security in mobile networks. For example, security policy enforcement can include allowing or blocking sessions or performing another action based on the policy, as described similarly above.

[0168] Although the foregoing embodiments have been described in considerable detail for clarity of understanding, the invention is not limited to the details provided. Many alternative ways of implementing the invention exist. The disclosed embodiments are illustrative and not restrictive.

Claims

1. A system comprising: The processor is configured to: Monitoring network traffic on a mobile network at a secure platform to identify new sessions, wherein the secure platform is located at the perimeter of the mobile network; The metadata associated with the new session is determined by extracting metadata from network traffic via one or more interfaces, wherein the network traffic includes Packet Forwarding Control Protocol (PFCP). as well as Based on the metadata, a security policy is enforced on the new session at the security platform to apply context-based security in the mobile network; as well as A memory that is coupled to the processor and configured to provide instructions to the processor.

2. The system of claim 1, wherein the security platform is configured to process PFCP messages to extract the metadata from the network traffic via the one or more interfaces.

3. The system of claim 1, wherein the security platform is located at one or more interfaces at the perimeter of the mobile network.

4. The system of claim 1, wherein the security platform is located at one or more interfaces at the perimeter of the mobile network, the one or more interfaces being selected from one or more of the following interfaces: SGi, Sxb, N4, and N6.

5. The system according to claim 1, wherein the metadata includes user equipment (UE) IP information.

6. The system according to claim 1, wherein the metadata includes International Mobile Subscription Identity (IMSI) information.

7. The system of claim 1, wherein the metadata includes subscription persistent identifier (SUPI) information.

8. The system according to claim 1, wherein the metadata includes IMEI / PEI information.

9. The system according to claim 1, wherein the metadata includes S-NSSAI information.

10. The system according to claim 1, wherein the metadata includes APN / DNN information.

11. The system according to claim 1, wherein the metadata includes RAT type information.

12. The system according to claim 1, wherein the metadata includes user location information.

13. The system of claim 1, wherein the metadata includes User Equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Permanent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN and / or RAT type information.

14. The system of claim 1, wherein the security platform is configured with multiple security policies to apply vulnerability protection, intrusion prevention, antivirus, anti-spyware, DNS security, denial-of-service (DoS) protection and / or cloud-based security.

15. The system of claim 1, wherein the processor is further configured to: Based on the security policy, the new session's access to resources is blocked.

16. A method comprising: Network traffic on a mobile network is monitored at a secure platform to identify new sessions, wherein the secure platform is located at the perimeter of the mobile network; The metadata associated with the new session is determined by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes Packet Forwarding Control Protocol (PFCP). as well as Based on the metadata, a security policy is enforced on the new session at the security platform to apply context-based security in the mobile network.

17. The method of claim 16, wherein the security platform is configured to process PFCP messages to extract the metadata from the network traffic via the one or more interfaces.

18. The method of claim 16, wherein the security platform is located at one or more interfaces at the perimeter of the mobile network.

19. A computer program product embodied in a non-transitory computer-readable storage medium and comprising computer instructions for: Monitoring network traffic on a mobile network at a secure platform to identify new sessions, wherein the secure platform is located at the perimeter of the mobile network; The metadata associated with the new session is determined by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes Packet Forwarding Control Protocol (PFCP); and Based on the metadata, a security policy is enforced on the new session at the security platform to apply context-based security in the mobile network.

20. The computer program product of claim 19, wherein the security platform is configured to process PFCP messages to extract the metadata from the network traffic via the one or more interfaces.

21. A system comprising: The processor is configured to: Monitoring network traffic on a mobile network at a secure platform to identify new sessions, wherein the secure platform is located at the perimeter of the mobile network; The metadata associated with the new session is determined by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes one or more of the following: Radius protocol and Diameter protocol; as well as Based on the metadata, a security policy is enforced on the new session at the security platform to apply context-based security in the mobile network; as well as A memory that is coupled to the processor and configured to provide instructions to the processor.

22. The system of claim 21, wherein the security platform is configured to process Radius and / or Diameter messages to extract the metadata from the network traffic via the one or more interfaces.

23. The system of claim 21, wherein the security platform is located at one or more interfaces at the perimeter of the mobile network.

24. The system of claim 21, wherein the security platform is located at one or more interfaces at the perimeter of the mobile network, the one or more interfaces being selected from one or more of the following interfaces: SGi, N6, Gx, Gy, and Sd.

25. The system of claim 1, wherein the metadata includes user equipment (UE) IP information.

26. The system of claim 21, wherein the metadata includes International Mobile Subscription Identity (IMSI) information.

27. The system of claim 21, wherein the metadata includes subscription permanent identifier (SUPI) information.

28. The system of claim 21, wherein the metadata includes IMEI / PEI information.

29. The system of claim 21, wherein the metadata includes S-NSSAI information.

30. The system of claim 21, wherein the metadata includes APN / DNN information.

31. The system of claim 21, wherein the metadata includes RAT type information.

32. The system according to claim 21, wherein the metadata includes user location information.

33. The system of claim 21, wherein the metadata includes User Equipment (UE) IP, International Mobile Subscription Identity (IMSI) / Subscription Permanent Identifier (SUPI), IMEI / PEI, S-NSSAI, APN / DNN and / or RAT type information.

34. The system of claim 21, wherein the security platform is configured with multiple security policies to apply vulnerability protection, intrusion prevention, antivirus, anti-spyware, DNS security, denial-of-service (DoS) protection and / or cloud-based security.

35. The system of claim 21, wherein the processor is further configured to: Based on the security policy, the new session's access to resources is blocked.

36. A method comprising: Monitoring network traffic on a mobile network at a secure platform to identify new sessions, wherein the secure platform is located at the perimeter of the mobile network; The metadata associated with the new session is determined by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes one or more of the following: Radius protocol and Diameter protocol; as well as Based on the metadata, a security policy is enforced on the new session at the security platform to apply context-based security in the mobile network.

37. The method of claim 36, wherein the security platform is configured to process Radius and / or Diameter messages to extract the metadata from the network traffic via the one or more interfaces.

38. The method of claim 36, wherein the security platform is located at one or more interfaces at the perimeter of the mobile network.

39. A computer program product embodied in a non-transitory computer-readable storage medium and comprising computer instructions for: Monitoring network traffic on a mobile network at a secure platform to identify new sessions, wherein the secure platform is located at the perimeter of the mobile network; Meta-information associated with the new session is determined by extracting metadata from the network traffic via one or more interfaces, wherein the network traffic includes one or more of the following: Radius protocol and Diameter protocol; and based on the metadata, a security policy is enforced on the new session at the security platform to apply context-based security in the mobile network.

40. The computer program product of claim 39, wherein the security platform is configured to process Radius and / or Diameter messages to extract the metadata from the network traffic via the one or more interfaces.