DNSSEC: A Vision. Anil Sagar. Additional Director Indian Computer Emergency Response Team (CERT-In)



Similar documents
Part 5 DNS Security. SAST01 An Introduction to Information Security Martin Hell Department of Electrical and Information Technology

DNS at NLnet Labs. Matthijs Mekking

The Domain Name System from a security point of view

Domain Name System (DNS) Security By Diane Davidowicz 1999 Diane Davidowicz

The Impact of DNSSEC. Matthäus Wander. on the Internet Landscape. Duisburg, June 19, 2015

DNSSEC Applying cryptography to the Domain Name System

Internet-Praktikum I Lab 3: DNS

Computer Networks: Domain Name System

Lesson 13: DNS Security. Javier Osuna GMV Head of Security and Process Consulting Division

DOMAIN NAME SECURITY EXTENSIONS

DNS security: poisoning, attacks and mitigation

Using the Domain Name System for System Break-ins

Security in the Network Infrastructure - DNS, DDoS,, etc.

THE DOMAIN NAME SYSTEM DNS

Resilient Networking. Overview of DNS Known attacks on DNS Denial-of-Service Cache Poisoning. Securing DNS Split-Split-DNS DNSSEC.

FAQ (Frequently Asked Questions)

Lecture 2 CS An example of a middleware service: DNS Domain Name System

DNSSEC for Everybody: A Beginner s Guide

Secure Domain Name System (DNS) Deployment Guide

Deploying DNSSEC: From End-Customer To Content

DNSSEC - SECURE DNS FOR GOVERNMENT. Whitepaper

Presented by Greg Lindsay Technical Writer Windows Server Information Experience. Presented at: Seattle Windows Networking User Group April 7, 2010

DNS and BIND. David White

Security of IPv6 and DNSSEC for penetration testers

CS 356 Lecture 25 and 26 Operating System Security. Spring 2013

DNSSEC - Why Network Operators Should Care And How To Accelerate Deployment

Information Security Basic Concepts

Domain Name System (DNS) RFC 1034 RFC

HTG XROADS NETWORKS. Network Appliance How To Guide: DNS Delegation. How To Guide

Networking Domain Name System

DNS Cache Poisoning Vulnerability Explanation and Remedies Viareggio, Italy October 2008

DNS. Computer networks - Administration 1DV202. fredag 30 mars 12

DNSSEC. Introduction Principles Deployment

American International Group, Inc. DNS Practice Statement for the AIG Zone. Version 0.2

DNSSEC. Introduction. Domain Name System Security Extensions. AFNIC s Issue Papers. 1 - Organisation and operation of the DNS

BEST PRACTICES FOR IMPROVING EXTERNAL DNS RESILIENCY AND PERFORMANCE

WHITE PAPER. Best Practices DNSSEC Zone Management on the Infoblox Grid

Securing an Internet Name Server

How to Add Domains and DNS Records

Description: Objective: Attending students will learn:

INFORMATION SECURITY REVIEW

DNS Security: New Threats, Immediate Responses, Long Term Outlook Infoblox Inc. All Rights Reserved.

Securing DNS Infrastructure Using DNSSEC

5 DNS Security Risks That Keep You Up At Night (And How To Get Back To Sleep)

OVERVIEW OF THE DNS AND GLOSSARY OF TERMS

Developing Network Security Strategies

DNS. The Root Name Servers. DNS Hierarchy. Computer System Security and Management SMD139. Root name server. .se name server. .

Rough Outline. Introduction Why DNSSEC DNSSEC Theory Famous last words. Universiteit van Amsterdam, Sep 2006.

DNSSEC: The Antidote to DNS Cache Poisoning and Other DNS Attacks

Where is Hong Kong in the secure Internet infrastructure development. Warren Kwok, CISSP Internet Society Hong Kong 12 August 2011

THE MASTER LIST OF DNS TERMINOLOGY. v 2.0

Domain Name System Security

A Best Practices Architecture for DNSSEC

A Security Evaluation of DNSSEC with NSEC3

Ordinary DNS: A? k.root-servers.net. com. NS a.gtld-servers.net a.gtld-servers.net A Client's Resolver

Secure Domain Name System (DNS) Deployment Guide

DNSSEC Policy Statement Version Introduction Overview Document Name and Identification Community and Applicability

Network Security Fundamentals

A Systems Engineering Approach to Developing Cyber Security Professionals

APNIC elearning: Network Security Fundamentals. 20 March :30 pm Brisbane Time (GMT+10)

