NNetify

Get comparable SD-WAN and SASE proposals from UK providers

Use Netify to request comparable proposals, demos and pre-sales contacts from named SD-WAN and SASE providers. Research is open, and you approve each request before a supplier receives it. SD-WAN provides the connectivity component of SASE.

  1. 1. Tell us your requirement

    Start with six essentials or paste your existing shortlist.

  2. 2. Approve who we approach

    Named suppliers, an anonymous brief and one agreed scope.

  3. 3. Compare the written responses

    Agree a response target before outreach. We report declines and agree the next step.

Netify is paid by suppliers when an introduction leads to business. Commission never affects the evidence order.

Prepare my sourcing plan →

UK Government & Public Sector Buyer's Guide · Last reviewed 19 November 2026

SD-WAN & SASE for Government and Public Sector

UK government departments, executive agencies, local authorities, blue-light services and arm’s-length public bodies are replacing legacy multiprotocol label switching (MPLS) WANs, Public Services Network (PSN) interconnects and perimeter VPN concentrators with Software-Defined Wide Area Networking (SD-WAN) and Secure Access Service Edge (SASE) architectures. Public sector buyers must balance wide-area transport modernisation against strict sovereign data handling, National Cyber Security Centre (NCSC) assurance frameworks and statutory public procurement rules.

This buyer’s guide sets out the technical, regulatory and commercial criteria required to specify, evaluate and procure SD-WAN and SASE across the UK public sector. It covers Government Security Classifications Policy (GSCP) handling for OFFICIAL and OFFICIAL-SENSITIVE data, NCSC Cyber Assessment Framework (CAF) alignment, Crown Commercial Service (CCS) purchasing routes under the Procurement Act 2023, operating realities by authority type and a structured Request for Proposal (RFP) checklist.

Written by Harry Yelland (19 November 2026). Fact-checked by Robert Sturt (19 November 2026).

Supplier Evidence & Shortlist

Looking for evaluated suppliers with confirmed UK coverage rather than the requirements and procurement guide? See the evaluated UK government and public sector providers.

Your buying project

Start a government project without re-entering this context

Review the suggested sector requirements in your private project. Use a short brief, a Short or Detailed RFP, or your own RFP or RFI. Your answers carry into the buying workspace; you decide when to publish.

Government and public sector shortlist tool

Which vendors fit your estate?

Preview aggregate coverage against UK government and public sector requirements. Private provider matching follows verified project publication.

Public sector priorities

Quick-start presets. Each one sets the matching capability requirements below, where you can refine feature by feature.

Operating model

Local authorities and arm’s-length bodies with lean network teams often require co-managed or fully managed delivery. Central departments with an internal NOC/SOC may prefer co-managed policy control.

Organisation size

Central departments and multi-agency shared services need multi-tenancy and RBAC separation across directorates. Smaller councils and public bodies benefit from turnkey managed assurance.

Regions you must cover

Most UK public sector estates require confirmed UK and Ireland PoPs, UK data residency for logs and telemetry, and UK-based support desks.

Cloud platforms

Select the public cloud platforms hosting citizen portals, Crown Hosting workloads, and departmental applications under the Cloud First policy.

AI capability

AIOps helps isolate underlay faults across council offices, depots and libraries. AI security analytics supports protective monitoring objectives.

Deployment ceiling

Framework call-offs and legacy WAN contract expiries carry fixed transition dates. Exclude providers whose typical activation exceeds your timetable.

Scoring profile

Security led aligns with NCSC CAF and zero trust programmes. Network led suits multi-site WAN replacement. Managed service led suits lean council IT teams.

Resilience and size

Citizen-facing services, emergency control rooms and revenue systems require tested dual-WAN and cellular failover.

Capability requirements (all 40 graded features)

Click once for required, twice for preferred, three times to clear. Public sector priorities above pre-select the relevant features.

Open this exact scenario in the full builder

Or describe your estate to the AI advisor

The advisor maps plain language onto these same filters and explains the result. It can also compare two providers head to head.

Open the full interactive filter at the public sector shortlist tool or review the UK government and public sector provider evaluation page.

What UK government and public sector buyers need from SD-WAN and SASE

