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
10/30/2016 | 12:41:23 PM
Considering they telephoned me, and considering that the number they were calling from was not a telephone number known to me to be associated w/ my carrier, I refused. The huffy person on the other end of the line appeared put out.
I then called my insurance company on the number I knew to be correct to ask them about it. Unfortunately, it's such a big bureaucracy that I couldn't even get through to someone who could even tell me whether or not the call was legitimate for sure.
Because my insurance company was so bureaucratic and stupid, I wouldn't put it past them to have such stupid practices -- but it's also just as likely (at least) that it was a malfeasor's bit of social engineering. In any case, nothing bad happened to me because I refused to "verify" my information.
People calling you asking you to "verify" your information is the slightly more sophisticated social-engineering equivalent of someone calling you and after you say hello, the other person on the line immediately says, "Who's this?" YOU CALLED ME. >:P