DNSSEC Practice Statement (DPS)

Domain Name System Security

Designing and Implementing a Server Infrastructure MOC 20413

DNS Risks, DNSSEC. Olaf M. Kolkman and Allison Mankin. and 8 Feb 2006 Stichting NLnet Labs

Creating the Conceptual Design by Gathering and Analyzing Business and Technical Requirements

Certified Ethical Hacker Exam Version Comparison. Version Comparison

Designing and Implementing a Server Infrastructure

Use Domain Name System and IP Version 6

Computer Networks: DNS a2acks CS 1951e - Computer Systems Security: Principles and Prac>ce. Domain Name System

DNSSEC. What is DNSSEC? Why is DNSSEC necessary? Ensuring a secure Internet

An Intrusion Detection System for Kaminsky DNS Cache poisoning

Passing PCI Compliance How to Address the Application Security Mandates

Configuring DNS. Finding Feature Information

Understanding DNS (the Domain Name System)

Understand Names Resolution

Defending your DNS in a post-kaminsky world. Paul Wouters <paul@xelerance.com>

Protection of DNS using HAVAL

DNSSEC in your workflow

Module 2. Configuring and Troubleshooting DNS. Contents:

Overview of Network Security The need for network security Desirable security properties Common vulnerabilities Security policy designs

Array Networks NetContinuum. Netli. Fine Ground. StrangeLoop. Akamai. Barracuda. Aptimize. Inkra. Nortel. Juniper. Cisco. Brocade/Foundry.

Transcription:

DNSSEC: A Vision Anil Sagar Additional Director Indian Computer Emergency Response Team (CERT-In)

Outline DNS Today DNS Attacks DNSSEC: An Approach Countering DNS Attacks Conclusion 2

DNS Today DNS is a distributed dynamic database application with a hierarchical structure and offering a dependable service Originally DNS design was focused on data availability and did not include it s security DNS major components: The Database Domain name space (DNS Tree) Resource Records The Server Name Server The Client Resolvers 3

DNS Namespace DNS uses a hierarchical namespace to locate computers. Root-level Domains.Country codes.com.edu.gov.net.org.mil Top-level Domains microsoft.com cisco.com Second-level Domains support.microsoft.com Sub-domains srv1.support.microsoft.com Host (FQDN) 4

DNS Attacks June 1997, Eugene Kashpureff (Alternic founder) redirected the internic.net domain to alternic.net by caching bogus information on the Internic name server In early February 2006, name servers hosting Top Level Domain zones were the repeated recipients of extraordinary heavy traffic loads On 6 February 2007, starting at 12:00 pm UTC, for approximately two-and-a-half hours, the system that underpins the Internet came under attack. Three-and-ahalf hours after the attack stopped, a second attack, this time lasting five hours, began 5

DNS Hacking Objectives Attacking DNS server data Attacking the DNS server 6

DNS Today: Potential Problems Original DNS design focused on data availability and did not include security DNS design included no authentication The DNS protocol does not allow you to check the validity of DNS data DNS data can be spoofed and corrupted between master server and resolver or forwarder 7

Securing DNS Built security into DNS systems TSIG Transactions Enhancements to secure Server-Server transactions DNS Security Extensions (DNSSEC) Enhancements to secure Server-Client transactions 8

DNSSEC: An Approach DNSSEC (short for Domain Name System Security Extensions) adds security to the Domain Name System s query / response Protects against unauthorised DNS data corruption and DNS spoofing It provides: origin authentication of DNS data data integrity but not confidentiality authenticated denial of existence It is designed to be interoperable with non-security aware implementations 9

DNSSEC: Characteristics Changes to DNS Protocol DNSSEC adds four new Resource Records (RR) KEYRR(DNSKEY): Key Resource Record specifies: the type of key (zone, host, user) the protocol (DNSSEC, IPSEC, TLS, etc.) the algorithm (RSA/MD5, DSA, etc.) SIGRR : Signature resource record specifies: the RR type covered (SOA, A, NS, MX, etc.) the algorithm (RSA/MD5, DSA, etc.) the inception & expiration times the signer key footprint DS: Delegation Signer a pointer to the next key in the chain of trust 10

DNSSEC: Characteristics NXTRR(NSEC): Next Secure the next name in the zone all the RR types covered by the current name The private key is kept off-line and is used to sign the RR sets of the zone file The public key is published in the KEY RR The public key of a zone is signed by the parent zone private key The parent zone signature on the zone s public key is added to the zone file 11