Public sector networks carry traffic with fundamentally different risk profiles from commercial enterprise estates. A single unitary authority or central department network routinely transports citizen tax and welfare records, social care case files, electoral registers, criminal justice evidence, building management telemetry, voice and video collaboration and public Wi-Fi access across dozens or hundreds of civic buildings. Under the UK Government Security Classifications Policy (GSCP, published by the Cabinet Office on gov.uk), the vast majority of public service operations fall within the OFFICIAL tier, with a critical subset marked OFFICIAL-SENSITIVE where unauthorised disclosure could cause material harm to citizens or administrative operations.

When public bodies migrate from legacy private MPLS circuits to internet-underlay SD-WAN and cloud-delivered SASE, three technical boundaries become non-negotiable. First, all WAN overlay tunnels and cloud security inspection points handling OFFICIAL and OFFICIAL-SENSITIVE workloads must enforce NCSC-approved cryptographic profiles in transit and at rest, with clear key custody and certificate lifecycle governance. Second, data residency and metadata sovereignty must be contractually fixed within the United Kingdom (or explicitly approved Crown Hosting and UK public cloud regions) so that session logs, packet captures, Data Loss Prevention (DLP) inspection buffers and identity telemetry do not silently traverse or rest in non-UK jurisdictions.

Third, public sector buyers must account for legacy shared-network dependencies that still anchor inter-agency workflows. While the Cabinet Office and Central Digital and Data Office (CDDO) have progressively retired central PSN compliance certification in favour of the Internet First policy and Zero Trust architecture principles, individual departmental shared services, justice interconnects, local authority revenues and benefits gateways and NHS Health and Social Care Network (HSCN) peering interfaces still impose specific routing, DNS, IP addressing and firewall boundary controls during transition.

Multi-site public estates also exhibit acute physical diversity. A county or unitary council typically connects a principal civic headquarters, regional administrative offices, housing depots, social care hubs, libraries, leisure centres, waste transfer stations and temporary project sites. Central government departments connect Whitehall ministries, regional civil service hubs, border or port facilities, tribunals and citizen-facing jobcentres. Specifying a uniform circuit or hardware template across all locations leads either to over-spending at small community sites or under-provisioning resilience at critical operational centres. A defensible public sector SD-WAN and SASE specification separates site tiers by operational criticality, user concurrency and local underlay availability.

Citizen-facing digital services and multi-agency shared services add a further requirement: predictable application availability during transport degradation. When a local fibre break affects a council contact centre, social care duty desk or departmental casework hub, the SD-WAN fabric must steer real-time voice, virtual desktop infrastructure (VDI) and line-of-business SaaS sessions onto secondary fibre or 4G and 5G cellular links without dropping active sessions or requiring manual routing changes by local staff.

Compliance and assurance map

Public sector network and security procurements are audited against published UK government assurance standards rather than generic vendor marketing claims. Under the Government Cyber Security Strategy (2022 to 2030), central departments and critical public bodies are required to adopt the NCSC Cyber Assessment Framework (CAF) and demonstrate measurable progress against its four objectives: managing security risk (Objective A), protecting against cyber attack (Objective B), detecting cyber security events (Objective C) and minimising the impact of cyber security incidents (Objective D).

Before issuing an Invitation to Tender (ITT) or framework further competition, procurement and information assurance teams should map each regulatory or policy obligation to a specific technical requirement and a verifiable supplier evidence request. An ISO/IEC 27001 certificate covering a vendor’s corporate offices does not prove that its UK SASE points of presence (PoPs), management plane or managed Security Operations Centre (SOC) meet NCSC Cloud Security Principles or GovAssure scoping rules. The table below maps the primary UK public sector assurance schemes to concrete supplier questions.

