Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Network Security

Universities Offer Practical Advice for Securing DNS

The Research and Education Networking Information Sharing and Analysis Center, or REN-ISAC, recently issued an alert to administrators and IT staffers at some of the world’s most notable institutions of higher learning that urges them to take the matter of securing DNS seriously.

The Research and Education Networking Information Sharing and Analysis Center, or REN-ISAC, recently issued an alert to administrators and IT staffers at some of the world’s most notable institutions of higher learning that urges them to take the matter of securing DNS seriously.

The REN-ISAC alert cites the recent Spamhaus attack as a perfect example of why DNS configuration should be a priority, if only to prevent the institution from becoming an unwitting accomplice to similar attacks in the future – and given the success of the last one, it’s only a matter of time before it happens again.

“These attacks may exploit thousands of institutional DNS servers to create an avalanche of network traffic aimed at a third-party victim. The traffic sourced by any single institutional system may be small enough to go unnoticed at the institution; however, the aggregate experienced at the target can be crippling,” the advisory explains.

“To put that in context, most universities and organizations connect to the Internet at 1 Gbps or less. In this incident not only was the intended victim crippled, Internet service providers and security service providers attempting to mitigate the attack were adversely affected.”

Related Reading: Now is the Time for Source Address Validation

The advisory goes on the list seven things that institutions can do to harden their DNS deployments, but it’s a list that can be used by any organization with a need to strengthen their own infrastructure.

First and foremost, the main piece of advice centers on limiting recursive resolvers, as “it is absolutely critical all university recursive resolvers are properly configured so they only answer queries for the local users they’re meant to be serving,” the advisory states. One way of doing this, the advisory says, by limiting access to the recursive resolvers to only the enterprise’s IP addresses.

Further advice includes rate limiting authoritative name servers, and using router ACLs so that queries from the outside can only go to permitted authoritative name servers. This “mitigates risk from various uncontrolled devices, such as Internet appliances that have an embedded DNS service.”

Advertisement. Scroll to continue reading.

The full advisory, along with additional resources, is available online.  

Related ReadingNow is the Time for Source Address Validation

Related ReadingDutchman Arrested in Spain for ‘Biggest Ever’ Cyberattack

Related Reading: Cyberattack Capable of Downing Entire Internet Is Unlikely

Written By

Click to comment

Trending

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Join this event as we dive into threat hunting tools and frameworks, and explore value of threat intelligence data in the defender’s security stack.

Register

Learn how integrating BAS and Automated Penetration Testing empowers security teams to quickly identify and validate threats, enabling prompt response and remediation.

Register

People on the Move

Edge Delta has appointed Joan Pepin as its Chief Information Security Officer.

Vats Srivatsan has been appointed interim CEO of WatchGuard after Prakash Panjwani stepped down.

Network security policy management firm FireMon has appointed Alex Bender as Chief Marketing Officer.

More People On The Move

Expert Insights

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest cybersecurity news, threats, and expert insights. Unsubscribe at any time.