Dark Reading is part of the Informa Tech Division of Informa PLC
This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
Everything You Need to Know About DNS AttacksIt's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask.
Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted.
Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Incident Readiness and Building Response Playbook
In this special report, learn the Xs and Os of any good security incident readiness and response playbook.
Tweet This
1 Comments
User Rank: Strategist
1/30/2019 | 3:40:31 PM
It may be fashionable to claim there is no longer a network perimeter but I still strongly favor using the border router as a "garbage filter".
The BOGONs list? - Drop them all. Invalid TCP flag combinations - Drop. No Telnet in your environment? No FTP? No RDP? - Block them all at the border router.
As mentioned in the post, the NGFW should take care of the deep packet inspection for only the traffic you potentially want inside your network. That firewall should see very little traffic except for the known IPs, ports and protocols which are candidates to be allowed all the way in.
And an outbound ACL (a.k.a. egress filtering) is a very powerful weapon against data exfiltration and many types of malware. You may still have a Trojan but if it can't phone home......