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: Apprentice
5/26/2021 | 2:17:37 PM
The attack was against the billing system and the operators of the pipeline chose to shut it down because they were afraid that they wouldn't have a way to retroactively bill their customers for activity that took place while the billing system was offline.
https://jalopnik.com/the-colonial-pipeline-was-fine-but-it-was-shutdown-to-1846911689
While the public reacted badly (hoarding gasoline, using improper/dangerous containers, etc.), if the pipeline operators either had an "offline" method for storing activity information that could be imported into the billing system retroactively or just decided to keep the pipeline operating and figure out the billing later, much of the Sturm und Drang around the incident could have been avoided.