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/25/2019 | 9:21:13 AM
Interesting, I don't agree with that, I think lack of knowledge, experience, strategy and inadequate education can leave a company susceptible to attack. The cloud is an extension of the organization. No matter how secure the cloud provider is, the individuals that are responsible for its functions will carry those same practices over to the cloud. Look at a few companies that have been hit by incompetence (Cloud S3 Issues):
Again, all you have to have is a person who leaves one door open. Think about creating a VM on any CSP, look at the /var/log/*.log files and run the following:
Be sure to look at the number of attempts of someone trying to access ssh, this is alarming, now you have the option of locking down ssh using iptables and cloud rules (NSG or ACL IP filtering):
Just a word to the wise.
Todd