BT Business / BT Global - Managed SASE - Netify Knowledge Profile
Research updates
Checked 23 October 2026. These sourced updates are separate from Harry Yelland's original profile, preserved in full below. Platform documentation describes technology support; the BT order determines service inclusion.
Fortinet launch date
BT announcement
BT announced the UK Fortinet managed SASE expansion on 25 November 2024.
Announcement date
International SSE choices
BT International
The 14 October 2026 announcement names Cisco, Fortinet, Netskope and Zscaler SSE connectivity through Global Fabric. This is an International offer, not a universal UK package.
Announcement and notes to editors
Data loss prevention
BT published service description
BT now names DLP for cloud applications, including M365.
Converged threat detection and prevention
Operations and reporting
BT published service description
BT names unified incident response, quarterly business reviews, a unified dashboard, custom reporting, anomaly detection and auto-remediation. These marketing claims do not establish each ordered package or its response targets.
End-to-end SASE managed by BT
UK logging
BT published service description
BT describes UK-resident logging and management. Retention, export permissions and the contracted processing scope need agreement.
Converged threat detection and prevention
Remote access and DNS
BT FortiSASE
The BT FortiSASE schedule names FortiClient, DNS security, CASB and private-application ZTNA.
Part B 1.1.2, 1.1.5-1.1.7; 3.1.1
Digital experience monitoring
BT FortiSASE option
DEM is orderable with an additional licence.
Part B 1.1.9
Customer access and changes
BT FortiSASE
Portal monitoring and reports require co-management. Permitted commands are agreed; BT disclaims losses from customer changes. Five simple service requests per year are included.
Part B 1.1.3; 2.2; 3.2; 8.1
Licence duration
BT FortiSASE
Licences may cover the service term or a minimum year with yearly renewals. BT manages the subscriptions.
Part B 1.1.10
Service-edge locations
BT FortiSASE
Specific PoPs are agreed for customer requirements; the schedule supplies no fixed worldwide count.
Part B 1.1.1
Physical, virtual and LAN options
BT Fortinet SD-WAN
BT specifies physical and virtual edges, optional cloud deployment, switches, Wi-Fi access points and LAN CPE. Exact models remain order-specific.
Part B 1.1; 2.1; 2.4; 2.8
4G and 5G underlay
BT Fortinet SD-WAN option
UK mobile options include 4G and 5G. Active-active mobile access requires available 5G.
Part B 2.3
Application and site visibility
BT Fortinet SD-WAN
Co-management provides FortiManager/FortiAnalyzer visibility; write access needs permission. The customer portal monitors network status and generates reports.
Part B 1.6; 2.2
Protective monitoring
BT Fortinet SD-WAN option
Optional protective monitoring handles high/critical events continuously and uses agreed response playbooks. It is separate from security licensing.
Part B 2.5-2.6
Hardware maintenance
BT Fortinet SD-WAN
BT maintains and, where applicable, replaces BT-owned SD-WAN edge devices.
Part B 7.2.2
Bandwidth and user licences
BT Fortinet SD-WAN option
FortiSASE add-ons include bandwidth, public IP and remote-user licences. No public unit price is stated.
Part B 2.7.1
Contracted service levels
BT FortiSASE contract
BT FortiSASE Part A gives on-time delivery a service level; availability and incident resolution have targets. This differs from other BT service schedules.
Part A 13.2-14
Commitments and renewal
BT FortiSASE contract
Charges and volume commitments are set in the order. Renewal requests are described at least 90 days before expiry; renewal needs an order. Reconfiguration and out-of-hours work can incur extra charges.
Part A 10-11
China availability
BT FortiSASE contract
The schedule addresses China restrictions; this does not establish universal availability or a named local PoP.
Part A 9
Incident and change management
BT management schedule
STANDARD defines incident ownership, escalation, diagnosis, restoration and controlled changes. The applicable management schedule is identified in the order.
STANDARD sections 4-12, 18-21; schedule index
Service reviews and reporting
BT management option
PLUS describes monthly performance reports and service management. Applicable options must be purchased and listed in the order.
PLUS sections 9-11, 14-15; schedule index
SOC 2 report access
BT assurance process
BT offers its SOC 2 report to customers and prospects under NDA. Request the report and check the exact service, legal entity, audit period and exceptions. The public page does not establish SASE-specific scope.
SOC2 Assurance
Browser access for contractors
Underlying platform, not BT inclusion
FortiSASE documents browser-only access to private HTTPS applications for contractors and temporary workers. BT orderability and application scope still need confirmation.
Agentless ZTNA; subscription prerequisites
Mobile clients
Underlying platform, not BT inclusion
FortiSASE lists Android and iOS clients alongside Windows and macOS. BT must confirm supported versions and feature parity for the chosen service.
Product integration and support
API-based CASB
Underlying platform, not BT inclusion
Fortinet documents out-of-band CASB for AWS S3, Google Cloud Storage and Office 365, with licence prerequisites. This does not prove inclusion in a BT order.
API-based CASB prerequisites
Browser isolation
Underlying platform, not BT inclusion
FortiSASE RBI is a select-availability feature, disabled by default where not already enabled. It requires an eligible subscription, proxy and Fortinet PoP. BT availability must be agreed.
RBI availability and prerequisites
Identity integration
Underlying platform, not BT inclusion
FortiSASE documents Entra ID, Okta, LDAP and RADIUS authentication. BT configuration and support responsibilities remain order-specific.
Access and authentication
Multiple identity providers
Underlying platform, not BT inclusion
FortiAuthenticator can proxy employee and contractor identities from Entra ID, Google Workspace or Okta. Its inclusion in BT service scope needs agreement.
Identity-provider proxy example
User provisioning
Underlying platform, not BT inclusion
FortiSASE documents SCIM provisioning with eligibility and instance restrictions. SAML support does not itself prove OIDC support. BT must confirm instance eligibility and enabled protocols.
SCIM server support prerequisites
External log export
Underlying platform, not BT inclusion
FortiSASE supports external FortiAnalyzer, Syslog and CEF forwarding, including DLP, security and administrative events. This is not evidence of a ready-made Sentinel or Splunk integration or BT-granted export access.
Forwarding logs to an external server
Loss protection
Underlying platform, not BT inclusion
FortiGate supports forward error correction and packet duplication. Firmware, design and BT support scope need matching before procurement.
SD-WAN architecture guides
AI assistant and reports
Underlying platform, not BT inclusion
FortiAnalyzer FortiAI supports natural-language queries, report generation and configuration assistance with its own licence. BT has not been shown to include that licence or customer access.
FortiAI capabilities and licence
Zero-touch Wi-Fi deployment
BT published component description
BT names zero-touch deployment for FortiAP. This is specific to Wi-Fi access points and does not prove a universal zero-touch branch workflow.
Notes to editors, FortiAP
Manufacturing experience
Sector experience, not product proof
BT publishes manufacturing case studies and links to its SD-WAN/SASE portfolio. These references do not establish a named Fortinet SASE manufacturing deployment.
Manufacturing case-study directory
ServiceNow orchestration
BT published transformation description
BT describes ServiceNow digital service apps for SASE-controller orchestration. A customer-facing ServiceNow connector, entitlement and workflow scope still need agreement.
Automation and orchestration
Separate security products
Separate BT offers
BT lists Managed CrowdStrike, Managed CySOC for Splunk and multiple cloud-security offers separately. Their presence in the catalogue does not establish integration or inclusion in BT FortiSASE.
Security service schedule list
Satellite scope
Different BT service
BT and Starlink announced consumer broadband and mobile-backhaul uses. This does not establish a managed SASE satellite option. Ask BT for the enterprise offer and support boundary.
Consumer announcement scope
Questions for BT
26 items need service-specific evidence
Public sources reviewed have not settled these points. They are procurement questions, not findings that BT lacks the capability.
- SaaS security posture
- Please identify the ordered product, licence and supported configuration for SaaS security posture, with a service-document reference.
- VDI environments
- Please confirm supported devices, applications, enrolment requirements and licence scope for VDI environments.
- Privileged access
- Please confirm supported devices, applications, enrolment requirements and licence scope for Privileged access.
- Middle East coverage
- Please provide the country/location list, regulatory restrictions and contracted delivery scope for Middle East coverage.
- Africa coverage
- Please provide the country/location list, regulatory restrictions and contracted delivery scope for Africa coverage.
- Latin America coverage
- Please provide the country/location list, regulatory restrictions and contracted delivery scope for Latin America coverage.
- Sovereign/regional service options
- Please provide the country/location list, regulatory restrictions and contracted delivery scope for Sovereign/regional service options.
- Role-based administration
- Please demonstrate Role-based administration and specify customer permissions, change controls and any additional charge.
- Multi-tenancy
- Please demonstrate Multi-tenancy and specify customer permissions, change controls and any additional charge.
- User/entity behaviour analytics
- Please identify the product/version, licence, customer access and BT support scope for User/entity behaviour analytics.
- Generative AI application controls
- Please identify the product/version, licence, customer access and BT support scope for Generative AI application controls.
- AI data protection controls
- Please identify the product/version, licence, customer access and BT support scope for AI data protection controls.
- VMware (historical)
- Please provide the supported connector or protocol, data flow, licence and responsibility split for VMware (historical).
- AWS
- Please provide the supported connector or protocol, data flow, licence and responsibility split for AWS.
- Microsoft Azure
- Please provide the supported connector or protocol, data flow, licence and responsibility split for Microsoft Azure.
- Google Cloud
- Please provide the supported connector or protocol, data flow, licence and responsibility split for Google Cloud.
- Microsoft Defender
- Please provide the supported connector or protocol, data flow, licence and responsibility split for Microsoft Defender.
- Nokia
- Please provide the supported connector or protocol, data flow, licence and responsibility split for Nokia.
- REST API
- Please provide the supported connector or protocol, data flow, licence and responsibility split for REST API.
- PCI DSS
- Please provide the service-specific assurance documentation and contractual scope for PCI DSS.
- GDPR
- Please provide the service-specific assurance documentation and contractual scope for GDPR.
- NIS2 relevance
- Please provide the service-specific assurance documentation and contractual scope for NIS2 relevance.
- DORA relevance
- Please provide the service-specific assurance documentation and contractual scope for DORA relevance.
- Financial services
- Please provide a named, product-specific deployment reference for Financial services.
- Retail
- Please provide a named, product-specific deployment reference for Retail.
- Mid-market
- Please provide a comparable deployment and explain service fit, scale and support scope for Mid-market.
Netify Overview: BT Business / BT Global Managed SASE
BT is not a single-platform SASE company, but the UK’s largest telecommunications operator and managed service provider, delivering SASE as one service line within a vastly larger, publicly-listed (LSE: BT.A) group. For FY2026 (year ended 31 March 2026), BT Group reported revenue of £19.7 billion, adjusted EBITDA of £8.2 billion, and profit before tax of £1.4 billion - a large corporate scale, reflecting BT’s identity as a diversified national telecommunications operator rather than a standalone SASE vendor. BT’s SASE proposition is delivered under its own named managed-connectivity brand, Agile Connect, and is explicitly multi-platform rather than built on a single, proprietary technology stack: BT’s own materials and Netify’s own published research confirm managed SD-WAN delivered on Cisco Meraki and Versa, with managed SASE delivered on Fortinet and Meraki, reinforced by BT’s own Managed Detection and Response service. The current, Fortinet-based managed SASE offering - adding firewall-as-a-service, secure web gateway, cloud access security broker and zero-trust network access on top of BT’s existing managed SD-WAN - launched in its most recent expanded form in late 2025, following an earlier, distinct managed SASE service built on VMware technology that BT brought to market in January 2022. Buyers researching BT’s SASE history should understand these as two different underlying technology generations rather than a single, continuous product. BT’s core differentiator is not a proprietary SASE architecture but infrastructural depth: Openreach, BT’s wholly-owned but operationally separate access-network subsidiary (established 2006 under Ofcom/Enterprise Act 2002 undertakings), gives BT direct control over one of the deepest last-mile access estates in the UK market, combined with BT’s own international core network and long-established BT Security division. Evidence quality here differs in character from many pure-play SASE vendors: no fully-named, quantified customer success story with an identified company was found, though a real, detailed, primary-sourced case study describes an anonymised global financial-services customer’s deployment of Agile Connect with BT Managed Fortinet Firewall. Commercially, BT’s SASE offering is confirmed as quote-based with no published enterprise pricing, and buyers should confirm directly which specific underlying vendor platform (Fortinet, Meraki, or otherwise) is being proposed for their specific deployment, since BT’s own positioning is explicit that platform choice and packaging vary by customer.
Core Architecture & Key Differentiators
BT's SASE architecture reflects its identity as a large, diversified telecommunications operator and systems integrator rather than a single-platform technology company: the differentiators are infrastructural and operational, not proprietary software.
Genuine, owned last-mile and core network depth via Openreach.
Netify's own published capability research on BT specifically confirms 'Openreach-adjacent last mile, owned core, and global reach through BT's international network' with 'dual-hub and diverse last-mile designs' as standard practise for resilience - a specific, structural advantage rooted in BT's ownership of Openreach rather than a SASE-platform feature.
A confirmed, deliberately multi-platform technology strategy.
Rather than committing to one SASE vendor, BT offers managed SD-WAN on Cisco Meraki and Versa, and managed SASE on Fortinet and Meraki, giving buyers genuine platform choice within a single managed-service contract - though this also means buyers must confirm exactly which platform is being proposed for their specific requirement, since capability and packaging vary between them.
Sector-specific SASE positioning with named, concrete use cases.
BT's own current SASE materials describe specific, named sector applications rather than generic capability claims - for retail, 'elastic SD-WAN and CASB to dynamically steer traffic and safeguard payment and customer data' during seasonal surges and pop-up environments; for financial services, ZTNA-based identity-first access with data residency support 'by keeping sensitive traffic within localised data paths'.
Where BT Managed SASE Stands Out vs Where It Falls Short
Evaluation Area | Strengths & Differentiators | Weaknesses & Watch-Outs |
|---|---|---|
| ||
| ||
| ||
| ||
| ||
Suitability Matrix: Who Should (and Shouldn't) Buy BT Managed SASE
Recommended for:
UK-headquartered or UK-anchored organisations wanting genuine underlay accountability and field-engineering depth alongside SD-WAN and SASE delivery, given BT's confirmed ownership of Openreach; public-sector and NHS-adjacent buyers specifically, given confirmed HSCN accreditation; and buyers wanting a single managed contract combining connectivity, hardware, and a choice of underlying SASE platform rather than separately procuring each element.
Look elsewhere if:
you want a fully self-managed, do-it-yourself platform, given BT's own confirmed positioning that this is not its primary delivery model; you need platform-specific compliance certifications (FedRAMP, an independently-confirmed ISO 27001 or SOC 2 for the SASE service itself) that this research pass could not confirm; or you want a single, proprietary, vendor-owned SASE architecture rather than a multi-platform managed-service model where the specific underlying technology varies by proposal.
Netify Buyer Checklist: Questions for BT
Before placing BT Managed SASE on a shortlist, it's worth getting clear answers to the following, ideally in writing rather than taken on trust from a slide.
On platform choice specifically:
exactly which underlying SASE platform (Fortinet or Meraki) is being proposed for this deployment, and why was it selected over the alternative?
On the co-managed model:
what does the RACI split actually look like in practise, and can BT provide a live portal demonstration showing exactly what visibility and control the customer retains directly?
On compliance:
beyond the confirmed HSCN accreditation, does the specific SASE service itself carry any independently-verified certifications (ISO 27001, SOC 2, or equivalent), distinct from BT Group's broader corporate compliance posture?
And on migration history:
given BT has offered managed SASE under at least two different underlying technology generations (VMware from 2022, Fortinet from 2024-2025), what is the current status of any legacy VMware-based deployments, and what would a migration path to the current platform look like for an existing customer?
Research tables and sources
Table 1 - Entity Identity and Market Position
Field | Required data |
|---|---|
| |
| |
| |
| |
| |
| |
| |
Table 2 - Product and Service Portfolio
Product/service | Category | Current name/version | Native or partner | Target buyer | Delivery model | Source | Last verified |
|---|---|---|---|---|---|---|---|
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
Table 3 - Core SASE, SSE and SD-WAN Feature Matrix
BT's SASE capability is delivered via named third-party platforms (principally Fortinet, with a Meraki-based alternative) rather than proprietary BT technology - several rows below reflect capabilities of the underlying platform as implemented and managed by BT, not a BT-built security stack.
Capability | Availability | Product/module | Included or add-on | Deployment options | Key limitations | Evidence | Confidence | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 4 - SD-WAN and Branch Capability
Data point | Finding | Evidence | Confidence | Netify View |
|---|---|---|---|---|
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
Table 5 - Remote User, Mobile and BYOD Support
Use case | Supported | Method/client | Operating systems | Identity/device requirements | User experience controls | Limitations | Netify View |
|---|---|---|---|---|---|---|---|
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
Table 6 - Architecture and Deployment Models
Deployment model | Supported | Components required | Traffic path | Policy location | Typical use case | Complexity | Migration notes | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 7 - Global Platform and Service Coverage
Data point | Verified finding | Direct or partner | Regions/countries | Limitations | Evidence date | Confidence | Netify View |
|---|---|---|---|---|---|---|---|
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
Table 8 - NOC, SOC, Support and Managed Operations
Operational capability | Availability | Hours | Locations/coverage | Included or premium | Customer responsibility | Escalation/SLA | Evidence | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 9 - Configuration, Administration and Operating Effort
Area | How it works | Primary interface | Skills required | Automation available | Operational effort | Known friction | Evidence | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 10 - Reporting, Statistics and Visibility
Capability | Available | Audience | Real time or historical | Retention | Export/API | Customisation | Limitations | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 11 - AI, Machine Learning and Automation
BT's confirmed AI investment is framed around threat detection specifically, layered on top of whichever underlying vendor platform (Fortinet or Meraki) is proposed - evidence in this table reflects BT's own positioning rather than a single, BT-built AI product.
Feature | Specific function | Input data | Output/action | Human approval required | GA or preview | Evidence | Practical value | Limitations | Netify View |
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
| |||||||||
Table 12 - Integrations and Ecosystem
Integration | Category | Native/certified/API/partner | Direction of data flow | Required licence | Implementation notes | Evidence | Confidence | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 13 - Security, Compliance and Data Sovereignty
This research pass found strong evidence of BT's own confirmed regulatory accreditations relevant to its network operations (HSCN), but no independently-confirmed, SASE-service-specific certifications (ISO 27001, SOC 2, FedRAMP) distinct from BT Group's much broader, larger corporate compliance posture.
Standard/requirement | Status | Scope | Certification or supporting capability | Region restrictions | Evidence | Last verified | Netify View |
|---|---|---|---|---|---|---|---|
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
Table 14 - Sector Suitability
BT's own current SASE materials name specific sectors directly with concrete, sector-relevant capability claims - genuinely stronger evidence than a generic sector list, even without individually-named customer case studies for most sectors.
Sector | Suitability | Relevant capabilities | Relevant compliance | Supporting case studies | Service/coverage considerations | Limitations | Netify View |
|---|---|---|---|---|---|---|---|
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
Table 15 - Organisation and Estate Suitability
Buyer profile | Suitability | Why | Operational prerequisites | Commercial considerations | Evidence | Netify View |
|---|---|---|---|---|---|---|
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
Table 16 - Commercial and Licensing Data
No pricing has been published for BT's managed SASE service in any source found in this research pass - Netify's own independent research explicitly confirms this is 'Quote-based. No complete public enterprise price was found in reviewed sources.'
Commercial field | Finding | Publicly disclosed | Variables/drivers | Buyer questions | Evidence | Confidence | Netify View |
|---|---|---|---|---|---|---|---|
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
| |||||||
Table 17 - Deployment and Migration Evidence
Scenario | Typical sequence | Dependencies | Customer resources | Provider resources | Time evidence if public | Risks | Mitigations | Netify View |
|---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
| ||||||||
Table 18 - Structured Customer Case Studies
One real, detailed, primary-sourced case study was found in this research pass. The customer's own identity is anonymised - a common, standard practise for this class of content - but the technical and business narrative is genuinely specific and credible. No fully-named, individually-identified customer case study was found for BT's managed SD-WAN or SASE services in this research pass, a real, worth-flagging gap Netify should prioritise closing directly with BT.
Case study | Customer/anonymous | Sector | Country/region | Users | Sites | Problem | Products/services | Deployment model | Integrations | Measured outcomes | Evidence quality | Netify interpretation |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Table 19 - Strengths, Limitations and Procurement Watch-outs
Type | Finding | Buyer impact | Best/worst affected buyers | Evidence | Confidence | Netify View |
|---|---|---|---|---|---|---|
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
Table 20 - Netify Human Evaluation
First six rows are the mandatory Netify Assessment questions and are answered explicitly here.
Evaluation area | Netify conclusion | Evidence basis | Confidence | Buyer implication |
|---|---|---|---|---|
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
Evidence Register
Every source used in this profile, numbered, with a reliability tier (see "Source reliability tiers" below). Each [n] superscript throughout the tables above is a clickable link that jumps to the matching numbered row here - right-click the number and choose "Update Field" if Word doesn't show it as a live link immediately after opening. Sources kept at Tier 4 are NOT relied on for any factual claim in this profile; they're retained here only for audit-trail transparency.
# | Tier | Source title/document | URL | Pub. date | Verified | Confidence / reliability note |
|---|---|---|---|---|---|---|
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
| ||||||
Source reliability tiers
- Tier 1 - Primary (BT / regulatory registry) -
- BT's own site (BT Newsroom, BT Business, BT case studies), plus a primary, regulatory-filed (RNS) BT Group financial announcement. Used freely as evidence.
- Tier 2 - Authoritative third-party -
- Named, editorially-independent trade-press outlets with original reporting (Comms Business, Computer Weekly). Used freely as evidence.
- Tier 3 - Secondary (corroboration only) -
- Netify's own dated, structured, independent comparative research (netify.co.uk and sase.netify.co.uk - treated with the same evidentiary standard applied to any other independent comparison platform in this profile series), company-data aggregators (Umbrex, PitchBook, ZoomInfo, Forbes, GlobalData), and Wikipedia's Openreach entry (used narrowly, only for specific facts cross-checked against other sources). Used only to corroborate, never as sole evidence for a claim that materially affects a buyer recommendation.
- Tier 4 - Not used as evidence -
- Wikipedia's BT Group entry specifically. Not cited as support for any factual claim in this profile; retained in the register only for audit-trail transparency about what was found and consciously not relied on, replaced instead by primary BT sources and independent corroboration.
Reference Architecture / Deployment Diagram Description
Typical BT Managed SASE deployment flow, suitable for later visual production:
- (1) At each site, customer-premises equipment (included within BT's confirmed managed commercial model) connects via a customer-selected mix of underlays - BT's own confirmed 'flexibility to mix different connectivity options for each of their sites' - with dual-hub and diverse last-mile designs applied as standard practise for resilience.
- (2) Wherever the UK last mile is involved, that connectivity runs over BT's own directly-owned Openreach access network, giving BT genuine, first-party accountability across the entire path rather than depending on a separate, third-party-owned local loop.
- (3) Traffic is elastically, dynamically steered by the managed SD-WAN layer (Agile Connect, delivered on Cisco Meraki or Versa) and prioritised to a SASE cloud node, avoiding public internet congestion for prioritised traffic.
- (4) At the SASE cloud node, the customer's chosen underlying platform - currently and predominantly Fortinet, with Meraki as a confirmed alternative - delivers firewall-as-a-service, secure web gateway, cloud access security broker, and zero-trust network access, with identity-based ZTNA access confirmed to support data-residency requirements by keeping sensitive traffic within localised data paths for regulated-sector customers specifically.
- (5) Network segmentation is applied throughout, confirmed directly via a real customer account, so that a breach in one area does not compromise data in other areas.
- (6) BT Security provides round-the-clock monitoring, AI-powered proactive threat detection, and Managed Detection and Response, feeding into BT's own confirmed unified monitoring services and giving customers centralised visibility and control across their entire infrastructure and security posture.
- (7) The whole estate is managed by BT by default under a single commercial contract combining access, CPE, and the chosen vendor stack together, with a confirmed co-managed option available for buyers wanting more direct operational involvement, subject to a RACI split that should be confirmed directly rather than assumed.