Requires Free Membership to View
SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!
Michael S. Mimoso, Editorial DirectorThat means the DNS server must be patched, or the company should upgrade to a more robust server infrastructure. One possibility is DNSSEC, which the U.S. federal government just deployed, but that is pretty complicated.
Another important thing is to make sure that all upstream ISPs have their act together. Even if the company's system is fine, dealing with any compromised name servers is disastrous.
In terms of where the responsibility of DNS security should reside, that depends on what kind of operational responsibilities the security team has. Many security teams these days are more influencers than implementers, which means they need to work with the organization's network team, which would actually deploy any remediation.
More information:
- Learn how to patch Kaminsky's DNS vulnerability.
- Read more about the importance of DNS rebinding defenses.
This was first published in July 2008