This article explains how Cato communicates new features and updates to the Cato service.
Cato regularly releases new content to production in the Cato Cloud. To ensure that you are informed and up-to-date with new content, we communicate changes and additions through weekly Product Update emails (release notes).
Note: When Cato Management Application (CMA) admins are deleted, they are not unsubscribed from Product Update emails. They need to manually unsubscribe using the link at the bottom of the email.
Each week on Sunday (around 5:00 pm UTC), Cato sends a Product Update email that describes the new features and enhancements that are gradually deployed to customers and the Cato service. The same information is also available in an article in the Release Notes section of the Cato Knowledge Base.
The customer Product Update email is sent to each Cato Management Application admin.
On Wednesday of each week, Cato sends a Partner Product Update email that describes new features in Early Availability (EA) and other updates for Cato Partners. The same information is also available in an article in the Partner Release Notes section of the Cato Knowledge Base (requires Cato Partner permissions to view these articles).
The Partner Product Update email is sent to each Cato Management Application (CMA) admin who is registered with Cato as a Partner.
Cato announces upcoming Cato Client versions in the Product Updates. When the new version is available for your account, an announcement is shown in the notification area of the Cato Management Application.
For more information, see Best Practices for Cato Client Upgrades and Summary of Cato Client Releases.
To ensure a stable and consistent experience for all admins, Cato avoids making major changes to the CMA without careful planning and clear communication. Enhancements are released incrementally to minimize disruption, allowing IT teams to adapt smoothly. Any significant updates are announced in advance and are designed to maintain continuity in workflows and functionality.
These are Cato's policies for major CMA changes and End of Life/End of Support (EoL/EoS):
-
CMA - A major change to the CMA is announced at least 3 months in advance in the Product Update
Examples of major changes to the CMA are: changing the navigation menus and migrating a rule base to the new Socket Next Gen LAN FW policy
-
Clients - A Client version for a specific operating system that will be EoS is announced at least 6 months in advance in the Product Update, see End of Support (EoS) Policy for Cato Clients
-
API - GA APIs that will be EoL are announced at least 3 months in advance, and generally 6 months in advance in this article: Cato API Potentially Breaking Changes and EoL
These are other types of updates and email notifications that are sent to customers.
When Cato is ready to release a new Socket version, a Socket Release Note announcement with the content of the version is shown in the notification area of the Cato Management Application. The content is also published as an article in the Socket Release Notes section of the Knowledge Base.
When there is a critical security vulnerability that could impact Cato customers, a Security announcement is emailed to all Cato Management Application admins. The same information is also available in the Security Announcements section of the Knowledge Base.
Sometimes, there is a change or update to the Cato service that may impact customers, for example migrating a legacy setting in the Cato Management Application to a new feature. An email notification is sent to the Cato Management Application admins for the specific accounts that are impacted by the change. The same information is also available in the General Notifications section of the Knowledge Base.
1 comment
Added Announcing Major CMA Changes and EoL
Please sign in to leave a comment.