--- title: "Update CMA Policies due to Changes to Suspicious TLD Applications" slug: "update-cma-policies-due-to-changes-to-suspicious-tld-applications" tags: ["App Category Updates"] updated: 2026-10-04T07:41:41Z published: 2026-10-04T07:41:41Z canonical: "knowledge.catonetworks.com/update-cma-policies-due-to-changes-to-suspicious-tld-applications" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledge.catonetworks.com/llms.txt > Use this file to discover all available pages before exploring further. # Update CMA Policies due to Changes to Suspicious TLD Applications In the [App Catalog](https://knowledge.catonetworks.com/docs/using-the-app-catalog), the following applications are currently members of the **Uncategorized** category in addition to their dynamic URL-filtering category: - Suspicious TLD mov - Suspicious TLD top - Suspicious TLD zip - Suspicious TLDs Starting from October 25, 2026, we are removing these apps from the **Uncategorized** category. Each traffic flow will be identified using the dynamic URL-filtering category (for example, Business, Shopping, Phishing, etc.), and rules that previously matched this traffic through the **Uncategorized** category will no longer match it. This update changes how the [Application Control](https://knowledge.catonetworks.com/docs/managing-the-application-control-policy), [File Control](https://knowledge.catonetworks.com/docs/creating-file-control-rules-in-the-application-control-policy), [Internet Firewall](https://knowledge.catonetworks.com/docs/managing-the-internet-firewall-policy), and [TLS Inspection](https://knowledge.catonetworks.com/docs/configuring-tls-inspection-policy-for-the-account) policies apply to these apps' traffic for rules that contain the **Uncategorized** category. To ensure these apps' traffic is controlled to meet your requirements, you must review rules in the policies above before October 25, 2026. **Note:** [Content updates to the Cato PoPs](/v1/docs/understanding-rollout-to-the-cato-cloud#updating-the-cato-cloud) are gradually rolled out to the PoPs over two weeks. ### What is the Impact to my Account? Starting from October 25, 2026: - Suspicious TLD mov, Suspicious TLD top, Suspicious TLD zip, and Suspicious TLDs will no longer be a member of the **Uncategorized** category - Rules that match on the **Uncategorized** category will stop applying to these apps - Flows will be evaluated by their dynamic URL-filtering category (for example, Business, Shopping, Phishing, etc.) For example, traffic that was previously blocked because a rule matched the **Uncategorized** category may now be allowed or only inspected by a rule that matches the dynamic URL-filtering category. ### What Updates do I Need to Make to My Account? You need to review the Application Control, File Control, Internet Firewall, and TLS Inspection policies and identify rules that contain: - The **Uncategorized** category — starting from October 25, 2026, this rule will no longer apply to Suspicious TLD mov, Suspicious TLD top, Suspicious TLD zip, and Suspicious TLDs Please use the [Cato Ask AI agent](https://knowledge.catonetworks.com/docs/what-is-cato-s-ask-ai-agent) in the CMA to help identify rules, objects, and entities that are impacted by this change. AI can make mistakes, and we recommend that you also validate that there is no impact to traffic flows. You can copy and paste the following prompt into Ask AI: --- > The following applications are going to stop carrying the **Uncategorized** category, and each application's traffic will be classified by its dynamic URL-filtering category instead: > > - Suspicious TLD mov > - Suspicious TLD top > - Suspicious TLD zip > - Suspicious TLDs > > Please review my existing policies and identify how this change will affect them. > > Look for rules referencing any of the mentioned apps or categories. Look in all policy types. > > For each affected policy and rule: > > - Explain why the rule will be impacted. > - Specify exactly what change, if any, I should make to the rule. > - Explain the expected behavior after the change. > > Please review all of my policies and rules so that no potential impact is missed. If a rule does not require any changes, no action is needed.