UK public sector SD-WAN and SASE compliance and assurance mapping across NCSC CAF, Cyber Essentials Plus, NCSC Cloud Security Principles, GSCP, UK GDPR and NHS DSPT (last reviewed 19 November 2026).
RequirementScheme & primary sourceWhat to ask a supplier
Baseline and enhanced technical cyber hygiene across supplier and managed service boundaryCyber Essentials and Cyber Essentials Plus (NCSC / IASME, ncsc.gov.uk)Provide a current Cyber Essentials Plus certificate covering the legal entity delivering the managed SD-WAN or SASE service, and confirm how patch management, vulnerability remediation and boundary firewall controls are enforced across customer CPE and cloud gateways.
Outcome-based cyber resilience across governance, protection, detection and responseNCSC Cyber Assessment Framework (CAF v3.2) and GovAssure (Cabinet Office / NCSC)Detail how the platform and managed service support CAF Principle B.2 (Identity and Access Control), B.3 (Data Security), B.4 (System Security), B.5 (Resilient Networks and Systems) and C.1 (Security Monitoring), including role-based access control and immutable audit logs.
Cloud-hosted control plane, SSE inspection PoPs and tenant separationNCSC 14 Cloud Security Principles (ncsc.gov.uk/collection/cloud-security)Supply a completed NCSC Cloud Security Principles alignment statement covering data in transit protection, asset protection and resilience, separation between customers, governance framework, operational security, personnel security and secure user management.
Identity-centric access replacing implicit network-perimeter trustNCSC Zero Trust Architecture Design Principles (ncsc.gov.uk)Explain how Zero Trust Network Access (ZTNA) authenticates and authorises every user and device session per application, evaluates device posture continuously and eliminates lateral movement between branch LANs and data centre or cloud workloads.
Protection of OFFICIAL and OFFICIAL-SENSITIVE public sector dataGovernment Security Classifications Policy (GSCP, Cabinet Office, gov.uk)Confirm UK-only data residency for configuration databases, traffic inspection logs, packet captures and DLP quarantine stores, and verify that all personnel with administrative access hold appropriate baseline personnel security standard (BPSS) or Security Check (SC) clearance.
Personal data processing, data subject rights and statutory data protection complianceUK GDPR, Data Protection Act 2018 and Data (Use and Access) Act 2025 (legislation.gov.uk)Provide the UK GDPR Data Processing Addendum, sub-processor register, UK International Data Transfer Agreement (IDTA) status where applicable and technical controls preventing unauthorized export of personal data from inspection nodes.
Information Security Management System (ISMS) scope and independent auditISO/IEC 27001:2022, ISO/IEC 27017 and SOC 2 Type IISupply the ISO/IEC 27001 Statement of Applicability (SoA) and certificate confirming that the specific SD-WAN orchestrator, SASE cloud PoPs and UK managed service desks are within the audited certification boundary.
Health and social care interface assurance for joint council and NHS estatesNHS Data Security and Protection Toolkit (DSPT) and HSCN Consumer Network Service Provider rulesFor authorities with integrated health and social care teams or shared NHS buildings, confirm NHS DSPT "Standards Met" status and compliant routing segregation for HSCN traffic.
Forthcoming statutory supply-chain and managed service provider reporting dutiesUK Cyber Security and Resilience Bill (DSIT legislative programme watch item, gov.uk)Confirm contractual readiness for mandatory 24-hour early warning and 72-hour incident reporting timelines and supply-chain security duties proposed under the UK Cyber Security and Resilience Bill.

For NHS trusts, integrated care boards and joint clinical networks, review our specialist Healthcare SD-WAN and SASE Buyer's Guide.

How the public sector buys: routes and frameworks

Public sector contracting authorities in England, Wales, Scotland and Northern Ireland must procure network and security services through compliant public procurement routes. Following the entry into force of the Procurement Act 2023 (implemented in February 2025 alongside the Procurement Regulations 2024, legislation.gov.uk), contracting authorities operate under a revised statutory regime that replaces the Public Contracts Regulations 2015. The Procurement Act 2023 introduces the Competitive Flexible Procedure alongside the Open Procedure, replaces Most Economically Advantageous Tender (MEAT) with Most Advantageous Tender (MAT) and mandates enhanced lifecycle transparency notices on the central digital platform (Find a Tender).

In practice, the majority of UK central government departments, local authorities, police forces and arm’s-length bodies procure SD-WAN, SASE and underlying WAN connectivity through established Crown Commercial Service (CCS) frameworks (verify current framework lot numbers and expiry dates directly on ccs.gov.uk on your publication date). The two primary CCS routes are Network Services 3 (RM6116) and G-Cloud 14 (RM1557.14). Understanding the structural difference between these two agreements prevents abortive procurement delays and challenge risk.

