SASE – It’s revolutionising network and security architecture. It’s shaking up how we connect. But what exactly is all the talk about? What does it mean for your organisation? Is your organisation sassy enough to conquer a SASE makeover?

Focus Points

• The future of our network and security infrastructures being cloud-centric is imminent.
• SASE has several advantages over traditional architectures, not the least of which include greater scalability and flexibility for your organisation
• Now is the perfect time to assess where on the SASE journey your organisation is at and what this means for your existing networking infrastructure.

What’s sassy about SASE?

Disruptive and transformational are just a few words that come to mind. Gartner defines SASE – pronounced “sassy” and shortened for ‘Secure Access Service Edge’ – as ‘an emerging cybersecurity concept combining comprehensive WAN capabilities with comprehensive network security functions…to support the dynamic secure access needs of digital enterprises’.

Unlike the legacy WAN, SASE shifts the focus from a network where each branch connects to a central office to access data and security services to the concept where an entity (e.g. user, group of people (branch), a single device, IoT system or edge computing location) is connected directly from the edge to cloud-based services bypassing the need for a centralised WAN.

SASE has several advantages over traditional architectures, not the least of which include greater scalability and flexibility for your organisation, potentially reduced network costs, and better performance for the end-user. SASE done right will open the door to enhanced security features, moving the management of your security to a cloud access security broker (CASB) whilst:

• protecting your users, regardless of where the device or user is located, from threats through secure web gateways (SWG) and remote browser isolation,
• securing your applications and data through zero-trust network access (ZTNA), firewall as a service (FWaaS) and protecting your web API’s (WAAPaaS).

Why is it the trend?

The era of centralised network and security architectures is fading. Today’s enterprises are hyper-distributed. More and more businesses are moving to a Software-as-a-Service (SaaS), cloud-based services and edge compute platforms, where there is an increased reliance on SDWAN connectivity, and remote user access is the new normal. As a result, the traditional reliance on enterprise data centres for routing and security is becoming obsolete.

We are at the forefront of a new transformation. We are shifting from relying on location as the core of networking and security to the end-user. With 2020 being a tumultuous year, with a massive exodus of users working from home, the need for such change has never been so evident. Whilst 81% of the population is now working from home, Gartner has predicted post-COVID that 41% of employees will remain working from home. The question is – is your security prepared for this – are you getting sassy with SASE?

The future of our network and security infrastructures being cloud-centric is imminent. Users need to have more confidence in a consistent and secure experience everywhere, anywhere.

If you are ready to get sassy with SASE, now is the perfect time to assess where on the SASE journey your organisation is at and what this means for your existing networking infrastructure.

Are you the sassy-type?

Ask yourself – Are you ready to revolutionise your network? Are you willing to embrace disruption to stay relevant? If so, you are ready to get sassy with SASE.

Enterprises of all sizes are discovering their reasons for needing to transform to SASE, including;

• Corporate services are changing to cloud-based providers
• The move from centralised MPLS networks to the Internet at the edge
• More user traffic from branches directed to public clouds, detouring the data centre
• The need to protect remote users as they perform work outside of the enterprise network and on their own devices
• Consolidating network and security
• Optimising cloud-based applications that are being accessed from the edge

If you tick any of the boxes above your organisation is also ready to embrace the change.

Get your SASE-on?

Adopting SASE should be part of your organisation’s IT journey. It is not something that has to be deployed all in one go. The goal is to ensure that you integrate it seamlessly, and you provide an optimal experience for the user.

The first step should be to identify the journey and the different phases within. Determine what is already in place and are already performing well, and what needs transforming.

Once you have done this, you will need to consider how to;

• Position the adoption of SASE as a digital business enabler to ensure speed and agility.
• Change focus from managing security boxes to delivering policy-based security services.
• Engage with network architects to discover your SASE capabilities. Use SD-WAN, and MPLS offload projects to evaluate integrated network security services.
• Identify ways to reduce the complexity on your network security

To help your organisation map out its journey to SASE contact Oreta today.

Securing important resources and applications is now vital, particularly with the continued rise in cyberattacks. But, how can you manage critical new levels of security without interruptions to your business operations, creating havoc with your employees and defiling your current defenses? More and more enterprises are leveraging Zero Trust to enhance their security posture, shift their reliance from infrastructure to the cloud, and have greater access control through granular policy enforcement. So what is ZTNA and how does it differ from the traditional VPN?

What is ZTNA?

ZTNA stands for Zero Trust Network Access, a type of security model that provides secure remote access to applications and services regardless of where they are hosted. The model considers all traffic as hostile. In the context of remote user access, the model does not trust any user until verification of their identities is complete. A software-defined perimeter (SDP) between users and applications completes the ZNTA model. SDP will consider the correct user credentials and multiple contextual factors before it grants a user access.

With COVID-19, the mobile workforce has grown exponentially, which will remain that way for the foreseeable future. Remote workers are working from insecure networks or using their own devices, making them more vulnerable to cyberattacks. A CAIC report indicates that between January and June 2020, 67% of cyber breaches were the result of compromised or stolen credentials. Statistics such as these show the growing importance of adopting security models like ZTNA to protect corporate application and data.

How is ZTNA different to VPN?

ZTNA and VPN serve a similar purpose of providing secure remote access. However, there are critical differences between the two types of technologies.

       1. Network Access vs Identity-based and Application access

Most VPN solutions use IP-based access control (i.e. source, destination IP address and protocol) to create access policies. An issue with these solutions is that the IP address does not provide much information about a user and frequently changes, making it difficult to tell all the users apart and track them, and often requires complex configuration such as separate IP allocation for different user groups. Access policies based on protocols also provides minimal granularity with regards to what applications users can access as many modern applications share the same sets of protocols and ports.

On the other hand, ZTNA uses SDP to control access based on the user’s identity and application. ZTNA enables the development of more granular policies and gives users access only to sanctioned applications. Furthermore, the level of access provided depends on a risk assessment of contextual information, such as a device’s security posture and location.

       2. Appliance-based v Cloud-delivered

Another common issue coming from an appliance-based solution like VPN is scalability and management overheads.

Typically, datacentres and head offices often require the deployment of VPN appliances. Users connect their VPN clients to the applicances to access corporate resources. Users may need to switch between VPN connection points, depending on the location of the resources or what the core network needs to support a single VPN entry point for resources across multiple sites. As the underlyinginfrastructure for VPN is often under or over-provisioned, this can result in businesses failing to meet their goals, poor user experience and excessive overheads.

Unlike VPN, ZTNA is not bound by infrastructure or a location. It is a cloud-based service whereby you can have the flexibility of scaling up and down on a needs-by-needs basis. Behind the scene, your service provider will take care of the underlying infrastructure and maintenance. Your IT team will be relieved from capacity planning, hardware/software ordering, deployment and ongoing maintenance.

How does ZTNA relate to SASE?

The SASE architecture aims to address network and security issues relating to the increasing reliance on the Cloud and mobility adoption. SASE enables applications and services to reside in the Cloud and on-prem, and permit users to work anywhere. The two critical elements of SASEtecture are identity-driven and securing all edges, including the mobile workforce. As part of the core features of SASE, ZTNA provides identity-based authentication, context-based access control and secure remote access from a mobile workforce.

Taking you further…

Whether you are looking at a standalone ZTNA solution or a full SASE architecture, you should also consider inspection capability. A ZTNA solution should not just play the role of granting user access, but also continuously monitor user traffic for any abnormal or malicious activity. Another aspect to look at is how well you can integrate your existing solutions and minimise complexity and silos. ZTNA will not cover every security aspect, but it should form part of your collective solutions to achieve better cybersecurity.