insecure SD-WAN
Your insecure SD-WAN and site network are not safe to run as they are.
First result within 24 hours.
You have several sites that need LAN, WAN, Wi-Fi and SD-WAN to work, with security inside the network rather than bolted on afterwards.
Recognize your situation?
- Sites drop, and the backup path does not take over as designed
- Policies conflict or are bypassed at a branch
- A branch is still a flat, trusted island
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
The problem
What insecure SD-WAN looks like, how you can tell, and what is at stake if it stays.
Signs your SD-WAN and site network are not safe to run as they are
These are concrete signals that the problem is the path and the policy, not only a noisy provider ticket.
Sites drop, and the backup path does not take over as designed
A failover that was never tested is a hope. Users feel it before anyone can draw the intended path.
Policies conflict or are bypassed at a branch
A local exception, a split tunnel, or a leftover router quietly undoes the overlay policy.
A branch is still a flat, trusted island
Guest, staff, printers and sometimes a small server all share the same trust.
Every outage becomes a debate between 'the provider' and 'our config'
Without a simple picture of the path, you cannot tell which story is true.
Security is only at the head office or the cloud edge
The branch path itself is under-protected, which is exactly where many incidents start.
What insecure SD-WAN looks like
What a weak multi-site network looks like, how it feels when every outage is a debate, and why connecting sites without containing them is a single incident waiting for a second building.
An insecure or failing SD-WAN leaves sites exposed or offline: links drop, policies conflict, a backup path was never tested, or a branch is still a flat, trusted island with security bolted on afterwards.
SD-WAN projects often stall halfway: the overlay is up, the policy is messy, and the old routers were never fully retired. Wi-Fi and guest access were left as a local exception. Security belongs inside the network, not only in front of it.
Links, policy or a branch path is already unsafe
Links drop, policies conflict, a backup path was never tested, or a branch is still a flat, trusted island. Wi-Fi and guest access were left as a local exception.
Nobody can show how a packet is supposed to travel
Every outage becomes a debate between 'the provider' and 'our config', and nobody can show a simple picture of how a packet is supposed to travel.
A network that connects sites must also contain them
A network that connects sites without containing them is a single incident waiting for a second building.
If you leave it, and if we close the urgent gaps
If you leave it
A weak branch can become the entry point, or a failed path can take orders, care, or production offline across sites.
If we close it
The urgent path or policy failure is fixed, and you have a clear note of how traffic is supposed to move and what still needs a larger rollout.
Recognize your situation?Message us, we will sort it out.
Why it happens
Where this usually comes from, why it shows up in fast or AI-assisted work, and how to check it yourself.
Why SD-WAN estates end up messy and unsafe
Halfway rollouts, leftover gear, and local exceptions are the usual causes, not a single bad box.
- 01
The overlay was switched on before policy was finished
Connectivity arrived first. Containment was scheduled later, then later slipped.
- 02
Old routers and extra paths were kept 'just in case'
The backup became an unreviewed door.
- 03
Branch staff made local exceptions to get something working
A printer, a vendor, or a Wi-Fi guest rule became permanent.
- 04
The provider and the internal design were never reconciled
Two sources of truth means no source of truth in an incident.
- 05
Security was treated as an appliance in front, not a property of the path
SD-WAN and IP networks need security inside the path, not only at a border.
Why insecure or failing SD-WAN is showing up now
More organisations depend on many sites, home paths, and cloud exits at once. Lean teams inherit a halfway overlay. Assistants can draft policy and still leave a leftover router in place. The honest work is a human reading of the real path, the real exceptions, and the security that should live in the network.
How to review an SD-WAN or multi-site path yourself
These checks do not replace a specialist, but they make the first conversation sharper.
Draw the intended path for one important application
If you cannot, the first finding is the missing picture.
Test the failover in a planned window, or admit you have not
An untested backup path is not a backup.
List local exceptions at two branches
If they already differ, policy is not really central.
See what a guest or a contractor can reach from a site
Flat branch trust is often wider than people think.
Check who can change overlay policy, and whether those changes are logged
A quiet policy change is a quiet incident.
0/ 5
Recognize your situation?Message us, we will sort it out.
How Contentum fixes it
A senior specialist leads. AI is a tool. A human checks the result.
SD-WAN projects often stall halfway: the overlay is up, the policy is messy, and the old routers were never fully retired.
Contentum is Human First. A specialist leads IP network and SD-WAN work. AI may help us read configs. A human checks that the path and the security policy actually match. We do not promise to rebuild an entire multi-site network in a day.
You need routing, policy and the security that belongs in the network to match. We do not promise to rebuild an entire multi-site network in a day.
How a typical weekday case moves
- 01Message received
- 02Specialist named
- 03Diagnosis
- 04Fix
- 05Human check
- 06Handover
How to get a human onto an SD-WAN or site-network problem
No web form, no web chat. We do not promise to rebuild an entire multi-site network in a day.
Write about the path that fails or feels unsafe
Write on WhatsApp or Telegram. Name the sites, the symptoms, and whether you have a provider, leftover routers, or a recent change.
You get a specialist's name
Within a minute you should see the name of the person who will lead. That specialist is alerted, and can be called if they do not respond.
A weekday case in scope is the 24-hour aim
The urgent path or policy failure, plus a clear picture of intended traffic, is the aim on a typical weekday. A full multi-site rollout is a complex project, and we will say so.
How a Contentum specialist fixes SD-WAN and site networks
We start with the failing or unsafe path, then fix routing, policy and the security that belongs in the network.
We start with the failing or unsafe path, then fix routing, policy and the security that belongs in the network. A full multi-site rollout is a complex project; a typical weekday case in scope is the 24-hour aim.
- 01
Establish the real path, not the slide
Including leftover devices and local exceptions.
- 02
Fix the urgent failure or unsafe opening
A broken failover, a flat branch, or a policy bypass that is already hurting you.
- 03
Put security back into the path
Access, encryption, and what a branch is allowed to reach.
- 04
Make the intended design visible to operators
A short picture beats two conflicting stories.
- 05
Leave a larger rollout or provider change as a named project
We will not hide a multi-site programme inside a session.
What to send so the first session is sharp
A simple site list and a description of the symptom is enough to start.
Sites and how they connect today
SD-WAN, MPLS leftovers, VPN, or a mix.
The symptom: drops, slow paths, or a security concern
When it started, and who is being blamed.
Providers and leftover equipment you know about
Even a partial list helps.
Change windows
Especially if a site cannot be touched in business hours.
Any recent incident that started at a branch
If you have one, describe it briefly.
Quick and urgent fixes
First 4 hours with a specialist + unlimited AI: free, once per client. Further work is paid, on request. A human leads and checks the result.
Free (first session)
Complex projects
Larger work uses a different rate, on request. We say so before we continue.
On request
Weekdays, then weekends
The base plan is weekdays only. Weekend work is a separate product. Any surcharge is stated up front, before any call, and depends on complexity. Amount: on request.
On request
The first session is free: the first 4 hours with a specialist, plus unlimited AI, once per client. Work beyond that, the complex-project rate, and the weekend rate are paid, on request.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.
Stay fixed
What not to do next, the stacks we see in this kind of work, and how to keep the fix in place.
Mistakes that keep multi-site networks unsafe
These are common in halfway rollouts.
Leaving the old path up without reviewing it as a door
A leftover router is still in the design, whether you remember it or not.
Trusting a provider dashboard as a security design
Availability is not containment.
Allowing each branch to invent exceptions
That is how a central policy dies.
Rebuilding everything because one path failed
Fix the urgent path, then plan the programme. Do not mix the two silently.
Ignoring Wi-Fi and guest access at the site
They are part of the same network story.
How to keep a multi-site network honest after the first fix
Paths drift when exceptions and leftover gear are not reviewed.
Keep a living path picture
One page operators actually use.
Test failover on a calendar
An untested path is not a backup.
Give exceptions an expiry
A printer rule should not become a permanent bypass.
Retire leftover gear on purpose
Or document why it must stay, and who owns the risk.
Multi-site setups we usually review
We work with the network you have, including mixed vendors and leftover gear.
SD-WAN overlays and their controllers
Policy, identity, and change control.
IP networks, LAN and Wi-Fi at the site
Flat VLANs, guests, and printers.
Hybrid exits to cloud and data centres
Where the path actually leaves the site.
Backup links and leftover VPN
The quiet second door.
Recognize your situation?Message us, we will sort it out.
Questions about insecure or failing SD-WAN
Straight answers about this problem, the session, and what happens next.
Will you fight with our network provider?
No. We will read the real path and say whether the problem sits in their scope, yours, or both. The point is a result, not a blame story.
What do I get within 24 hours?
A first result: a gap assessment and a plan you can act on, on a typical weekday in agreed scope. A finished programme — a full SOC, a certificate, or a rebuilt estate — is later work, and we will say so. The first 4 hours with a specialist, plus unlimited AI as a tool, are free, once per client.
Do we have to replace our current SD-WAN vendor?
Not necessarily. We start from what you have. A change of vendor, if it is truly needed, is a later agreed project.
Is this only a security topic, or also uptime?
Both, when the path fails or is unsafe. We will say which side is leading in your case.
What do I get within 24 hours?
A first result: a gap assessment and a plan you can act on, on a typical weekday in agreed scope. A finished programme — a full SOC, a certificate, or a rebuilt estate — is later work, and we will say so. The first 4 hours with a specialist, plus unlimited AI as a tool, are free, once per client.
Do I fill in a form?
No. There is no web form and no web chat. Write on WhatsApp or Telegram. Within a minute you should see the specialist's name.
Will you publish findings?
No. This is a private service conversation, not a public write-up.
What is free?
You get one free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool. Further work is paid, on request.
Do you take emergency work during an active attack?
Yes. If you are under an active attack, write now on WhatsApp or Telegram and say so in the first message. A specialist is alerted, and can be called. Keep your own incident plan running in parallel — two paths are safer than waiting. We start as soon as we can on a typical weekday case in scope. We do not promise to stop every attack in a day, but we do take this work.
What is free, and what does “within 24 hours” mean?
You get one free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool. On a typical weekday, for a case in agreed scope, we aim to give you a first result within 24 hours: a gap assessment and a plan. On urgent, in-scope fixes we often close the job itself in that window. That 24-hour line is a speed aim, not 24 hours of unpaid work, and not a promise to finish a large programme in a day.
Related security problems we also take on.
See all 20 problems. Each page is written for one pain, not as a copy of this one.
Your insecure SD-WAN and site network are not safe to run as they are. First result within 24 hours.
Write on WhatsApp or Telegram. You will talk to a person. We aim to give you a first result within 24 hours — a gap assessment and a plan — the unsafe or failing path, not an entire network rebuilt in a day.
One free session per client: the first 4 hours with a specialist, plus unlimited AI as a tool.