DNS is inherently insecure because it was built in a time when everyone on the Internet trusted everyone else to have users’ best interests at heart. Sadly, we live in a world where that’s not the case. One of the proposals on the table to help fix problems is to secure DNS by running it over HTTPS. That’s great for the average consumer in the world that doesn’t do much beyond surfing, checking email, and shopping online. But what about Enterprises?
The amount of DNS in the Enterprise that is custom and needs care and feeding is impressive. You need to have a plan of attack to make sure it’s going to still work when DNS-over-HTTPS is finally rolled out. Josh Warcop takes a look at how to do this with Firefox, the web browser that was the first to implement this new protocol by default in an upcoming release.
Let’s address the most obvious problems for enterprises. DNS represents a wealth of information gathering within the four walls of a business. Content control, security protections, and split DNS are just a few things to mention. Breaking host level DNS resolution of browser is a threat against these protections.
Read more here: Firefox DNS-over-HTTPS for the Enterprise
- Bad Behavior Analysis with Juniper Networks - August 6, 2020
- Multi-Cloud Fabric with Arrcus - July 30, 2020
- IoT Doesn’t Need Wi-Fi 6E – The On-Premise IT Roundtable - July 28, 2020
- Introducing Security Field Day 4 - July 21, 2020
- Cisco SecureX Roundtable - July 14, 2020
- Cisco Intent-based Networking Roundtable - July 13, 2020
- Tomversations: Episode 5 – End-to-End Encryption - July 9, 2020
- Cisco Live Interview with Khalid Raza - July 2, 2020
- The New Branch with Riverbed SD-WAN - June 30, 2020
- AI Can’t Do Much for WiFi – The On-Premise IT Roundtable - June 30, 2020