Versa Networks

In this model Versa NOC is responsible for managing and maintaining Versa SASE, while the customer IT team is responsible for management and monitoring of the CPEs. Versa does operate a NOC and a hosted, managed head-end and gateway service under its own SLA, so part of the estate is genuinely run by Versa. But its own solution brief places CPE management with the customer IT team in that model, and the alternative model places configuration management and monitoring with a Service Provider. End-to-end design, deploy, change, support and report by Versa itself for the whole service is not evidenced, so partial rather than yes.

In this model Versa NOC is responsible for managing and maintaining Versa SASE, while the customer IT team is responsible for management and monitoring of the CPEs. This is a textbook split of responsibility: Versa runs the platform and the customer retains CPE operations. Concerto's provider-level and tenant-level roles document the same shared model in the tooling.

Head-end server hardware OS and security patch upgrades and updates For the hosted head-end, Versa documents software upgrades of Director, Analytics, Controller, Concerto and VMS plus OS and security patching, which is lifecycle handled as part of the service. Separately, hardware documentation covers a two-year limited warranty, next-business-day and same-business-day advance replacement, DOA handling and an end-of-life policy. Graded partial rather than yes because branch CPE firmware upgrades and renewals in a typical Versa deployment sit with the customer or the service provider partner, and hardware replacement coverage is a purchased support tier rather than something evidenced as included in the service by default.

Native, per-application SLA-based routing confirmed specifically via the Adobe deployment [19]

The term WWAN interfaces refers to LTE, 4G, and 5G interfaces. Documentation covers LTE, 4G and 5G on a VOS WAN port, SIM activation and operator ID checks, and radio quality monitoring via RSRP, RSRQ, RSSI and SINR with banded signal states. It is documented as usable where a branch has no wired connection and alongside wired links, so both primary and failover roles are covered. On the source page the words WWAN interfaces are italicised; the italics add no characters to the rendered text.

Native - confirmed explicitly for AWS-hosted VOS deployment, described as 'cloud edge deployment such as AWS running VOS' [24]

Versa Cloud Gateways (VCGs) are Versa SASE Gateways which are deployed in Point of Presence (PoP) locations around the world. These are Versa's own gateways running Versa's own VOS software, not a third party's PoPs resold under Versa's name, so yes rather than partner_integrated. They deliver secure internet access, ZTNA, threat protection and DLP as a cloud service, and the SASE client selects the VCG offering lowest latency.

Versa SASE is delivered via the cloud, on-premises, or as a blended combination of both Versa markets Private SASE and Sovereign SASE as distinct deployment models alongside the shared cloud. Network World, a named-author dated source, reports that Sovereign SASE runs entirely on customer-controlled infrastructure with the customer choosing its own compute, on-premises or in a private cloud. Confidence is medium rather than high because the Sovereign SASE product page itself would not render without JavaScript, so the strongest Tier 1 statement of the claim could not be read directly.

Versa SD-WAN Traffic Engineered network which uses multiple global and regional providers for the underlay. Inter-gateway traffic rides a Versa-controlled traffic-engineered overlay that selects paths on least end-to-end latency and loss, and each VCG is connected to multiple global and multiple regional service providers with peering relationships. But the underlay is explicitly other carriers' capacity, not fibre or circuits owned by Versa. Graded partial: the control plane and path selection are Versa's, the physical backbone is not.

Native - Versa-certified white-box routers (third-party hardware running VOS) confirmed specifically via the Adobe deployment account; branch edge devices, cloud edge deployment, and on-premises appliances all confirmed as supported form factors [24]

Native, confirmed at a specific, quantified level via the Adobe case study - 'four-nines of availability for critical services' was an explicit deployment requirement Versa was chosen to meet [18]

target Uptime average of 99.999% ("Uptime SLA Percentage") measured monthly A published, dated SLA document covering Versa Hosted and Managed Secure Services Edge Gateways, with a tiered service-credit table running from 2 days of credit for uptime below 99.999% up to 24 days below 98.0%, plus a security processing latency commitment of 10ms without TLS inspection and 50ms with anti-virus, malware detection and IPS with TLS decryption. Contractual rather than best-effort, including a two calendar day claim window.

Data loss prevention (DLP) is a set of tools and processes for detecting and preventing data breaches, cyber exfiltration, and unwanted destruction of sensitive data. Native to the platform and configured from Concerto. Content passing through the organisation's ports and protocols is scanned against match rules, with enforcement actions of Alert, Allow, Block, Reject, Quarantine, Encrypt, Redact or Tokenize, and all actions reported to Versa Analytics for review. Documentation also covers offline DLP, DLP data exfiltration policies and applying Microsoft MIP sensitivity labels.

Native, confirmed and well-evidenced via Versa Analytics' specific, itemised log-type list (flow logs, SD-WAN path and bandwidth usage, CGNAT, DHCP, DNS, SASE-web monitoring, secure access, traffic conditioning, URL filtering, and IDP logs) and confirmed export to CrowdStrike Falcon Next-Gen SIEM [26] Not confirmed

Native, confirmed via a named practitioner review describing the console's 'ZTP (zero touch provisioning)' capability speeding up implementation [7]

Versa will provide Root-Cause Analysis for customer-reported P1 issues. The NOC half is evidenced: 24x7 monitoring of head-end alarms and application health, a Versa NOC responsible for managing and maintaining Versa SASE, formal root cause analysis on P1 incidents, and scheduled periodic or quarterly customer review meetings. What I did not find on any page I read is a 24x7 SOC performing proactive security monitoring on the customer's behalf, nor a documented change governance process. Graded partial on that gap. Note also that the Premier Service datasheet carries a 2020 copyright.