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
6/1/2019 | 6:50:13 PM
In contrast, a past company of mine that developed financial software blocked all Internet access by default, prevented USB access to all systems by use of physical system locks and protected all their Ethernet ports with similar locks. Emails were filtered on a level of paranoia and no attachments were allowed incoming or outgoing. A document control system that was only accessible on the LAN (no VPN access) was exclusively used for exchange of documents, and all the code bases were accessed from secured local servers serving up Git to onsite developers.
Obviously the comment here is going to be that many companies are hybrids with local offices and also remote offices and contractors. Some companies don't even have physical offices. This could point to why many organizations like the one who spent so much time securing USB port might overlook the existence of Google Drive and MEGA being just a URL away. It also begs the question whether convenience and the modern expectation of immediate response might be one of our biggest Information Security setbacks...