What DNSSEC does NOT do Does NOT provide confidentiality of DNS responses Does NOT protect against DDOS attacks Does NOT protect against IP Spoofing Is NOT about privacy Is NOT a PKI 12

DNSSEC Query Request for www.cnn.com Root Name server (. ) Reply [SIG (IP add & PK of.com server) by its private key] DNS Server Request for ww.cnn.com Reply [SIG (IP add & PK of cnn.com server) by its private key] Top-level Domain Authoritative Server (.com) Request for www.cnn.com Reply Request for ww.cnn.com Reply [SIG (x.x.x.x) by its private key Second-level Authoritative Server (cnn.com) Client 13

DNSSEC Response Validation Validation of a DNS response: Did the matching private key sign the RRSIG RR? Does the hash match the RR data? Does the public key validate? Does the parent have a DS RR? Has the Parent signed the matching RRSIG RR? Does the parent s key validate? Loop until you get to a recognised trust anchor This interlocking of parent signing over child is a critical aspect of the robustness of DNSSEC. It s also DNSSEC s major weakness in today s partial DNSSEC deployment world 14

DNSSEC: Chain of Trust Request for www.cnn.com Root Name server (. ) Reply [SIG (IP add & PK of.com server) by its private key] DNS Server Request for ww.cnn.com Reply [SIG (IP add & PK of cnn.com server) by its private key] Top-level Domain Authoritative Server (.com) Request for www.cnn.com Reply Request for ww.cnn.com Reply [SIG (x.x.x.x) by its private key Second-level Authoritative Server (cnn.com) Client 15

DNSSEC: Chain of Trust Request for KEY for.com Reply KEY, SIG RR of.com Top-level Domain Authoritative Server (.com) Client Second-level Authoritative Server (cnn.com) 16

DNS Defenses Protocol Based Exploits DNS reconnaissance Protocol-based denial-ofservice Dynamic DNS (DDNS) hacking Defense Split-level DNS topologies Network and Name Server monitoring, intrusion detection DNSSEC digital signatures to secure DNS data Server-side access controls Configuration audit and verification tools Split-level DNS topologies DNS redundancy Stateful firewalling Server-side access controls Network and Name Server monitoring, intrusion detection Patches and service packs Split-level DNS topologies Network and Name Server monitoring, intrusion detection Server-side access controls for DDNS DNSSEC: authentication of DDNS requests Configuration audit and verification tools Patches and service packs 17

DNS Defenses Application Based Exploit Buffer overflow attacks Defense System and service hardening Network and Name Server monitoring, intrusion detection Stateful firewalling Split-level DNS topologies DNS redundancy Patches and service packs Third-party application-layer security tools 18

DNS Defenses Trust Based Exploits DNS registration hacking DNS spoofing Defense Imposition of registration controls Split-level DNS topologies Stateful firewalling Server-side access controls Network and Name Server monitoring, intrusion detection DNSSEC digital signatures to secure DNS data Patches and service packs Upgrade to latest version(s) of Name Server software (protections against DNS ID hacking) Cache poisoning DNS hijacking Split-level DNS topologies Stateful firewalling Server-side access controls Network and Name Server monitoring, intrusion detection DNSSEC digital signatures to secure DNS data Patches and service packs Split-level DNS topologies Stateful firewalling Server-side access controls Network and Name Server monitoring, intrusion detection DNSSEC digital signatures to secure DNS data Patches and service packs 19

DNSSEC: Deployments DNSSEC test deployment at IANA This data, including the signed zones, are purely for test purposes and are not to be used in any production capacity DNSSEC testbed in Sweden (.se) Russia (.ru) United Kingdom (.uk) Mexico (.mx) Puerto Rico (.pr) Netherlands (.nl) Bulgaria (.bg) Brasil (.br) Malaysia (.my) VeriSign 20

Why DNSSEC is important? Is this ROI or Return on Risk? Total dependence on DNS for the functioning of Internet Low security awareness Rise in threats How costly is the exploitation that occurs if we don t have this protection? 21

Refrences http://www.dnssec.net http://www.dnssec-deployment.org http://www.ripe.net http://www.icann.org RFCs: 4033, 4034, 4035 and 3833 22

Thank you anil@cert-in.org.in Incident Response HelpDesk Phone: 1800 11 4949 FAX: 1800 11 6969 e-mail: incident@cert-in.org.in http://www.cert-in.org.in 23