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/16/2019 | 10:05:22 AM
If this aspect is one of their main concerns, why don't they bring in third-party consultants to address some of their issues? A number of health-care agencies have a direct relationship with the university's CIS or IT divisions. It would make sense to tap into that knowledge base on campus (i.e. CIS - Computer Information Systems). The university's IT group could help address some of the IT security issues, not sure if they are but it would be interesting to see what they are doing to protect this data?
Please review the top NAC solutions (comparison listed below), it is imperative because NACs ensure isolated access to medical devices.
NAC Device Comparison Reference
Per the conversations on DR (Dark Reading), it is imperative to put the medical devices on their own network (network segmentation), then route all of the traffic from the various devices to managing switches (daisy chain or cluster them together). By isolating the traffic, the hospital could filter access to the medical devices (i.e. Med-Dev, made it up) to only to their management systems and staff, nothing else. This process could limit the external attack by reducing the hospital's attack surface. Also, I would suggest the following as a possible solution:
The vendor needs to support IPv6, most of the hack attempts identified have occurred on IPv4 and not IPv6 (Russia, China, North Korea, Iran, Japan).
Todd