CCS Network Services 3 (RM6116) is purpose-built for multi-year wide-area networking, data access services, overlay SD-WAN, managed router estates and integrated network security. It supports both direct award (where capability and catalogue pricing are determinable from the framework) and further competition across pre-qualified suppliers, and critically permits multi-year call-off contract terms suited to 36-month or 60-month WAN infrastructure lifecycles. Where a public body is procuring physical access circuits (FTTP, SoGEA, Ethernet leased lines) bundled with managed SD-WAN appliances and SASE licensing under one prime service wrap, Network Services 3 (or its successor iteration on ccs.gov.uk) is typically the primary vehicle.

CCS G-Cloud 14 (RM1557.14) is a catalogue-led framework for cloud hosting (Lot 1), cloud software (Lot 2) and cloud support (Lot 3). Cloud-native Security Service Edge (SSE) subscriptions, ZTNA platforms, SWG licences and cloud-orchestrated SASE software overlays are widely listed on G-Cloud, together with specialist Lot 3 architecture, migration and onboarding support. Buyers using G-Cloud must respect its call-off duration rules (typically an initial term of up to 36 months with defined extension options under G-Cloud 14, verified against the current CCS Buyer’s Guide) and must conduct a structured, auditable search and shortlisting evaluation across the Digital Marketplace catalogue rather than pre-selecting a preferred vendor.

Every public sector SD-WAN and SASE procurement must also incorporate two mandatory policy evaluations. First, under Procurement Policy Note PPN 06/20 (and subsequent National Procurement Policy Statement guidance under the Procurement Act 2023), central government and wider public bodies must apply a minimum 10% evaluation weighting to Social Value, measuring concrete deliverables such as UK cyber apprenticeships, regional digital skills investment or supply-chain decarbonisation tied directly to the contract. Second, technical specifications must align with the CDDO Technology Code of Practice (TCoP, gov.uk/guidance/the-technology-code-of-practice), demonstrating adherence to the Internet First policy, open standards, cloud-first architecture and avoidance of proprietary vendor lock-in.

Operating environment by organisation type

While UK government bodies share a common regulatory baseline, operational network requirements differ markedly across the six main public sector organisation types. Buyers should tailor their SD-WAN and SASE architecture to the specific site profile, user mobility and legacy constraints of their estate.

Central government departments and executive agencies

Central ministries and national executive agencies operate large multi-building campuses, regional civil service hubs and high-security operational facilities alongside thousands of hybrid civil servants. Their primary drivers are GovAssure CAF compliance, strict OFFICIAL-SENSITIVE separation, UK sovereign PoP enforcement, Security Check (SC) cleared support personnel, high-throughput multi-cloud on-ramps into AWS UK (eu-west-2) and Azure UK South / UK West, and automated telemetry feeds into departmental or cross-government protective monitoring SOCs.

Local authorities, unitary and county councils

Local councils manage highly fragmented estates spanning main civic offices, housing and highways depots, libraries, registrars, social care hubs, community centres and schools. IT teams are frequently lean, making zero-touch provisioning (ZTP), co-managed or fully managed NOC support and consolidated single-pane-of-glass orchestration essential. Councils must segment corporate staff, revenues and benefits systems (handling PCI DSS card payments), building management IoT and free public library Wi-Fi across shared physical circuits.

Police forces and fire and rescue services

Blue-light services require continuous 24/7/365 availability across headquarters, custody suites, divisional stations, fire stations and mobile command vehicles. Network architectures must satisfy National Policing Community security standards, support low-latency voice and control-room dispatch systems, bond fixed fibre with dual-SIM 4G and 5G cellular routers for vehicles and rural stations, and enforce strict cryptographic and device-posture controls for officers accessing sensitive operational databases in the field.

Higher education, further education and multi-academy trusts

Universities, colleges and multi-academy school trusts combine high-density student and staff Wi-Fi, research or Jisc Janet connectivity, safeguarding web filtering (aligned with Department for Education Keeping Children Safe in Education statutory guidance) and administrative finance and HR systems. SASE and SD-WAN deployments in education prioritise high-throughput local internet breakout, granular URL and content categorisation, DDoS protection and cost-predictable licensing that scales across large student populations without punitive per-user seat fees.

Arm’s-length bodies, regulators and non-departmental public bodies

