SD-WAN + SASE

Coordinate network paths with application access rules.

Secure Access Service Edge (SASE) combines software-defined WAN (SD-WAN) and cloud security. It suits distributed sites and users; define identity, inspection and paths together.

It is not a single product; providers, underlays, policies and the managed model must be specified.

Let’s talk

Two digital guardians outside an office: one diverts suspicious packets and the other lets legitimate traffic through.

How it works

Coordinate identity, access and inspection with the paths applications use.

Your site

SD-WAN edge

Preferred path

Alternative path

Sites and applications

One policy, several paths

SD-WAN devices apply policies over compatible IP access such as Internet or IP VPN (the underlay). In the Versa variant, encrypted tunnels connect SD-WAN endpoints (the overlay); Internet/SaaS traffic follows the agreed breakout. Different applications can have different path criteria.

SASE combines this network management with cloud security controls (SSE, Security Service Edge). Depending on contracted functions, these controls validate identity and access and inspect traffic to Internet or private applications. Routing and security are designed together, but perform different functions.

Your site

SD-WAN edge

Degraded quality

Eligible alternative

Sites and applications

An active link can still perform poorly

First separate Wi-Fi/LAN, application and WAN causes: compare a wired call, affected sites and peak-load periods. More fibre will not fix poor Wi-Fi coverage or a fault in the video-call service.

Versa measures latency, delay variation (jitter) and packet loss. If the WAN path is the problem, a policy can prioritise voice and steer it to an eligible alternative using configured thresholds; it does not create capacity or guarantee uninterrupted sessions.

Your site

SD-WAN edge

Access unavailable

Eligible alternative

Sites and applications

Continuity starts with design

If an access fails, another working path needs suitable routes and capacity. Two circuits sharing a physical route, device or power source may fail together.

The pilot should test failure, recovery and application behaviour. Protection against device failure requires considering a high-availability architecture, not just a second circuit.

Illustrative case: from situation to decision

Situation: A site and a remote user access the same application with different permissions.
Option: Coordinate path policies with the contracted identity and inspection controls.
Check: Test permissions and revocation, and check that changing paths does not bypass agreed controls.

SD-WAN does not create capacity or physical diversity. SASE adds security controls according to the contracted variant.

Decisions for your project

Applications and quality: Identify critical flows and acceptable latency, jitter and loss; voice and backups need different policies.
Access and routing: Inventory IP VPN/MPLS, Internet or other compatible access; prefixes, segmentation and return paths.
Actual continuity: Validate alternative capacity, physical diversity, equipment and power. A second access does not remove every dependency.
Operations and security: Agree who changes policies, who handles incidents and which SSE functions are part of the service.

From design to operation

First we characterise applications, then agree a design with Colt and validate a pilot site. Phased migration should include acceptance tests and a rollback plan.

Complements, alternatives and variants

Colt IP AccessComplementProvides Internet access over which SD-WAN policies can operate.IP VPNComplementCan provide private transport in a hybrid architecture.Colt SSEComplementAdds cloud access controls and inspection; this is different from path selection.

Product sources

What challenge would you like to solve?

Tell us what is happening and what needs to change. You do not need to know the catalogue.

Name

Company

Work email

Phone (optional)

What would you like to solve? (optional)

Do not include passwords, sensitive data or confidential information.

Ideas to get started (optional)

You can use this idea and explain what is happening in your situation.

Enquiry context

This context will be added to your message. You can edit or remove it; it does not replace your explanation.

Product (optional)

Case or situation (optional)

Service family (optional)

Locations and timing (optional)

Cities or countries

When do you need it?

* Required fields. The challenge description, phone, service and context are optional.

Your draft is kept while you navigate this website. Reloading or closing the tab clears it.

Controller: Begumva, S.L. We process your details to handle your enquiry and, only if you choose, send updates. Read about recipients, retention and your rights.

Privacy

I have read the privacy policy. *Send me technology updates by email (optional).

You can also email us at contact@coltplatinum.es.

What happens next?

Understand the context
What’s changing, where your teams work and what cannot fail. Still defining the brief? We can help structure it.
Design the options
Bring needs, Colt capabilities and technical criteria together. Compare alternatives and explain dependencies and limits.
Validate before committing
Coverage, feasibility, responsibilities and terms. A commercial proposal is developed with the relevant specialists.

ColtPlatinum guides the project and coordinates commercial discussions and follow-up. Colt validates feasibility, enters into the service contract, and provisions, installs and delivers the services.

Availability, coverage, capabilities, SLAs and timelines are subject to technical validation and contract. No diagram is a service guarantee.