Legacy Security vs SASE

A complete SASE platform puts security as we know it in the “legacy” category. SASE is a single cloud platform containing the full spectrum of security functionality, and it effectively replaces legacy solutions that were until now consumed separately.

Legacy Security Pitfalls

Consumed Separately

Legacy security solutions are deployed individually and added as one part of the full stack


Legacy security tools typically come with a single purpose, or type of attack against which it defends

Results in Tech Silos

Security tools that operate independently of one another make orchestration difficult

Intensive Configuration

IT must work hard to configure products in a secure manner, even with no hardware involved

A Look at Legacy Security

Legacy security is represented by the many examples of single-purpose security tools that still exist today – firewalls, VPNs, multi-factor authentication, monitoring and logging solutions and more. Though these tools are still required to secure networks and traffic, they can be considered “traditional” because in the very near future, companies will no longer use them in the same way.

Here’s how an IT team operates today: At the outset members of the team identify the resources that need protecting and have built a list of multiple products to buy, install, integrate, and manage in order to secure them properly. Though the downsides of this approach couldn’t be addressed until now, the result of this planning is multiple tech silos that require timely and expensive upkeep, not to mention detract from productivity elsewhere.

Configuring a number of solutions through many consoles takes lots of time, daily maintenance and difficult configuration – which is itself a risk to security. Moreover, when these disparate point solutions need to scale as the company grows, the work facing IT teams multiplies even further, and open gaps in the network where hackers can get in.