Top Banner
Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA
16

Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Dec 13, 2015

Download

Documents

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Recursive DNS Cache Auditing

Jose Avila IIIFounder, ONZRA

Page 2: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Who Am I?

•One of the founders of ONZRA

•Security Researcher

•Previous Lead Developer at NeuStar for the Managed Internal DNS and SiteBacker2 products

Page 3: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Cache Poisoning Is Not New!

•We find out we were poisoned when services start failing!

•There is a need for a notification system

•Why aren’t there solutions to detect this?

Page 4: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Where Does ONZRA Fit In?

•Developing a Cache Verification Tool

•Verifies changes seen in cache

•Alert on potential Cache Poisoning Events

•Similar to DoX concept

Page 5: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

How Does It Work?

•Takes a dump of the in-memory cache

•Finds differences with an old dump

•Verifies the changes

•Checks authoritative servers

•Checks peer recursive servers

•Alerts if results could not be verified

Page 6: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Features

•Recordset comparison

•Content Delivery Network detection

•Record type based comparison

•Threshold based peer approval

•History tracking

•Alerting based on percentage of change

Page 7: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Content Delivery Network Detection

•Detected by comparing the record sets amongst the peers

•Can lower the alert level

Page 8: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Record Comparison

•Ordering of records does not matter

•We don’t have to verify everything

•What we do not verify:

•MX Record: Preference

•SOA Record: Serial, etc.

Page 9: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Threshold Based Peer Approval

• Based on the threshold of required peers we need to alter our probing interval.

• If too much time passes we will not be able to verify with peers

Page 10: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Probe Interval

•Verify Freq. = TTL-(THRESHxTTL/PEERS)

•Verifying against:

•20 Peers

•10% Threshold

•120s Min TTL

•Need to verify cache every 108 seconds

Page 11: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

History Tracking

•Stores a history of prior record sets

•If the record is not verified by peers its verified against historic values

Page 12: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Detecting Fast Flux

•Value changing quicker than the TTL

•Peers will have multiple values represented

•Screws up prior formula

•How can we verify these?

•Shared DB of historic data?

Page 13: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Tool Components

•TCP Daemon (Listens for Cache Dumps)

•Cache Dump Parsers

•Cache Compare

•Application Cache

•CDN / Fast Flux Detection

•Alerter (Currently only SYSLOG)

Page 14: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

What Resolvers Are Supported?

•Currently Supported

•Microsoft DNS

•Bind

•Supported eventually

•DJB DNS w/ custom Patch

•PowerDNS

Page 15: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Future Features

•Cache Verification Service?

•More Research Data

•Multiple Query Nodes

•Better CDN Detection

•Use peer cache dumps instead of querying

•Interaction with other DNS Projects

Page 16: Recursive DNS Cache Auditing Jose Avila III Founder, ONZRA.

Questions?

[email protected]@ONZRA.com