Public regulators, inspectorates, museums, research councils and statutory tribunals often operate 3 to 25 UK offices with a predominantly cloud-first SaaS application stack (Microsoft 365, Dynamics, Workday, ServiceNow) and field inspectors working nationwide. These organisations frequently adopt an SSE-first or lightweight SASE architecture: replacing legacy MPLS circuits with dual business FTTP or Ethernet underlays at offices while concentrating investment in ZTNA, CASB, DLP and SWG for their mobile workforce.

NHS trusts, integrated care boards and joint health-care estates

NHS acute, mental health, community and ambulance trusts operate under specialized clinical networking rules, including HSCN peering, NHS Data Security and Protection Toolkit (DSPT) compliance, medical IoT segmentation and sub-50ms latency for picture archiving and communication systems (PACS) and electronic patient records (EPR). Where a local authority shares civic buildings with NHS teams, the SD-WAN must cleanly segregate HSCN and corporate VRFs. For dedicated NHS procurements, read our specialist Healthcare SD-WAN and SASE Buyer’s Guide.

Network performance and resilience

Transitioning public sector sites from MPLS to internet-based SD-WAN underlays requires engineering for deterministic performance rather than best-effort broadband delivery. Under the CDDO Internet First policy, public bodies are encouraged to use business-grade internet connections as their primary WAN transport, relying on application-layer encryption and SD-WAN traffic engineering to deliver enterprise availability. However, raw internet links do not provide end-to-end Quality of Service (QoS) class-of-service markings across carrier peering boundaries.

To protect citizen-facing telephone contact centres, Microsoft Teams voice and video conferencing, remote court or tribunal video links and virtual desktop sessions (Citrix, Azure Virtual Desktop), the SD-WAN platform must perform continuous sub-second path measurement across every active underlay tunnel. The edge appliance must measure one-way latency, jitter and packet loss in real time and execute sub-second application-aware path steering, combined with Forward Error Correction (FEC) and packet duplication for critical voice and real-time streams, whenever an underlying FTTP, SoGEA or Ethernet bearer degrades.

Physical underlay diversity is equally important. Specifying two fibre services that share the same Openreach duct, footway box or local exchange headend creates a single point of physical failure. For Tier-1 civic headquarters, emergency control rooms, contact centres and data centres, buyers should specify physically diverse dual-fibre Ethernet circuits (such as BTnet Diverse+ or dual-carrier tails routed to separate exchange nodes). For Tier-2 and Tier-3 community offices, libraries and depots, pairing a primary FTTP or Ethernet circuit with an active 4G or 5G cellular interface on diverse mobile network operators provides cost-effective survival during street civil-engineering strikes.

Within the SASE cloud layer, performance depends on the geographic distribution and peering architecture of the supplier’s UK Points of Presence. If a vendor routes UK local authority or departmental traffic to inspection PoPs in Frankfurt, Amsterdam or Dublin before breaking out to Microsoft 365 or UK government cloud workloads, round-trip latency increases by 15ms to 35ms and geo-IP localisation rules can break. Buyers should require confirmed active-active UK PoPs (for example in London and Manchester or Slough) with direct private peering into Microsoft, AWS, Google Cloud and UK internet exchanges (LINX, LONAP).

Security architecture: SD-WAN vs SASE vs SSE for the public sector

A frequent cause of scope creep in public sector tenders is conflating SD-WAN, Security Service Edge (SSE) and full SASE. As defined in the Gartner SASE framework (explored in our guide to the Gartner SD-WAN and SASE security model), SD-WAN governs the wide-area network edge, connecting physical buildings, routing packets across multiple transport links and enforcing branch zone segmentation. SSE delivers the cloud-hosted security stack: Zero Trust Network Access (ZTNA), Secure Web Gateway (SWG), Cloud Access Security Broker (CASB), Firewall as a Service (FWaaS) and Data Loss Prevention (DLP). Full SASE converges both the SD-WAN network edge and the SSE security cloud under a unified policy plane and identity context.

