SD-WAN acceptance · Buyer guide
SD-WAN acceptance should cover degraded links as well as complete outages. Unplugging an internet circuit proves only one failure scenario. Users may suffer more often when a link remains up but becomes unsuitable for an important application. Ask an SD-WAN bidder to define application and path-quality acceptance cases before the demonstration.

SD-WAN acceptance: define application conditions
Identify business-critical flows, normal paths and fallback requirements with the service owner. Fortinet describes application-aware steering and performance considerations in Secure SD-WAN. Convert that broad capability into a site-specific expected outcome: which approved traffic should use which path under stated conditions.
Agree a safe degraded-path test
Ask the engineer to propose an authorised method for representing the relevant delay, loss or other impairment, with containment and rollback. Do not interfere with a live carrier or production service casually. Record how application behaviour and path decisions will be observed, including existing sessions where the platform and policy make that relevant.

Verify recovery as well as diversion
Document what happens when quality improves and whether the design avoids undesirable repeated changes. Include circuit dependencies, subscriptions and support ownership in the order. Keep the final evidence tied to the application case and device software. A successful staged test should not become a promise about every future internet condition.
SD-WAN acceptance: test worksheet
Use the rows below to compare proposals. Enter the actual evidence reference, accountable owner and unresolved decision against each item. Keep provisional assumptions visible when asking bidders to revise their prices.
| Decision | Evidence to request | Purpose |
|---|---|---|
| Application | Business priority and expected path | Service-owner decision |
| Impairment | Authorised method and conditions | Controlled test |
| Observation | Path decision and user service | Evidence record |
| Recovery | Stable return and exceptions | Acceptance outcome |
Questions buyers ask
Is unplugging a cable a sufficient SD-WAN test?
It covers one failure condition. Add the degraded-service cases that matter to the business.
Can tests run on live circuits without planning?
Use an authorised method with impact controls, a window where needed and a rollback owner.
Should subscriptions be priced?
Yes. Identify the functions and entitlements required by the selected design over the compared term.
What about existing sessions?
Ask the engineer to state expected behaviour for the chosen platform, policy and applications.
What should RIAM receive?
Circuit inventory, application priorities, observed problems and acceptable operational windows help define an evidence-based pilot.
Manufacturer research and scope
Fortinet: Secure SD-WAN capabilities, reviewed 31 October 2026. The buying worksheet is RIAM editorial analysis; it is not an OEM-approved design. Confirm current product, software, support and local requirements for the selected bill of materials.
Brief RIAM with the evidence
Share the existing inventory, the specific service or buying decision, available records and access constraints with RIAM’s security services team. Ask for a scoped assessment with deliverables, responsibilities, exclusions and acceptance evidence. Site work and production changes require the responsible owners’ approved plan.
Also read our multi-site pilot acceptance.


