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
9/23/2014 | 11:12:58 AM
But a small correction for @Robert McDougal...
Transcom is short for USTRANSCOM which is the DoD Command responsible for all tranportation logistics doctrine and management for all DoD organizations. Transcom is thus a government entity, not a contractor.
The fact that Transcom was not aware of the breaches does not surprise me. Transcom is basically a large entity that facilitiates and coordinates the contracting for movement of military materiel and personnel. The intelligence function of Transcom relies on DIA and other government intelligence functions to provide information on threats to their contractor pool.
I believe that the bigger problem is that contractors are not generally required to report security incidents unless the incident will directly impact delivery of logistics services. Most of these hacks look to be information gathering thus having very little impact on service delivery. Unlike the health industry, there is no legal requirement for private entities in the defense industry to report any compromises unless dictated by contractual agreement.
Counterintelligence is generally perceived as the realm of the USGov intelligence community, not the logistics community. If the intelligence community notified Transcom of such activity, odds are it would have acted on the information.
I am certain that Transcom is currently in the immediate remediation of the causes for this situation. If there is one thing that the DoD is good at, is adapting to security threats that make the headlines.