Scope
Cato continuously develops, enhances, and improves the capabilities of its products, including through new Socket software releases. Each Socket software release has a defined Product Support Period and, as newer releases are made available to customers, ultimately reaches End of Support (EOS). This policy provides customers and partners with guidance on the milestones and timeframes associated with the Socket software support lifecycle. It is intended to help customers plan and successfully transition to supported releases.
Cato Socket
Cato Sockets are customer-premises edge devices that connect customer sites to the Cato Cloud, enabling SD-WAN connectivity, traffic forwarding, and centralized policy enforcement. A Socket serves as the connection point between the customer LAN and the Cato Cloud and supports bidirectional traffic for internet, SaaS, and internal application access.
Cato Sockets may be deployed as physical appliances at customer sites or as virtual appliances, known as vSockets, in public or private cloud environments. In this policy, “Socket software” means the software running on both physical Sockets and vSockets. This policy applies only to Socket software releases and does not govern the lifecycle or end of support of physical Socket hardware. For the hardware policy, see the Cato Socket Hardware Refresh Policy.
Software release lifecycle
Cato Socket software follows a lifecycle based on the major release. The key milestones are General Availability (GA), the Product Support Period, and End of Support (EOS).
Milestone | Timeframe | Description |
|---|---|---|
General Availability (GA) | Start of the lifecycle | The major release becomes generally available to customers, and Product Support begins. |
Product Support Period | 12 calendar months from GA | Cato provides issue investigation and troubleshooting under the applicable support terms. New capabilities, enhancements, fixes, patches, and security updates may be provided. Compatibility with current Cato Cloud capabilities is maintained, subject to product requirements. |
End of Support (EOS) | At the end of the Product Support Period | Product Support ends for the major release and all of its minor releases, including troubleshooting, issue investigation, fixes, patches, and security updates. The release may not remain compatible with future Cato Cloud capabilities |
EOS schedule and notification
Under the standard lifecycle, Cato publishes a major release’s EOS date at least six months before EOS. Each major release has its own dedicated software lifecycle, and the availability of another software release does not, by itself, change a major release’s lifecycle or EOS date. Cato may shorten the software lifecycle because of a critical security vulnerability, material stability or service-integrity risk, third-party or operating-system end-of-life, regulatory requirements, or another condition that materially puts the Cato platform or service at risk. In these circumstances, the notice period may be shorter.
Software release types
Cato Socket software includes major and minor releases. The support lifecycle and EOS date are established at the major-release level.
Major releases
A major release is a family of Socket software identified by its major release number (for example, v27). It may introduce significant security, networking, architectural, functional, or compatibility changes and improvements.
Minor releases
A minor release is an update within a major release (for example, v27.1). It may include bug or security fixes, stability or performance improvements, compatibility changes, new capabilities, or feature enhancements. References to minor releases include maintenance releases and builds.
Minor releases do not have independent support periods or EOS dates. They inherit the EOS date of their major release, even if they become available later in the Product Support Period. A minor release does not restart the support clock.
Software Upgrades
Cato recommends running the latest supported major release available to the customer’s account. By default, customers are automatically upgraded when a new Socket software release becomes available to their account. A release’s lifecycle is measured from its GA date, irrespective of its deployment to or availability for a specific account.
During Product Support, Cato may require an update to a designated minor release or an upgrade to a newer supported major release to reproduce, investigate, or resolve an issue, address a security or stability risk, or maintain compatibility.
Customers that pause automatic upgrades should monitor the published EOS date and complete an upgrade before the cutoff. After EOS, customers must upgrade to a supported major release before Cato can resume Product Support. EOS alone does not trigger a forced upgrade, but Cato may require or enforce an upgrade when continued operation creates a material security risk or threatens service integrity.
Disclaimer
This policy should be read together with the customer’s applicable Cato Networks Master Service Agreement (MSA) and support terms. It supplements and does not amend the parties’ contractual obligations or remedies. EOS applies to Product Support for the affected Socket software release and does not, by itself, terminate the customer’s subscription or Cato Cloud service.
FAQ
How long is a major release of Socket software supported?
Under the standard lifecycle, a major release receives 12 calendar months of Product Support from its GA date. Always refer to the latest official release-lifecycle notice for the applicable EOS date.
How do I know whether my Socket software release is supported?
Check the major release’s published GA and EOS dates. Product Support is available from GA until the EOS date. Updates or upgrades may be required for support purposes as recommended by Cato
What happens when my release reaches EOS?
Product Support ends for the affected Socket software release, including troubleshooting, issue investigation, fixes, patches, and security updates. Upgrade to a supported major release to receive Product Support under the applicable support terms.
Is there a grace period after Product Support ends?
No. The published EOS cutoff is the end of Product Support. There is no separate grace period, additional support phase, or option to extend support.
Does Cato support every minor release or build within a supported major release?
Minor releases and builds share their major release’s EOS date. Support is provided at the major-release level. Cato may require an update to a designated minor release or an upgrade to a newer supported major release.
Does a minor release restart the Support clock?
No. A minor release or build inherits the major release’s EOS date, even if it becomes available later in the Product Support period.
How often does Cato issue a new major release of Socket software?
The support lifecycle does not depend on a fixed major-release cadence. A newer major release does not change an older major release’s EOS date. Each major release follows the standard 12-calendar-month lifecycle.
Will Cato force an upgrade when a release reaches EOS?
EOS alone does not trigger a forced upgrade. Cato may require or enforce an upgrade when continued operation creates a material security risk or threatens service integrity.
How will I know when I need to upgrade?
Monitor official Cato release-lifecycle notices for the major release’s EOS date. Standard EOS dates are published at least six months in advance; Keep automatic upgrades enabled or complete an upgrade before the EOS date.
Does automatic rollout change my release’s EOS date?
No. The lifecycle is based on the major release’s GA date, not the date it reaches an individual account or Socket. Customers should verify that upgrades complete successfully before EOS.