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: Ninja
8/21/2014 | 8:47:12 AM
I am also not surprised by the lack of defense-in-depth regarding security protocols and controls.
At this point, the only remaining bit of information I am interested in is how they discovered the breach. Was it an internal audit? Was it a spike in network activity?
I am developing particularly thick shell regarding information breaches. Not in reaction, but in preparation. I believe there are many more breach reports to come from all parts of the world and all industries. As the world very... very slowly becomes more security conscious, organizations are standing up their security programs. As these security programs begin to put in basic security controls, information from those controls will, if they are working correctly, identify more breaches. In more mature security programs, there are likely areas where there are weaknesses in the capability to identify breaches as soon as possible.
The only question that remains is in how transparent the organization leadership is in notifying share holders, law or regulatory entities, and the general public when a breach is identified. This is likely going to be an ongoing debate for years to come.
Knowing how the breach occurred is important, but it is also important to learn specifics about how the victim discovered the breach in the first place. That information can be helpful to other organizations that are still developing their security programs. The same information can also be helpful for more mature security programs to engage new initiatives to improve relevant controls.