Monday, December 23, 2024
HomeCyber AttackDHS Issued Emergency Directive Ordering Federal Agencies To Audit DNS Activity for...

DHS Issued Emergency Directive Ordering Federal Agencies To Audit DNS Activity for their Domains

Published on

SIEM as a Service

DHS issued an emergency directive to federal agencies and it staffs to Audit DNS Records, Change DNS Account Passwords, Add Multi-Factor Authentication and Monitor Certificate Transparency Logs within next 10 business days.

The emergency alert issued after in wake of the ongoing DNS campaigns targeting various domains organizations belonging to various government, telecommunications and internet infrastructure entities.

DNS hijacking is a type of Malicious attack that used to redirect the users to the malicious website when they visit the website via compromised routers or attackers modifying a server’s settings.

- Advertisement - SIEM as a Service

These types of attacks begins by gaining access to the acounts that privileaged to make changes with the DNS records.

Once the attackers gains control over the DNS portal of the domains they will change the DNS records such as Address (A), Mail Exchanger (MX), or Name Server (NS) records and points to malicious server address.

A – A record is used to point the domain name such as gbhackers.com to the IP address of it’s hosting server.
MX – Records responsible for Email exchange.
NS – NS records are to identify DNS servers responsible for the domain.

“To address the significant and imminent risks to agency information and information systems presented by this activity, this emergency directive requires the following near-term actions to mitigate risks from undiscovered tampering, enable agencies to prevent illegitimate DNS activity for their domains, and detect unauthorized certificates,” reads the advisory.

Advisory Actions – Within 10 Business Days

  • Audit public DNS records on all authoritative and secondary DNS servers and to verify they are pointing to desired locations.
  • Update passwords for all the accounts on the system.
  • Add multi-factor authentication for all the accounts that are privileaged to make the DNS changes.
  • Agencies should monitor the Certificate Transparency (CT) logs for agency domains and to begin monitoring CT log data for certificates issued that they did not request.

The infrastructure agency CISA began to provide regular delivery of newly added certificates to CT logs for agency domains via the Cyber Hygiene service.

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity updates also you can take the Best Cybersecurity courses online to keep your self-updated.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

17M Patient Records Stolen in Ransomware Attack on Three California Hospitals

A staggering 17 million patient records, containing sensitive personal and medical information, have been...

WhatsApp Wins NSO in Pegasus Spyware Hacking Lawsuit After 5 Years

After a prolonged legal battle stretching over five years, WhatsApp has triumphed over NSO...

PentestGPT – A ChatGPT Powered Automated Penetration Testing Tool

GBHackers come across a new ChatGPT-powered Penetration testing Tool called "PentestGPT" that helps penetration...

Threat Actors Selling Nunu Stealer On Hacker Forums

A new malware variant called Nunu Stealer is making headlines after being advertised on underground hacker...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

17M Patient Records Stolen in Ransomware Attack on Three California Hospitals

A staggering 17 million patient records, containing sensitive personal and medical information, have been...

WhatsApp Wins NSO in Pegasus Spyware Hacking Lawsuit After 5 Years

After a prolonged legal battle stretching over five years, WhatsApp has triumphed over NSO...

Threat Actors Selling Nunu Stealer On Hacker Forums

A new malware variant called Nunu Stealer is making headlines after being advertised on underground hacker...