<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>TDR - Product Enhancements — WatchGuard Community</title>
        <link>https://community.watchguard.com/watchguard-community/</link>
        <pubDate>Wed, 11 Mar 2026 13:44:31 +0000</pubDate>
        <language>en</language>
            <description>TDR - Product Enhancements — WatchGuard Community</description>
    <atom:link href="https://community.watchguard.com/watchguard-community/categories/tdr-product-enhancements/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Add SD-WAN Failover Thresholds to Global Multi-WAN Configuration</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/4443/add-sd-wan-failover-thresholds-to-global-multi-wan-configuration</link>
        <pubDate>Fri, 31 Oct 2025 12:27:53 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>Ward_Cauwelier</dc:creator>
        <guid isPermaLink="false">4443@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>Currently, SD-WAN actions support measurement-based failover (packet loss %, latency, jitter), but the global Multi-WAN failover configuration only supports basic connectivity failover (connection fail). This means we must create individual SD-WAN actions for every policy on a firebox when we want that site to failover intelligently for every connection, which is time-consuming and difficult to maintain. This could be solved by adding the SD-WAN failover threshold options to the existing global Multi-WAN failover configuration.This would make WatchGuard's Multi-WAN more competitive with other enterprise firewall platforms while maintaining the flexibility of per-policy overrides when needed.</p>
]]>
        </description>
    </item>
    <item>
        <title>Host configuration</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/241/host-configuration</link>
        <pubDate>Mon, 17 Jun 2019 14:27:03 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>Nateb</dc:creator>
        <guid isPermaLink="false">241@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>In previous versions of the host administrators could push out configurations such as hiding the client from the system tray, or turning off notifications. That ability isn't in 5.7 and it's confusing the heck out of my users. They're getting too many notifications and don't understand what the software is on their computers for. Please bring this capability back!</p>
]]>
        </description>
    </item>
    <item>
        <title>Indicator summary by hash</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/1809/indicator-summary-by-hash</link>
        <pubDate>Fri, 07 May 2021 13:36:01 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>hfwu</dc:creator>
        <guid isPermaLink="false">1809@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>Hi!</p>

<p>We're a few months into testing TDR on our systems. A few days ago, we started rollout on our student pc pools (30-40 hosts each). Whenever a software update trips the heuristics on the host sensor, at least 2-4 indicators are created per host but most of them have the same hash. With &gt;800 Indicators that have to be dealt with, the one indicator that might be a real threat flies under the radar and might even be disregarded with all the false-positives. Of course this will only get worse the more clients we add. With a view-by-hash or view-by-threat feature that lists the active hashes of the indicators, number of affected clients, if possible the filename or folder of the indicator and the threat information, identifying real threats could be made much easier. Adding to that, if you identified an identical false-positive indicator that was generated on hundreds of hosts, disregarding these indicators or allowing the hashes all at once would also be much easier. Maybe you could even add an automatic filter by hash to the existing indicator list when you click on a specific hash in this new list.</p>
]]>
        </description>
    </item>
    <item>
        <title>Roadmap - TDR in WG Cloud</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/1506/roadmap-tdr-in-wg-cloud</link>
        <pubDate>Tue, 22 Dec 2020 03:37:22 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>Tristan.Colo</dc:creator>
        <guid isPermaLink="false">1506@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>Is there a target date for when TDR will be available in cloud.watchguard.com?</p>
]]>
        </description>
    </item>
    <item>
        <title>TDR access for MSP customers</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/751/tdr-access-for-msp-customers</link>
        <pubDate>Tue, 04 Feb 2020 16:09:13 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>Sean</dc:creator>
        <guid isPermaLink="false">751@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>We have customers that want to get access to their own TDR portal and investigate alerts, etc. Currently this is not possible. If we give them access through WG Portal they get extra access and can see other customers data too!!!</p>

