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: Apprentice
6/9/2017 | 9:33:58 PM
I started to experience these problems at home more than a year ago. One of my sons got a Roku box and later NVidia media shield.
Many times we had been attacked and cut of the internet services only when using any of these two boxes. Started with a massive DoS that somehow poisoned the CAM table of the managed switch. As we do not have any VLANS or separate network for Roku or NVidia boxes, it ended up corrupting and cutting of the internet services as the exit gateway on any PC at home ends in 0.0.0.0 instead of the right one. It also poisons the DNS cache of the home router.
After that I put in service a Cisco ASA 5506x- Firepower and things turned more difficult for them.
Two weeks ago I took the Cisco ASA out and put a Fortinet 30E but forgot to enable the DoS policy, hence, last night we lost the internet again but now the policy is in place, as well as IPS (Intrusion Prevention System). Needeles to say this weekend, the NVidia shield will end in its own Vlan and VDOM (as fortigate callst it) and in a new managed switch with ARP protection as well.
Well, not many home users will have the knowkedge and capacity to put this toghether but let me tell you that 99% oh those "royuters" at home would not last 10 seconds. Even some of the "commercial" grades one like D Link D 520 that I had to put in the rubbish bin.
Yes, agree, there is a gigantic problem..............I can even see the security logs of the Fortigate 30E with the HTTP injection coming in...............quite an incredible and "invisible to the human eyes" problem.