For UK public sector organisations, the architectural centre of gravity is Zero Trust Network Access (see our ZTNA glossary definition). Traditional remote-access VPNs place authenticated users onto an internal network subnet, creating broad lateral-movement risk if an endpoint is compromised by ransomware or credential phishing. An NCSC-aligned Zero Trust architecture never grants network-level access. Instead, the ZTNA broker verifies the user’s identity via the authority’s Identity Provider (such as Microsoft Entra ID with phishing-resistant MFA), validates device health and Cyber Essentials patch posture via the endpoint agent, and establishes an encrypted micro-tunnel solely to the specific application the user is authorised to access.

Inside physical civic buildings, network segmentation (see our network segmentation glossary guide) must enforce strict Virtual Routing and Forwarding (VRF) or micro-segmentation boundaries between distinct trust zones. At a minimum, a public sector branch design should isolate: (1) corporate managed endpoints accessing OFFICIAL and OFFICIAL-SENSITIVE systems, (2) payment card terminals or kiosks within PCI DSS scope, (3) building management systems, CCTV, access control and HVAC IoT sensors, (4) partner or visiting agency staff (such as co-located NHS, police or DWP personnel) and (5) unauthenticated citizen public Wi-Fi.

As detailed in our analysis of why modern architecture is SD-WAN and SASE together rather than SD-WAN vs SASE, public bodies do not need to rip and replace both layers on the same day. Many local authorities and executive agencies execute a phased transition: deploying SSE (ZTNA and SWG) first to retire end-of-life VPN appliances and secure hybrid workers within weeks, and then rolling out SD-WAN edge appliances site by site as legacy MPLS and PSN circuit terms expire. Whether procured as a single-vendor converged SASE platform or a dual-vendor SD-WAN plus SSE integration, all security inspection events, DNS queries, blocked threats and ZTNA authentication logs must stream in real time (via syslog, REST API or native connector) into the organisation’s Microsoft Sentinel, Splunk or managed SOC SIEM platform to satisfy NCSC CAF Objective C.

Central government vs local authority and smaller public bodies

Public sector estates span two distinct operational scales. Evaluating suppliers through the lens of your organisation’s scale and internal staffing prevents buying an over-complex platform that your team cannot run or an inflexible managed wrapper that restricts departmental agility.

Central government departments, national agencies and large county/metropolitan authorities

Large public sector estates typically connect 50 to 500+ physical sites and 5,000 to 100,000+ users across multiple directorates or constituent agencies. These buyers require multi-tenant or hierarchical role-based access control (RBAC) so departmental security teams can audit policy without granting global write permissions, dedicated or sovereign UK inspection PoPs, border gateway protocol (BGP) and EVPN integration with core data centres and Crown Hosting, automated Terraform or API policy-as-code pipelines, and formal GovAssure CAF evidence packs backed by SC-cleared UK service management.

Unitary, district and borough councils, blue-light forces and arm’s-length public bodies

Mid-market and smaller public bodies typically operate 5 to 60 sites and 250 to 4,000 users, supported by a small internal infrastructure and cyber team that also manages endpoints, cloud and helpdesk operations. For these buyers, operational simplicity and managed service assurance outweigh bespoke protocol customisation. Priorities include turnkey co-managed or fully managed delivery, rapid zero-touch branch deployment over FTTP and 4G/5G, pre-built NCSC CAF and Cyber Essentials Plus compliance reporting, 24/7 UK SOC alert triage and transparent all-inclusive per-site or per-user subscription pricing suitable for G-Cloud or Network Services budgets.

Government SD-WAN / SASE RFP checklist

A well-structured public sector RFP or framework further-competition specification eliminates ambiguous vendor bids and ensures every supplier prices the same sovereign residency, resilience and support scope. Use the Netify RFP Builder, review our Sample SASE and SD-WAN RFP and draw from the SASE RFP Question Bank to assemble your tender documentation.

The table below sets out the core requirement categories, the mandatory documentary evidence to request from bidders and an indicative evaluation weighting structure aligned with Most Advantageous Tender (MAT) principles under the Procurement Act 2023.