<p>I hope WatchGuard adds this feature soon so that we can create a TDR account for customers who want to have access to their OWN TDR portal - with read-only account option.</p>
]]>
        </description>
    </item>
    <item>
        <title>TDR Service Provider - unable to add existing customers</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/340/tdr-service-provider-unable-to-add-existing-customers</link>
        <pubDate>Tue, 30 Jul 2019 13:46:28 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>oncfirebox</dc:creator>
        <guid isPermaLink="false">340@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>I don't understand why the feature to delegate firebox licenses to a TDR partner is not provided (as the option does exist for Authpoint and WatchGuard Cloud).</p>

<p>WG Support recommends to use 'transfer of ownership' from customers to partners for TDR Service Provider Management ?</p>
]]>
        </description>
    </item>
    <item>
        <title>Pain Points</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/237/pain-points</link>
        <pubDate>Thu, 13 Jun 2019 17:10:55 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>JellyKid</dc:creator>
        <guid isPermaLink="false">237@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>We went all in on Watchguard this year because the sales team talks a big game but I'm starting to regret it.</p>

<p>Here are my most painful points:<br />
1. Support doesn't understand the product. I always have to try to escalate until I find someone that kind of understands it. Most of the time support wants to connect to one of my firewalls instead of TDR, when the issue has nothing to do with the firewall. Honestly this product is so different from the others, there should be a separate support team for it IMO.<br />
2. Lack of documentation on things like best practices.<br />
3. Loads of indicators on things that should be trusted. We see indicators on files signed by Microsoft. There is no way to exclude indicators based on publisher. Whitelisting doesn't solve the issue as most of the indicators are for updates or patches which is a routine thing that happens everyday and creates unique files.<br />
4. No way to whitelist domains / report false positives. I understand that it's RED on my firewall that is blocking it and I can whitelist in the HTTP proxies but when something like my AV vendor domains are getting level 7 incidents because of RED, wouldn't the better solution be to submit the domain as a false positive and whitelist it?<br />
5. Files don't upload to APT blocker 90% of the time due to file size. When they do upload, if the file is found to be by a trusted vendor the indicator still stays at the original level rather than being remedied.<br />
6. No way to create rules to automatically remedy or take complex actions, there's not enough control over policy actions.<br />
7. It doesn't interact / take advantage of intelligentAV. There are big holes in the intelligentAV product(no proper way to scan MAPI protocol without routing all mail through a single firewall) which could be remedied by directly interacting with TDR.<br />
8. No true baselining. As far as I can tell it doesn't set a network baseline for things like traffic and activity on the host. I thought this was supposed to be an intelligent product that could detect and alert on abnormal behavior on the host. How can it do that if it doesn't set a network activity baseline.<br />
9. Reporting is sparse and uses scary lingo in executive reports. I am yet to bring any of the reports to our board of directors because the language in the reports makes it seem like our network has been infected when in fact it was just a RED false positive or there are outstanding indicators for things like Microsoft patches.</p>

<p>TDR has a lot of potential but right now it seems half baked. It's frustrating how much was promised and how little was actually delivered.</p>
]]>
        </description>
    </item>
    <item>
        <title>Welcome!</title>
        <link>https://community.watchguard.com/watchguard-community/discussion/103/welcome</link>
        <pubDate>Fri, 15 Mar 2019 13:34:31 +0000</pubDate>
        <category>TDR - Product Enhancements</category>
        <dc:creator>Ricardo_Arroyo</dc:creator>
        <guid isPermaLink="false">103@/watchguard-community/discussions</guid>
        <description><![CDATA[<p>Welcome to the WatchGuard Community. The product enhancements discussion is the place to post your ideas and suggestions for improvements that you would like to see to the Threat Detection &amp; Response product. This will be monitored by the Product Management team as a valuable source of input into our product planning process.</p>

<p>Please describe the user pain point or problem that you need to solve with as much detail as possible. Try to avoid defining exactly what type of checkbox or widget you need to see added as our Engineers and PMs may often create more general or creative solutions.</p>

<p>Thanks,</p>
]]>
        </description>
    </item>
   </channel>
</rss>
