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
4/15/2021 | 5:48:17 PM
In addition, all ports (if web-server) should be blocked, except port 443 or 80 in some respects (Windows firewall can do that but there are ofcourse better options - PaloAlto is a good one that we use), not sure why the execution policy (if configured properly) would even allow remove exploits like this to penetrate the initial defenses).
netsh advfirewall firewall add rule name="Require Encryption for Inbound TCP/80" protocol=TCP dir=in localport=80 security=authdynenc action=allow
I would also go to "taskschd.msc" and look at the "Task Scheduler Library" to ensure there are no running "PS" scripts. The user can create a script to run to ensure the setting is always set to "Restricted"
This ensures the system is set to restrict executionpolicy or set it to Restricted.
Also, Windows 10 uses Windows Defender Security Center to protect against these types of Attacks, this could have been overlookewell, lessons learned.
Todd