{"id":17345,"date":"2026-02-03T09:01:09","date_gmt":"2026-02-03T08:01:09","guid":{"rendered":"https:\/\/www.savecall.de\/sase-only-works-as-well-as-your-underlay\/"},"modified":"2026-04-28T11:01:51","modified_gmt":"2026-04-28T09:01:51","slug":"sase-only-works-as-well-as-your-underlay","status":"publish","type":"post","link":"https:\/\/www.savecall.de\/en\/sase-only-works-as-well-as-your-underlay\/","title":{"rendered":"SASE only works as well as your underlay"},"content":{"rendered":"\n

\n

\n

SASE only works as well as your underlay <\/h1>\n<\/div>\n\n\n\n

Trusted Advisor for IT & Telecommunications Sourcing<\/h3>\n<\/div>\n\n\n\n
\n
\n
Get SASE off to the right start: Why underlay determines success<\/h2>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
\n
Increasing demands on performance, security<\/a> and availability meet distributed locations<\/a>, cloud applications<\/a> and hybrid work. This is exactly what SASE<\/a> is supposed to solve – but it often fails due to unstable or inconsistent connectivity. The problem is not SASE, but underlay<\/a>. <\/p>\n\n\n\n
What this means for you<\/strong><\/h5>\n\n\n\n\n
Poor user experience despite modern SASE architecture<\/li>\n\n\n\n
Voice, video & SaaS react sensitively to latency, jitter & packet loss<\/li>\n\n\n\n
Security policies lose effect with unstable transport<\/li>\n\n\n\n
Fault clearance takes longer with fragmented providers & SLAs<\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
What this article is about<\/strong><\/h5>\n\n\n\n<\/div>\n\n\n\n
This article shows why a stable, resilient underlay is the basis for a functioning SASE. The role connectivity plays for performance, security and operation becomes clear – and why sequence determines success. <\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
Book a consultation<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
\n
\n
>20%
Savings<\/h2>\n<\/div>\n\n\n\n
\n
Learn more<\/a><\/h5>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
99,99%
Availability<\/h2>\n<\/div>\n\n\n\n
\n
Learn more<\/a><\/h5>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
24\/7
Support<\/h2>\n<\/div>\n\n\n\n
\n
Contact<\/a><\/h5>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
Why the path to the Secure Access Service Edge (SASE) doesn’t start with the vendor pitch – but with connectivity, resilience and transparency <\/em><\/h4>\n\n\n\n<\/div>\n\n\n\n
\n
SASE bundles network and security functions cloud-natively – but it doesn’t automatically make bad lines better. <\/li>\n\n\n\n
If your underlay (access\/transport) fluctuates, is fragmented or fails, user experience, security policy effectiveness and operation will suffer. <\/li>\n\n\n\n
The first step towards SASE is therefore: check the underlay, standardize it and make it resilient – then set up the overlay (SD-WAN\/SASE) on top. <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
Why so many companies are relying on SASE right now <\/h4>\n\n\n\n
<\/div>\n\n\n\n
Hybrid work, multi-cloud and distributed applications have pushed the edge of the network: Users, devices and workloads are everywhere. At the same time, the threat landscape is growing – and security<\/a> must work in-line without destroying performance. SASE<\/a> addresses exactly this by providing network performance and security functions as a unified cloud service – independent of location and scalable. <\/p>\n<\/div>\n\n\n\n
\n
\n
$\"Alpine$ <\/figure>\n<\/div>\n\n\n\n
\n
\n
SASE explained in brief:
What is in the architecture? <\/h4>\n\n\n\n
<\/div>\n\n\n\n
SASE typically combines the following components: <\/p>\n\n\n\n
<\/div>\n\n\n\n
Network\/control<\/strong> <\/p>\n\n\n\n
\n
SD-WAN<\/a> (policy-based path control, app awareness, encryption) <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
Security services<\/strong> <\/p>\n\n\n\n
\n
SWG (Secure Web Gateway) <\/li>\n\n\n\n
CASB (Cloud Access Security Broker) <\/li>\n\n\n\n
FWaaS (Firewall as a Service) <\/li>\n\n\n\n
ZTNA (Zero Trust Network Access) <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
The goal: secure, high-performance access to applications – no matter where users and workloads are located. <\/p>\n\n\n\n
\n
Book a consultation<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
<\/div>\n\n\n\n
\n
The most common mistake in SASE projects <\/h3>\n\n\n\n
<\/div>\n\n\n\n
Many organizations start with the tool selection: “Which SASE provider? Which ZTNA solution? Which SD-WAN?” What is often missing: an honest inventory of the global underlay network. If the quality of your underlay varies from region to region or if SLAs and fault clearance processes vary from provider to provider, then your SASE rollout will exacerbate these problems – not solve them. <\/p>\n\n\n\n
<\/div>\n\n\n\n
The first question before every SASE rollout: Is our underlay SASE-ready?<\/strong> <\/h4>\n\n\n\n<\/div>\n\n\n\n
Use this checklist as a starting point: <\/p>\n\n\n\n
\n
Do we have consistent connectivity across all regions? <\/li>\n\n\n\n
Are there locations that are based on consumer-grade access? <\/li>\n\n\n\n
Do we achieve low latency and high availability where it counts (voice\/video\/real-time)? <\/li>\n\n\n\n
Is resilience planned (redundancy, various paths, fast failover)? <\/li>\n\n\n\n
How quickly can we isolate and rectify underlay faults? <\/li>\n\n\n\n
Are there standardized SLAs\/escalation paths or is there uncontrolled growth? <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
If you say “not sure” more than once here: Underlay first. <\/p>\n\n\n\n
<\/div>\n\n\n\n
Underlay vs. overlay – the difference that determines success <\/h3>\n\n\n\n
<\/div>\n\n\n\n
Underlay<\/a> (the “road”)<\/strong> <\/h4>\n\n\n\n
The underlay is the physical transport layer: fiber optic\/DIA<\/a>, Ethernet<\/a>, MPLS<\/a>, fixed wireless, satellite\/LEO – including last mile, providers, handovers and SLAs. <\/p>\n\n\n\n
<\/div>\n\n\n\n
Overlay (the “intelligence”)<\/strong> <\/h4>\n\n\n\nThe overlay is the virtual control layer on top: SD-WAN tunnels<\/a>, app routing, encryption and policies – plus cloud-based security services<\/a> in the SASE model<\/a>. <\/p>\n\n\n\n
Important: An overlay cannot turn bad roads into highways. At most, it can take more intelligent evasive action – if alternatives exist. <\/p>\n\n\n\n
<\/div>\n\n\n\n
What a weak underlay does in practice with SASE<\/strong><\/h4>\n\n\n\n
<\/p>\n\n\n\n
An unstable underlay often leads to: <\/p>\n\n\n\n
\n
Unpredictable latency: poor voice\/video quality, sluggish SaaS apps <\/li>\n\n\n\n
Packet loss and jitter: Policies work, but the experience breaks down <\/li>\n\n\n\n
Longer MTTRs (Mean Time to Repair): because troubleshooting between providers\/regions becomes slow <\/li>\n\n\n\n
Higher operating costs: more tickets, more escalations, more “fire department” <\/li>\n\n\n\n
Frustrated end users: SASE is perceived as a problem instead of a solution <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
\n
Book a consultation<\/a><\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
\n
What does a SASE-compatible underlay really look like?<\/h2>\n<\/div>\n<\/div>\n\n\n\n
\n
1) Resilience by design (not by hope) <\/strong><\/h4>\n\n\n\n
\n
Primary: Fiber optics\/DIA for critical locations <\/li>\n\n\n\n
Secondary: Fixed wireless or LEO as an independent backup path (or for locations that are difficult to access) <\/li>\n\n\n\n
Goal: fast failover without users noticing <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
2) Consistency across countries and providers <\/strong><\/h4>\n\n\n\n
\n
Standardized performance targets (latency\/jitter\/loss) <\/li>\n\n\n\n
Standardized SLAs and escalation processes <\/li>\n\n\n\n
Less provider proliferation = faster fault clearance <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
3) End-to-end transparency <\/strong><\/h4>\n\n\n\n
Without monitoring, your SASE policy stack is flying blind. Underlay telemetry for all links creates clarity and makes it possible to measure what the user is really experiencing – and whether a problem comes from security or transport. <\/p>\n\n\n\n
<\/div>\n\n\n\n
Change of perspective: from product to customer reality <\/h3>\n\n\n\n
Before talking about SASE features, it is worth taking a look at the reality in the company: Where do most tickets arise today – performance, security, provider coordination or remote sites? What is the real driver: cloud migration, hybrid work, compliance, cost pressure or standardization? When the “why” is clear, SASE becomes a business enabler rather than a tool project. <\/p>\n\n\n\n
Typical stumbling blocks: talking about specific products or carriers too early. The motive for the purchase and the need are decisive first – only then does the right solution follow. <\/p>\n<\/div>\n\n\n\n
\n
\n
\n
How Savecall supports you <\/h3>\n\n\n\n
Savecall works vendor-neutral: i.e. we compare location options across the market (carrier, last mile, SLA and costs) and turn fragmentation into a controllable platform. <\/p>\n\n\n\n
<\/div>\n\n\n\n
Our typical approach: <\/p>\n\n\n\n
\n
Underlay audit: performance, availability, risk, provider landscape, dependencies <\/li>\n\n\n\n
Target image and standards: SLA framework, redundancy principle,
location classes (HQ\/Branch\/Remote) <\/li>\n\n\n\n
Sourcing and design: suitable connectivity per location (DIA\/Fiber\/FWA\/LEO\/Mix) <\/li>\n\n\n\n
Operating model and monitoring: clear processes, escalation, transparency <\/li>\n\n\n\n
Then overlay: Roll out SD-WAN\/SASE in such a way that security and user experience win <\/li>\n<\/ul>\n\n\n\n
<\/div>\n\n\n\n
Conclusion: Underlay first – then SASE delivers the promised effect <\/h4>\n\n\n\n
<\/div>\n\n\n\n
SASE<\/a> can massively accelerate cloud, hybrid work and security – if the foundation is right. A well-designed underlay<\/a> provides stability, predictable performance and fast fault clearance. A SASE overlay can play to its strengths: secure, scalable, everywhere. <\/p>\n\n\n\n
<\/div>\n\n\n\n
\n
Book a consultation<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
$\"A$ <\/figure>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n
\n
\n
Customers<\/h3>\n<\/div>\n\n\n\r\n
\r\n
\r\n
\r\n
\r\n
\r\n $\"ZVEI$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"TotalEnergies,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"TELUS,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Social$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"smava,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Sivantos,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Sanacorp,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Nippon$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"MWB,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"MSC,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Kraftanlagen$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"McDermott,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Magna,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"LV$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Lebenswege,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Korian,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Kekst$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"K\u00e4uferportal,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"item,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Ingram,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"ILF$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Hyatt,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Heinrich-B\u00f6ll-Stiftung,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Fressnapf,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Financial.com,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Contora,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Cognizant,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Bitmarck,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"AVIA,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Aurelius,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Almeda,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Allianz$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Allianz$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Allianz,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Advantest,$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"Satellite$ \r\n <\/div>\r\n <\/div>\r\n
\r\n
\r\n $\"B\u00f6rsen$ \r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n <\/div>\r\n