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/28/2019 | 5:35:31 PM
There is a simple way to address this problem, the S3 bucket process involves blocking public access if the user goes to aws.amazon.com | Select S3 | Click the bucket | Click Permissions Tab | Select Block Public Access. Secondly, select "Access Control List" | access for bucket owner | Select the bucket owner (should be a long bucket id to allow access only to this S3 bucket).
Examples of S3 Bucket compromise are listed below (this is not the complete list but it should give you an idea of breaches.
Again, all of these instances could have been mitigated by following best practices provided by AWS (improperly trained personnel or oversight need to be top priority).
T