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
- Moving Past The Edge with Aruba SD-Branch - February 26, 2020
- Does SPB Mean “Secure Path Bridging”? - February 12, 2020
- Cloud Isn’t Your Key To Compliance - February 10, 2020
- Breaking IoT Security - February 7, 2020
- Answers at Your Fingertips with Forward Networks - February 4, 2020
- Priming Your Application Performance with Intel Application Device Queues - January 29, 2020
- Is Cisco SD Access Intent Based Networking? - January 28, 2020
- Captivating Wireless Connectivity with Cisco OpenRoaming - January 22, 2020
- Does the Apple Airport Extreme Use VLANs? - January 21, 2020
- Predicting Data Patterns with Cradlepoint - January 16, 2020