Skip to main content

From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking


From MPLS to SD-WAN to SASE: An Evolution of Enterprise Networking


The way we do business is changing. As critical business applications migrate to the cloud, and the mobile workforce continues to grow, networking and security solutions need to evolve in order to meet the changing business needs. Gartner believes (and we agree) that the future of networking lies with SASE (Secure Access Service Edge) – the convergence of networking and security into one cloud service. Here’s why.

1990s – 2000s: MPLS and the Era of Clear Network Boundaries?

Back in the day, networking models were hardware-centric and manually configured. Applications, data, and services lived within private datacenters and relied on remote access solutions to connect remote workers. Dedicated network connectivity, known as MPLS, was the preferred approach for connecting remote locations.
MPLS provides predictable performance, low latency and packet loss, and central management. However, MPLS is expensive, capacity constrained, and provisioning of new links takes a long time. Alongside MPLS, Internet links co-existed as a lower quality and inexpensive alternative, which didn’t come with the performance and uptime guarantees of dedicated connectivity. Many organizations ended up integrating both into their networking environments in an active (MPLS), and passive backup (Internet).
Regardless, the WAN became complex, costly and the epitome of lack of agility. Operational costs grew as administrators had to manually configure and deploy routers and appliances needed in the branch offices: WAN optimizers for overcoming bandwidth limitations, stacks of security appliances for defending the Internet perimeter, packet capture and analysis appliances for visibility and more. Maintaining such a setup was becoming increasingly difficult.

2000s – 2010s: Moving to Software-Defined WAN

Next came the attempt to fill the gaps created by the limitations of MPLS and the public Internet with SD-WAN. SD-WAN automates the use of multiple links (MPLS, xDSL, Fiber, Cable, and 4G) to increase overall network capacity, improve agility to speed up site provisioning, automatically adjust to changing network conditions, and reduce overall cost per megabit.
SD-WAN offers a cost-efficient and flexible alternative to MPLS, but SD-WAN alone can’t provide a complete WAN transformation. It fails to deliver the security, cloud readiness and mobility required to support the digital business. As a result, IT teams find themselves dealing with technological silos, built upon point products that are loosely integrated and separately managed.

Today: Network and Security Delivered from the Cloud (SASE)

In the digital age we all live in, enterprise networks must extend to the cloud, remote locations, and mobile users. This is easier said than done. IT traditionally responds to new business needs with point products. For example, SD-WAN is used to address the high cost and capacity constraints of MPLS; cloud acceleration and security appliances are deployed to support cloud migration; branch security and WAN optimization are needed for distributed locations; and VPN enables remote users to access business applications.
This type of network architecture, built on a pile of point products and appliances, increases complexity and cost for IT, and is hard pressed to support the needs of the digital business for optimization, security and efficiency. As Gartner notes, “In essence, complexity is the enemy of availability, security and agility” *. There must be a simpler way. There is, and it’s called SASE.
SASE is a new infrastructure category introduced by Gartner in 2019. It converges multiple point solutions such as SD-WAN, Next-gen firewalls, secure web gateway, Software defined perimeter (SDP), and more into a unified, global cloud-native service. SASE enables IT to provide a holistic, agile and adaptable service to the digital business.
According to Gartner, “Digital transformation and adoption of mobile, cloud and edge deployment models fundamentally change network traffic patterns, rendering existing network and security models obsolete.” **
This is why Gartner considers SASE to be transformational, providing enterprises with an agile, scalable and elastic platform to support their digital business needs today, and into the future.

Comments

Popular posts from this blog

Checkpoint firewall common commands part 2

Checkpoint firewall common commands part 2 For basic firewall informaton gathering: fgate stat -Status and statistics of Flood-Gate-1. fwaccel <stat|stats|conns>  – View status, statistics or connection table of SecureXL. fw getifs -Show list of configured interfaces with IP and netmask. cpstat <app_flag> [-f flavour] -View OS, HW and CP application status. Issue cpstat without any options to see all possible application flags <app_flag> and corresponding flavours. Examples: cpstat fw -f policy – verbose policy info cpstat os -f cpu – CPU utilization statistics cpinfo -y all   -List all installed patches and hotfixes. cpd_sched_config print -Show task scheduled with CPD scheduler. enabled_blades -View enabled software blades avsu_client [-app <app>]   , get_version <app>  -Get signature version and status of content security .Without the -app option “Anti Virus” is used. show configuration -Show

Unable to Connect to Server Checkpoint R80

Unable to Connect to Server Checkpoint R80 Unable to Connect to Server A connection to the management server will fail if: A firewall between SmartConsole and the management server blocks Port 19009 -  port 19009 is used for a new R80 service. Allow traffic on this port for all clients and management servers. No GUI clients are assigned -  Open the Gaia Portal. If the First Time Configuration Wizard opens, complete it. If the First Time Configuration Wizard has already run, open  User Management > GUI Clients  and add a client. When using Multi-Domain Security Management, connect SmartConsole to the Multi-Domain Server and make sure the domains have GUI clients assigned to them. The required processes are not reachable -  Make sure the computer with SmartConsole installed can reach the IP address of the management server, and that these server processes are up and running: cpm fwm Operation time out  – Your connection to the management (cloud demo

Configuring Proxy ARP for Manual NAT

Configuring Proxy ARP for Manual NAT Symptoms After creating a Manual Static NAT rule, Security Gateway does not answer the ARP Requests for the Static NATed IP address that was configured in the Manual NAT rule. Security Gateway replies to ARP requests with a wrong MAC address, mostly for the NAT traffic.  Introduction Let us consider the following scenario: Two networks ( Network_A  and  Network_B ) are separated by a Security Gateway (single Security Gateway or ClusterXL). On each network, there is a host ( Host_A  on  Network_A ,  Host_B  on  Network_B ). Let us assume, that  Network_A  represents the  Internal  network, and  Network_B  represents the  External  network. According to the existing standards, when  Host_B  needs to send data to  Host_A , an ARP Request for the MAC address of  Host_A  will be sent by  Host_B  to  Network_B . Since  Host_A  is located on another network, and the Security Gateway acts as a router, this ARP Request (sent