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
1/14/2017 | 2:51:36 PM
1) If something is everybody's job, it's nobody's job. If employees whose primary tasks are to answer telephones or to do data entry or construct marketing plans or whatever engage in a cybersecurity failing, while there should be some remediation, instead of flogging the peasants, I propose punishing the generals -- and calling the CIO/CISO/etc. on the carpet -- because, ultimately, it's their failing. If the front-line employees aren't properly trained and properly acting on that training, it's the trainers' fault and the fault of the people responsible for that training to begin with.
2) In a heavy-handed "flog-the-peasants" environment, employees -- even managers -- will be reluctant at best to come forward if they violate a policy that then results in a potential data compromise. Consequently, there needs to be appropriate policy for this that doesn't use the stick so much as the carrot. (I've written on this, for example, here: enterprisenetworkingplanet.com/netsysm/minimize-shadow-it-damage-by-encouraging-self-reporting.html ).