Public sector SD-WAN and SASE RFP evaluation checklist, documentary evidence requests and indicative Most Advantageous Tender (MAT) scoring weights.
Evaluation categoryRequirements to includeEvidence to requestWeight
UK Data Sovereignty, GSCP & NCSC AssuranceUK-hosted inspection PoPs, UK log and metadata storage, NCSC 14 Cloud Security Principles alignment, NCSC CAF v3.2 support, Cyber Essentials Plus and ISO/IEC 27001 scope.Named UK PoP data centre facilities, data-flow diagram showing log and DLP storage locations, current ISO 27001 SoA and Cyber Essentials Plus certificates, and BPSS/SC clearance confirmation for support staff.25%
Zero Trust Security & Multi-Zone Branch SegmentationContinuous posture-checked ZTNA, SWG, CASB, DLP, NGFW and isolated VRFs for corporate OFFICIAL-SENSITIVE, PCI DSS payments, building IoT, partner agencies and citizen Wi-Fi.Reference architecture diagram for a multi-zone civic site, Entra ID / IdP integration walkthrough, and demonstration of per-application ZTNA policy enforcement without subnet exposure.20%
Underlay Diversity, QoS & Real-Time ResilienceSub-second application-aware failover, FEC/packet loss remediation for voice and video, dual-fibre physical diversity at Tier-1 sites and 4G/5G cellular failover at Tier-2/3 sites.Measured failover recovery times for active Teams voice calls, carrier duct-diversity verification process and SLA availability commitments per site tier.15%
Managed Service Operating Model, SIEM & MigrationCo-managed or fully managed 24/7 UK NOC/SOC, real-time SIEM log streaming (Sentinel/Splunk), parallel MPLS/PSN/HSCN migration runbook and zero-touch provisioning.RACI matrix covering change control and incident response, sample migration project plan from a UK public sector deployment and confirmed SIEM connector documentation.15%
Total Cost of Ownership & Licensing Transparency36-month and 60-month pricing schedules covering CPE, SASE/SSE subscriptions, underlay circuits, professional services and rate-card unit costs for adding or closing sites.Completed line-item pricing workbook with zero hidden throughput overage penalties, explicit exit/offboarding fees and framework call-off terms.15%
Social Value & Sustainability (PPN 06/20 / NPPS)Contract-specific UK social value commitments, hardware energy efficiency, circular CPE recycling and supply-chain accessibility.Quantified Social Value method statement with measurable KPIs tied specifically to the call-off contract duration.10%

How Netify scores suppliers

Netify evaluates SD-WAN and SASE suppliers independently using a governed 40-feature capability matrix combined with verified sector and geographic evidence. Every capability claim is graded from primary public documentation, regulatory attestations and published public sector case studies rather than commercial sponsorship, and providers without confirmed UK and Ireland delivery coverage and government sector evidence are excluded from the public sector shortlist.

This buyer’s guide intentionally omits provider rankings so your procurement team can establish vendor-neutral technical and compliance requirements first. When you are ready to compare individual suppliers and their capability scores, view our dedicated government and public sector provider evaluation page.

Open the UK government and public sector provider evaluation list or configure custom technical filters in the interactive shortlist tool.

Frequently asked questions

Does a SASE architecture meet NCSC Cyber Assessment Framework (CAF) expectations?

SASE is an architectural delivery model rather than a certification, so a vendor platform does not make an authority CAF-compliant automatically. However, a properly configured SASE service directly supports core CAF principles: identity-centric Zero Trust Network Access and multi-factor enforcement support Principle B.2 (Identity and Access Control), encrypted overlay transport and DLP support Principle B.3 (Data Security), branch micro-segmentation and NGFW inspection support Principle B.4 (System Security), dual-WAN and multi-PoP failover support Principle B.5 (Resilient Networks and Systems) and centralised telemetry streaming into your SIEM supports Principle C.1 (Security Monitoring). Buyers must still verify that the vendor’s control plane and managed service operations meet the NCSC 14 Cloud Security Principles.

Can internet-underlay SD-WAN carry OFFICIAL and OFFICIAL-SENSITIVE traffic?

Yes, provided the architecture follows NCSC guidance for protecting bulk and sensitive data over untrusted networks. Under the CDDO Internet First policy and the Government Security Classifications Policy (GSCP), OFFICIAL, including OFFICIAL-SENSITIVE, traffic can traverse public internet underlays when protected by NCSC-approved IPSec or TLS encryption profiles, strong mutual device authentication, validated key management and UK-resident security inspection nodes. Where a department handles SECRET or above, separate high-assurance cryptographic and accredited bearer rules apply outside standard commercial SD-WAN.

