Want to get started with implementing a protective DNS solution, but not sure how or where to get started? Watch this video as Paul Mockapetris, the inventor of the DNS, gives you step-by-step instructions to make sure your system’s and users are secure.


Conventional cybersecurity solutions alone are not enough these days. Sensitive information is being stolen and systems are being hacked daily. Make sure you have a secure defense in place that includes a preventative security control like Protective DNS (PDNS). In this video, we help you secure your systems and users to keep out malware and get hackers to move on to other, easier targets.

We’re here to help! Finding the right DNS security system can be overwhelming. But making sure your network is protected with PDNS is an easy fix, and takes less than five minutes to deploy and configure - and the results are immediate. Let ThreatSTOP prevent threats before they can even become a problem. Talk with one of our experts today to get going and get protected. Remember, not all DNS filtering solutions are equal. You need a complete solution that delivers security and helps you meet compliance requirements without interrupting your business operations. ThreatSTOP delivers on all three of these critical needs.


Learn More:

What DNS Security Does A Typical Enterprise Need?

DNS Defense Cloud 

DNS Defense 


Video Transcript


0:00 Intro
0:05 Steps In An Ideal PDNS Implementation

0:05 Steps In An Ideal PDNS Implementation
So what’s the steps in an ideal, perfect PDNS? Well, you have to have your network designed in the appropriate way. You have to have DNS servers. You have to get threat intelligence.

Threat intelligence I said very quickly, was knowing what's naughty and what's nice, knowing which traffic you want and which traffic you don't. You don't have to figure this out for yourself. You can get threat intelligence from a variety of open source, government, and proprietary sources for that.

You have to deploy that threat intelligence into your DNS servers. You have to take a look at the results and then you have to take what you've learned and use it to modify the threat intelligence that you have deployed in your network. And sometimes in these cloud implementations, a particular cloud server will turn bad, be a source of malware for a while. It'll get cleaned up and then be a good thing.

So, you can't just continually add bad guys. You have to occasionally cull the bad sites that have been cleaned up. Bad guys that have been cleaned up might include sites like the New York Times, for example, that for a short while, was hosting malware ads.

You can't necessarily depend upon your instincts for this. You have to be on guard.