www.cisa.gov Open in urlscan Pro
2600:141b:1c00:258d::447a  Public Scan

Submitted URL: https://www.us-cert.gov/ncas/alerts/TA15-240A
Effective URL: https://www.cisa.gov/news-events/alerts/2015/08/28/controlling-outbound-dns-access
Submission: On September 12 via api from IT — Scanned from US

Form analysis 2 forms found in the DOM

<form class="gsc-search-box gsc-search-box-tools" accept-charset="utf-8">
  <table cellspacing="0" cellpadding="0" role="presentation" class="gsc-search-box">
    <tbody>
      <tr>
        <td class="gsc-input">
          <div class="gsc-input-box" id="gsc-iw-id1">
            <table cellspacing="0" cellpadding="0" role="presentation" id="gs_id50" class="gstl_50 gsc-input" style="width: 100%; padding: 0px;">
              <tbody>
                <tr>
                  <td id="gs_tti50" class="gsib_a"><input autocomplete="off" type="text" size="10" class="gsc-input" name="search" title="search" aria-label="search" id="gsc-i-id1" dir="ltr" spellcheck="false"
                      style="width: 100%; padding: 0px; border: none; margin: 0px; height: auto; outline: none;"></td>
                  <td class="gsib_b">
                    <div class="gsst_b" id="gs_st50" dir="ltr"><a class="gsst_a" href="javascript:void(0)" title="Clear search box" role="button" style="display: none;"><span class="gscb_a" id="gs_cb50" aria-hidden="true">×</span></a></div>
                  </td>
                </tr>
              </tbody>
            </table>
          </div>
        </td>
        <td class="gsc-search-button"><button class="gsc-search-button gsc-search-button-v2"><svg width="13" height="13" viewBox="0 0 13 13">
              <title>search</title>
              <path
                d="m4.8495 7.8226c0.82666 0 1.5262-0.29146 2.0985-0.87438 0.57232-0.58292 0.86378-1.2877 0.87438-2.1144 0.010599-0.82666-0.28086-1.5262-0.87438-2.0985-0.59352-0.57232-1.293-0.86378-2.0985-0.87438-0.8055-0.010599-1.5103 0.28086-2.1144 0.87438-0.60414 0.59352-0.8956 1.293-0.87438 2.0985 0.021197 0.8055 0.31266 1.5103 0.87438 2.1144 0.56172 0.60414 1.2665 0.8956 2.1144 0.87438zm4.4695 0.2115 3.681 3.6819-1.259 1.284-3.6817-3.7 0.0019784-0.69479-0.090043-0.098846c-0.87973 0.76087-1.92 1.1413-3.1207 1.1413-1.3553 0-2.5025-0.46363-3.4417-1.3909s-1.4088-2.0686-1.4088-3.4239c0-1.3553 0.4696-2.4966 1.4088-3.4239 0.9392-0.92727 2.0864-1.3969 3.4417-1.4088 1.3553-0.011889 2.4906 0.45771 3.406 1.4088 0.9154 0.95107 1.379 2.0924 1.3909 3.4239 0 1.2126-0.38043 2.2588-1.1413 3.1385l0.098834 0.090049z">
              </path>
            </svg></button></td>
        <td class="gsc-clear-button">
          <div class="gsc-clear-button" title="clear results">&nbsp;</div>
        </td>
      </tr>
    </tbody>
  </table>
</form>