Which Crown Commercial Service frameworks can public bodies use to buy SD-WAN and SASE?

The two primary CCS routes are Network Services 3 (RM6116) and G-Cloud 14 (RM1557.14), alongside specialist digital and technology frameworks published on ccs.gov.uk. Network Services 3 is typically used when procuring multi-year wide-area network connectivity, physical access circuits (Ethernet, FTTP, SoGEA) and managed SD-WAN infrastructure under a single prime contract or further competition. G-Cloud 14 is widely used for cloud-hosted Security Service Edge (SSE), ZTNA, SWG and SASE software subscriptions (Lot 2) and specialist architecture or migration support (Lot 3). Always check the current framework lot rules and maximum call-off durations on ccs.gov.uk before starting your procurement.

How should councils and agencies handle remaining PSN or HSCN connections during SD-WAN migration?

While the central PSN compliance regime has been superseded by the Internet First policy and modern API-based cross-government data sharing, many local authorities and agencies still maintain specific legacy PSN-connected gateways or co-located NHS HSCN circuits. During migration, your SD-WAN provider should deploy dual-homed gateway routers or data-centre hubs that maintain isolated Virtual Routing and Forwarding (VRF) instances and accredited firewall boundaries for legacy PSN or HSCN subnets, allowing sites to migrate onto SD-WAN incrementally without breaking inter-agency routing. NHS bodies procuring clinical networks should consult our dedicated Healthcare SD-WAN and SASE guide.

Why is UK data residency a critical RFP gate for cloud-delivered SASE?

In a cloud-delivered SASE or SSE platform, user traffic is decrypted and inspected inside the vendor’s Points of Presence, while configuration policies, user identity attributes, DNS logs, firewall event logs and DLP incident captures are stored in the vendor’s management cloud. If a supplier processes traffic in non-UK PoPs or stores management and telemetry logs in US or continental European data centres by default, the contracting authority may breach internal GSCP handling rules for OFFICIAL-SENSITIVE data and incur additional international data transfer obligations under UK GDPR. Your RFP must require contractual confirmation of both UK data-plane PoPs and UK control-plane/log residency.

What should a UK government or local authority SD-WAN and SASE RFP include?

A complete public sector RFP should define: (1) a tiered site inventory detailing postcodes, user headcount, critical applications and existing circuit end dates, (2) mandatory UK data residency, NCSC Cloud Security Principles, NCSC CAF and Cyber Essentials Plus evidence gates, (3) required branch VRF segmentation zones (corporate, PCI DSS payments, building IoT, partner agencies, citizen Wi-Fi), (4) ZTNA and Entra ID integration requirements for hybrid staff, (5) co-managed vs fully managed NOC/SOC responsibilities and SIEM log integration, (6) transparent 36-month and 60-month pricing schedules and (7) PPN 06/20 Social Value deliverables. You can generate a tailored requirements document directly in the Netify RFP Builder.

How we researched this page

This buyer’s guide was written by Harry Yelland and fact-checked by Robert Sturt (Managing Director, Netify Group Limited), with primary references reviewed on 19 November 2026 against published UK government and regulator documentation. Primary sources include the NCSC Cyber Assessment Framework (CAF v3.2) and GovAssure guidance (ncsc.gov.uk and security.gov.uk), the NCSC 14 Cloud Security Principles and Zero Trust Architecture Design Principles (ncsc.gov.uk), the Cabinet Office Government Security Classifications Policy (GSCP, gov.uk), the CDDO Technology Code of Practice and Internet First policy (gov.uk), Crown Commercial Service framework specifications for G-Cloud 14 (RM1557.14) and Network Services 3 (RM6116) (ccs.gov.uk), and the Procurement Act 2023 and Data (Use and Access) Act 2025 (legislation.gov.uk).

In accordance with Netify’s editorial and research methodology, buyer’s guides and ranked supplier evaluations are strictly separated so procurement teams can establish objective requirements before comparing vendors. Supplier capability scores are computed from traceable public evidence records and are never influenced by commercial referral arrangements. Read our full scoring and evidence rules on the Netify methodology page.

Review our scoring framework and source-verification rules on the Netify methodology page.

Related regulated sectors: Healthcare & NHS · Energy & Utilities · Financial Services · Manufacturing · Retail