Cloud-based 5G security network architectures
A Multi-Access Edge Compute (MEC) system includes a plurality of compute resources including one or more processors configured to implement services; wherein the services include any of edge services, routing functions, and hosted services; and wherein the services further include cloud-based security services implemented in the MEC in conjunction with a cloud-based security system that includes a plurality of nodes and offers multi-tenant cloud-based security services, and wherein the cloud-based security services implemented in the MEC are for subscribers of a service provider associated with the MEC.
1. A Multi-Access Edge Compute (MEC) system comprising:
a plurality of compute resources comprising one or more processors configured to implement services;
wherein the services include any of edge services, routing functions, and hosted services;
wherein the services further include cloud-based security services implemented in the MEC in conjunction with a cloud-based security system, and wherein the cloud-based security services implemented in the MEC are for subscribers of a service provider associated with the MEC; and
wherein the cloud-based security system includes a plurality of nodes including a private node in the hosted services for the subscribers, wherein the subscribers are routed directly through the private node via the routing functions, and wherein the cloud-based security system supports a plurality of tenants in addition to the service provider and the subscribers, via one or more additional nodes of the plurality of nodes, such that the private node and the one or more additional nodes operate together to provide multi-tenant cloud-base security services.
2. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the private node for the subscribers is dedicated to the service provider as a single tenant, and wherein the one or more additional nodes support multiple tenants.
3. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the edge services include a cloud connector that is a gateway between the MEC and the cloud-based system.
4. The Multi-Access Edge Compute (MEC) system of claim 3 , wherein the cloud connector is configured to forward traffic for the subscribers to a dedicated node in the cloud-based system for the MEC.
5. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the routing functions include a node of the cloud-based system included therein, for inline monitoring of the subscribers.
6. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the cloud-based security services are implemented according to a policy associated with the service provider.
7. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the cloud-based security services are implemented according to a policy associated with the service provider or a policy associated with a tenant of a user.
8. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the cloud-based security services include Internet Access and/or private application access.
9. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the cloud-based security services include monitoring of Secure Sockets Layer (SSL) traffic.
10. The Multi-Access Edge Compute (MEC) system of claim 1 , wherein the cloud-based security services obtaining policies and rules from a central authority in the cloud-based system.
11. A method implemented in a Multi-Access Edge Compute (MEC) system comprising:
operating a plurality of compute resources comprising one or more processors configured to implement services, wherein the services include any of edge services, routing functions, and hosted services; and
operating cloud-based security services implemented in the MEC in conjunction with a cloud-based security system, and wherein the cloud-based security services implemented in the MEC are for subscribers of a service provider associated with the MEC,
wherein the cloud-based security system includes a plurality of nodes including a private nodes in the hosted services for the subscribers, wherein the subscribers are routed directly through the private node via the routing functions, and wherein the cloud-based security system supports a plurality of tenants in addition to the service provider and the subscribers, via one or more additional nodes of the plurality of nodes, such that the private node and the one or more additional nodes operate together to provide multi-tenant cloud-based security services.
12. The method of claim 11 , wherein the private node for the subscribers is dedicated to the service provider as a single tenant, and wherein the one or more additional nodes support multiple tenants.
13. The method of claim 11 , wherein the edge services include a cloud connector that is a gateway between the MEC and the cloud-based system.
14. The method of claim 13 , wherein the cloud connector is configured to forward traffic for the subscribers to a dedicated node in the cloud-based system for the MEC.
15. The method of claim 11 , wherein the routing functions include a node of the cloud-based system included therein, for inline monitoring of the subscribers.
16. The method of claim 11 , wherein the cloud-based security services are implemented according to a policy associated with the service provider.
17. The method of claim 11 , wherein the cloud-based security services are implemented according to a policy associated with the service provider or a policy associated with a tenant of a user.
18. The method of claim 11 , wherein the cloud-based security services include Internet Access and/or private application access.
19. The method of claim 11 , wherein the cloud-based security services include monitoring of Secure Sockets Layer (SSL) traffic.
20. The method of claim 11 , wherein the cloud-based security services obtaining policies and rules from a central authority in the cloud-based system.