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
7/19/2019 | 8:22:15 PM
The online grid is great, right click on an element, press select, then click on view technique, this provides a page that details on what is using that exploit, this is good for identying the threat, the techniques they use but it does not provide the ways to mitigate. Google's ProjectZero provide the code and way to mitigate the variant or method of attack.
What I do like is that there are numerous resources from FireEye, Google, McAfee, Symantec and other sources that have validated the attack problem, this is very good, a way to verify and cross-reference the attack.
I think the next evolution would be to implement a guide that provides the solution or fix to the vulnerability or threat. This should be cross-referenced by multiple sites to ensure what we are proposing actulaly fixes or resolves the problem. Also, if the solution was identified on a Linux or Windows machine, then some sort of code could be used to mitigate the problem, short or long term.
Todd