How the D-Zone DNS Firewall adds defence in depth

For larger organizations and MSPs (managed service providers), IT security has grown into its own team, often with a contributory role in premise and physical security. For those teams, this type of framework helps to describe how things work to their peers and to non-technical people across the organization. For those IT departments in smaller organizations that are boot-strapping together security solutions, we hope this guide can help you understand the role of the DNS in a defence-in-depth scenario.

The threat landscape is more complicated than ever

In the entire scope of security we often include money, technology, processes, premises and people. For technology there is a fairly common understanding of the layers involved in a typical stack and these layers all need to consider security in their design and development.

Within the technology framework there are also subcategories for hardware and network equipment that need management and patching. While this creates an administrative burden, it is the responsibility of individuals and if the time is planned it can be managed more easily. What is harder to manage is the behaviour of your users and that of thieves targeting your organization.

With a massive upward trend of connected devices and shadow IT combined with increasing threats fueled by a profit motive, a defence in depth strategy is necessary. Organizations benefit from multiple tools because the hackers are motivated to deploy their own multi-vector frameworks.

What is “defence in depth”?

The term has its origins in the military, where defensive layers protect themselves, each other, and the core. In the case of a DNS firewall, it exists outside the organization and could be analagous to air-cover over a battlefield. It has a unique view and response to the threat landscape.

Common attacks and their motivations. While ransomare garners the headlines, the threat landscape has all sorts of motivations.

source: Nominum Data Science