<form class="gsc-search-box gsc-search-box-tools" accept-charset="utf-8">
  <table cellspacing="0" cellpadding="0" role="presentation" class="gsc-search-box">
    <tbody>
      <tr>
        <td class="gsc-input">
          <div class="gsc-input-box" id="gsc-iw-id2">
            <table cellspacing="0" cellpadding="0" role="presentation" id="gs_id51" class="gstl_51 gsc-input" style="width: 100%; padding: 0px;">
              <tbody>
                <tr>
                  <td id="gs_tti51" class="gsib_a"><input autocomplete="off" type="text" size="10" class="gsc-input" name="search" title="search" aria-label="search" id="gsc-i-id2" dir="ltr" spellcheck="false"
                      style="width: 100%; padding: 0px; border: none; margin: 0px; height: auto; outline: none;"></td>
                  <td class="gsib_b">
                    <div class="gsst_b" id="gs_st51" dir="ltr"><a class="gsst_a" href="javascript:void(0)" title="Clear search box" role="button" style="display: none;"><span class="gscb_a" id="gs_cb51" aria-hidden="true">×</span></a></div>
                  </td>
                </tr>
              </tbody>
            </table>
          </div>
        </td>
        <td class="gsc-search-button"><button class="gsc-search-button gsc-search-button-v2"><svg width="13" height="13" viewBox="0 0 13 13">
              <title>search</title>
              <path
                d="m4.8495 7.8226c0.82666 0 1.5262-0.29146 2.0985-0.87438 0.57232-0.58292 0.86378-1.2877 0.87438-2.1144 0.010599-0.82666-0.28086-1.5262-0.87438-2.0985-0.59352-0.57232-1.293-0.86378-2.0985-0.87438-0.8055-0.010599-1.5103 0.28086-2.1144 0.87438-0.60414 0.59352-0.8956 1.293-0.87438 2.0985 0.021197 0.8055 0.31266 1.5103 0.87438 2.1144 0.56172 0.60414 1.2665 0.8956 2.1144 0.87438zm4.4695 0.2115 3.681 3.6819-1.259 1.284-3.6817-3.7 0.0019784-0.69479-0.090043-0.098846c-0.87973 0.76087-1.92 1.1413-3.1207 1.1413-1.3553 0-2.5025-0.46363-3.4417-1.3909s-1.4088-2.0686-1.4088-3.4239c0-1.3553 0.4696-2.4966 1.4088-3.4239 0.9392-0.92727 2.0864-1.3969 3.4417-1.4088 1.3553-0.011889 2.4906 0.45771 3.406 1.4088 0.9154 0.95107 1.379 2.0924 1.3909 3.4239 0 1.2126-0.38043 2.2588-1.1413 3.1385l0.098834 0.090049z">
              </path>
            </svg></button></td>
        <td class="gsc-clear-button">
          <div class="gsc-clear-button" title="clear results">&nbsp;</div>
        </td>
      </tr>
    </tbody>
  </table>
</form>

Text Content

Skip to main content

An official website of the United States government

Here’s how you know

Here’s how you know

Official websites use .gov
A .gov website belongs to an official government organization in the United
States.

Secure .gov websites use HTTPS
A lock (LockA locked padlock) or https:// means you’ve safely connected to the
.gov website. Share sensitive information only on official, secure websites.

Free Cyber Services#protect2024Secure Our WorldShields UpReport A Cyber Issue



Search

×

search
 

Menu



Close
×

search
 

 * Topics
   Topics
   Cybersecurity Best Practices
   Cyber Threats and Advisories
   Critical Infrastructure Security and Resilience
   Election Security
   Emergency Communications
   Industrial Control Systems
   Information and Communications Technology Supply Chain Security
   Partnerships and Collaboration
   Physical Security
   Risk Management
   How can we help?
   GovernmentEducational InstitutionsIndustryState, Local, Tribal, and
   TerritorialIndividuals and FamiliesSmall and Medium BusinessesFind Help
   LocallyFaith-Based CommunityExecutivesHigh-Risk Communities
 * Spotlight
 * Resources & Tools
   Resources & Tools
   All Resources & Tools
   Services
   Programs
   Resources
   Training
   Groups
 * News & Events
   News & Events
   News
   Events
   Cybersecurity Alerts & Advisories
   Directives
   Request a CISA Speaker
   Congressional Testimony
   CISA Conferences
   CISA Live!
 * Careers
   Careers
   Benefits & Perks
   HireVue Applicant Reasonable Accommodations Process
   Hiring
   Resume & Application Tips
   Students & Recent Graduates
   Veteran and Military Spouses
   Work @ CISA
 * About
   About
   Culture
   Divisions & Offices
   Regions
   Leadership
   Doing Business with CISA
   Site Links
   Reporting Employee and Contractor Misconduct
   CISA GitHub
   CISA Central
   2023 Year In Review
   Contact Us
   Subscribe

Free Cyber Services#protect2024Secure Our WorldShields UpReport A Cyber Issue

Breadcrumb
 1. Home
 2. News & Events
 3. Cybersecurity Advisories
 4. Alert

Share:


Alert


CONTROLLING OUTBOUND DNS ACCESS

Last Revised
September 29, 2016
Alert Code
TA15-240A



SYSTEMS AFFECTED

Networked systems


OVERVIEW

US-CERT has observed an increase in Domain Name System (DNS) traffic from client
systems within internal networks to publically hosted DNS servers. Direct client
access to Internet DNS servers, rather than controlled access through enterprise
DNS servers, can expose an organization to unnecessary security risks and system
inefficiencies. This Alert provides recommendations for improving security
related to outbound DNS queries and responses.

Client systems and applications may be configured to send DNS requests to
servers other than authorized enterprise DNS caching name servers (also called
resolving, forwarding or recursive name servers). This type of configuration
poses a security risk and may introduce inefficiencies to an organization.   


IMPACT

Unless managed by perimeter technical solutions, client systems and applications
may connect to systems outside the enterprise’s administrative control for DNS
resolution. Internal enterprise systems should only be permitted to initiate
requests to and receive responses from approved enterprise DNS caching name
servers. Permitting client systems and applications to connect directly to
Internet DNS infrastructure introduces risks and inefficiencies to the
organization, which include:

 * Bypassed enterprise monitoring and logging of DNS traffic; this type of
   monitoring is an important tool for detecting potential malicious network
   activity.
 * Bypassed enterprise DNS security filtering (sinkhole/redirect or
   blackhole/block) capabilities; this may allow clients to access malicious
   domains that would otherwise be blocked.
 * Client interaction with compromised or malicious DNS servers; this may cause
   inaccurate DNS responses for the domain requested (e.g., the client is sent
   to a phishing site or served malicious code).
 * Lost protections against DNS cache poisoning and denial-of-service attacks.
   The mitigating effects of a tiered or hierarchical (e.g., separate internal
   and external DNS servers, split DNS, etc.) DNS architecture used to prevent
   such attacks are lost.  
 * Reduced Internet browsing speed since enterprise DNS caching would not be
   utilized.


SOLUTION

Implement the recommendations below to provide a more secure and efficient DNS
infrastructure. Please note that these recommendations focus on improving the
security of outbound DNS query or responses and do not encompass all DNS
security best practices.  

 * Configure operating systems and applications (including lower-tier DNS
   servers intended to forward queries to controlled enterprise DNS servers) to
   use only authorized DNS servers within the enterprise for outbound DNS
   resolution.
 * Configure enterprise perimeter network devices to block all outbound User
   Datagram Protocol (UDP) and Transmission Control Protocol (TCP) traffic to
   destination port 53, except from specific, authorized DNS servers (including
   both authoritative and caching/forwarding name servers).  
   * Additionally, filtering inbound destination port 53 TCP and UDP traffic to
     only allow connections to authorized DNS servers (including both
     authoritative and caching/forwarding name servers) will provide additional
     protections. 
 * Refer to Section 12 of the NIST Special Publication 800-81-2 for guidance
   when configuring enterprise recursive DNS resolvers. [1]


REFERENCES

[1] Secure Domain Name System (DNS) Deployment Guide


REVISIONS

August 28, 2015: Initial Release

This product is provided subject to this Notification and this Privacy &
Use policy.


PLEASE SHARE YOUR THOUGHTS

We recently updated our anonymous product survey; we’d welcome your feedback.


RELATED ADVISORIES

Sep 12, 2024
Alert


CISA RELEASES TWENTY-FIVE INDUSTRIAL CONTROL SYSTEMS ADVISORIES

Sep 12, 2024
Alert


ADOBE RELEASES SECURITY UPDATES FOR MULTIPLE PRODUCTS

Sep 12, 2024
Alert


CISCO RELEASES SECURITY UPDATES FOR IOS XR SOFTWARE

Sep 10, 2024
Alert


CISA RELEASES FOUR INDUSTRIAL CONTROL SYSTEMS ADVISORIES

Return to top
 * Topics
 * Spotlight
 * Resources & Tools
 * News & Events
 * Careers
 * About

Cybersecurity & Infrastructure Security Agency
 * Facebook
 * Twitter
 * LinkedIn
 * YouTube
 * Instagram
 * RSS

CISA Central 1-844-Say-CISA SayCISA@cisa.dhs.gov
DHS Seal
CISA.gov
An official website of the U.S. Department of Homeland Security
 * About CISA
 * Budget and Performance
 * DHS.gov
 * Equal Opportunity & Accessibility
 * FOIA Requests
 * No FEAR Act
 * Office of Inspector General
 * Privacy Policy
 * Subscribe
 * The White House
 * USA.gov
 * Website Feedback