DOCSLIB.ORG

GNSO Issues Report on Domain Tasting

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GNSO Issues Report on Domain Tasting Draft Final Report on Fast Flux Hosting Date: Deleted: Initial 1 2 3 22 Deleted: Initial 4 [Draft] Final Report of the 5 GNSO Fast Flux Hosting Working Group 6 7 8 9 10 STATUS OF THIS DOCUMENT 11 This is the [Draft] Final Report of the Working Group on fast flux hosting, for submission to the GNSO 23 Deleted: Initial 12 Council on [date] following public comments on the Initial Report of 26 January 2009. 24 Deleted: 26 January 2009 13 25 Deleted: A Final Report will be prepared 26 following public comment.¶ 14 15 16 17 18 SUMMARY 19 This report is submitted to the GNSO Council following public comments to the Initial Report as a 20 required step in the GNSO Policy Development Process on Fast Flux Hosting. 21 Deleted: Initial Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 1 of 151 Draft Final Report on Fast Flux Hosting Date: Deleted: Initial 45 Deleted: ¶ 46 This report is submitted to the GNSO 27 TABLE OF CONTENTS 47 Council and posted for public comment as a 48 required step in this GNSO Policy 49 Development Process on Fast Flux Hosting. 50 Deleted: ¶ 28 1 EXECUTIVE SUMMARY 3 51 ¶ 52 ¶ 29 2 REPORT PROCESS AND NEXT STEPS 15 30 3 BACKGROUND 16 31 4 APPROACH TAKEN BY THE WORKING GROUP 22 32 5 DISCUSSION OF CHARTER QUESTIONS 25 33 6 PUBLIC COMMENT PERIOD 53 34 7 CHALLENGES 66 35 8 CONCLUSIONS 69 36 9 RECOMMENDED NEXT STEPS 71 37 ANNEX I – CONSTITUENCY INPUT TEMPLATE 74 38 ANNEX II - CONSTITUENCY STATEMENTS (SUMMARY)76 39 ANNEX III – CONSTITUENCY STATEMENTS (FULL) 78 40 ANNEX IV FAST FLUX CASE STUDY 105 41 ANNEX V – FAST FLUX METRICS 106 42 ANNEX VI THE MANNHEIM FORMULA 115 43 ANNEX VII– INDIVIDUAL STATEMENTS 124 44 ANNEX VIII – FAST FLUX WG ATTENDANCE SHEET 150 Deleted: Initial Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 2 of 151 Draft Final Report on Fast Flux Hosting Date: Deleted: Initial 87 Deleted: Page Break 53 1 Executive summary 88 Deleted: Section Break (Continuous) 54 55 1.1. Background 56 . Following the publication of the SSAC Advisory on Fast Flux Hosting and DNS (SAC 57 025) in January 2008, the GNSO Council instructed ICANN staff on 6 March 2008 to 58 prepare and Issues Report which ‗shall consider the SAC Advisory [SAC 025], and shall 59 outline potential next steps for GNSO policy development designed to mitigate the 60 current ability for criminals to exploit the DNS via ‗fast flux‘ IP or nameserver changes‘. 61 . The issues report was published on 31 March 2008 and recommended ―the GNSO 62 sponsor further fact-finding and research concerning guidelines for industry best 63 practices before considering whether or not to initiate a formal policy development 64 process‖. 65 . At its 8 May 2008 meeting, the GNSO Council initiated a formal policy development 66 process (PDP) and called for the creation of a working group on fast flux. The working 67 group charter was approved on 29 May 2008 and asked the working group to consider 68 the following questions: 69 - Who benefits from fast flux, and who is harmed? 70 - Who would benefit from cessation of the practice and who would be harmed? 71 - Are registry operators involved, or could they be, in fast flux hosting activities? If so, 72 how? 73 - Are registrars involved in fast flux hosting activities? If so, how? 74 - How are registrants affected by fast flux hosting? 75 - How are Internet users affected by fast flux hosting? 76 - What technical (e.g. changes to the way in which DNS updates operate) and policy 77 (e.g. changes to registry/registrar agreements or rules governing permissible 78 registrant behavior) measures could be implemented by registries and registrars to 79 mitigate the negative effects of fast flux? 80 - What would be the impact (positive or negative) of establishing limitations, 81 guidelines, or restrictions on registrants, registrars and/or registries with respect to 82 practices that enable or facilitate fast flux hosting? 83 - What would be the impact of these limitations, guidelines, or restrictions to product 84 and service innovation? 85 - What are some of the best practices available with regard to protection from fast 86 flux? Deleted: Initial Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 3 of 151 Draft Final Report on Fast Flux Hosting Date: Deleted: Initial 89 The Group was also tasked to obtain expert opinion, as appropriate, on which areas of fast 90 flux are in scope and out of scope for GNSO policy making. 91 92 1.2. Approach taken by the Working Group 93 . The Fast Flux Working Group started its deliberations on 26 June 2008 and decided to 94 start working on answering the charter questions in parallel to the preparation of 95 constituency statements on this topic. In order to facilitate the feedback from the 96 constituencies, a template was developed for responses (see Annex I). In addition to 97 weekly conference calls, extensive dialogue occurred through the fast flux mailing list 98 with over 800 messages posted. 99 . Except where marked differently, the positions outlined in this document should be 100 considered in agreement by the Working Group. Where no broad agreement could be 101 reached, the following labels have been used to indicate the level of support for a certain 102 position: 103 - Support – there is some gathering of positive opinion, but competing positions may 104 exist and broad agreement has not been reached. 105 - Alternative view – a differing opinion that has been expressed, without garnering 106 enough following within the WG to merit the notion of either Support or Agreement. It 107 should be noted that an alternative view could be expressed where there is broad 108 agreement as well as support. 109 . The Initial Report was published on 26 January 2009 and was followed by a public 110 comment period as prescribed in the ICANN by-laws. 111 112 1.3. Discussion of Charter Questions 113 . After considerable deliberation, the working group was able to identify positive 114 applications of certain characteristics generally associated with the term fast flux hosting. 115 These adaptive networking characteristics, including short TTLs and frequent update of 116 DNS records, are present in production networking environments that are high profile, 117 support mobility, or are likely-targets of attacker, or network that must be adaptive and 118 resilient. Such self-beneficial or positive applications are described in the literature as 119 ‗volatile networking‘. Generally, additional, sufficiently different and suspicious 120 characteristics are present in malicious networking applications to distinguish positive, 121 volatile networks from fast flux attack networks. Deleted: Initial Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 4 of 151 Draft Final Report on Fast Flux Hosting Date: Deleted: Initial 122 . A fast flux attack network, for the purposes of the working group exhibits the following 155 Deleted: 123 characteristics: 124 Some but not necessarily all of the network nodes are operated on compromised 125 hosts (i.e., using software that was installed on hosts without notice or consent to the 126 system operator/owner); 127 Is ‗volatile‘ in the sense that the active nodes of the network change in order to 128 sustain the network‘s lifetime, facilitate the spread of the network software 129 components, and to conduct other attacks; and 130 Uses a variety of techniques to achieve volatility including: 131 - rapid and repeated selection of systems from a pool of botted hosts, with those 132 systems being used for the purpose of serving malicious content, for use as 133 name servers, and for other purposes, all via DNS entries with low TTLs; 134 - dispersing network nodes across a wide number of consumer grade autonomous 135 systems; 136 - monitoring member nodes to determine/conclude that a host has been identified 137 and shut down; and 138 - time, or other metric-based, topology changes to network nodes, name server, 139 proxy targets or other components. 140 Additional characteristics that in combination or collectively have been used to 141 distinguish or ―fingerprint‖ a fast flux hosting attack include: 142 - multiple IPs per NS spanning multiple ASNs, 143 - frequent NS changes, 144 - in-addrs.arpa or IPs lying within consumer broadband allocation blocks, 145 - domain name age, 146 - poor quality WHOIS, 147 - determination that the nginx proxy is running on the addressed machine: nginx is 148 commonly used to hide/proxy illegal web servers, 149 - the domain name is one of possibly many domain names under the name of a 150 registrant whose domain administration account has been compromised, and the 151 attacker has altered domain name information without authorization. 152 . The distribution and use of software installed on hosts without notice to or consent of the 153 system operator/owner is a critically important characteristic of a fast flux attack network; 154 in particular, it is one among several characteristics that distinguish fast flux attack Deleted: Initial Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 5 of 151 Draft Final Report on Fast Flux Hosting Date: Deleted: Initial 156 networks from production uses of fast flux techniques in applications such as content 157 distribution networking, high availability and resilient networking, etc. 158 . When used by criminals, the main goal of fast-flux hosting is to prolong the period of time 159 during which the attack continues to be effective. It is not an attack itself – it is a way for 160 an attacker to avoid detection and frustrate the response to the attack. 161 . The WG offers the following initial working answers to the charter questions but would 162 like to emphasize that continued work is required in the following areas: 163 - A robust technical, and process, definition of ―fast flux‖, 164 - Reliable techniques to detect fast flux networks while maintaining an acceptable rate 165 of false positives, 166 - Reliable information as to the scope and penetration of fast flux networks, 167 - Reliable information as to the financial and non-financial impact of fast flux networks 168 .
Load more

Recommended publications
  • Click Trajectories: End-To-End Analysis of the Spam Value Chain
    Click Trajectories: End-to-End Analysis of the Spam Value Chain ∗ ∗ ∗ ∗ z y Kirill Levchenko Andreas Pitsillidis Neha Chachra Brandon Enright Mark´ Felegyh´ azi´ Chris Grier ∗ ∗ † ∗ ∗ Tristan Halvorson Chris Kanich Christian Kreibich He Liu Damon McCoy † † ∗ ∗ Nicholas Weaver Vern Paxson Geoffrey M. Voelker Stefan Savage ∗ y Department of Computer Science and Engineering Computer Science Division University of California, San Diego University of California, Berkeley z International Computer Science Institute Laboratory of Cryptography and System Security (CrySyS) Berkeley, CA Budapest University of Technology and Economics Abstract—Spam-based advertising is a business. While it it is these very relationships that capture the structural has engendered both widespread antipathy and a multi-billion dependencies—and hence the potential weaknesses—within dollar anti-spam industry, it continues to exist because it fuels a the spam ecosystem’s business processes. Indeed, each profitable enterprise. We lack, however, a solid understanding of this enterprise’s full structure, and thus most anti-spam distinct path through this chain—registrar, name server, interventions focus on only one facet of the overall spam value hosting, affiliate program, payment processing, fulfillment— chain (e.g., spam filtering, URL blacklisting, site takedown). directly reflects an “entrepreneurial activity” by which the In this paper we present a holistic analysis that quantifies perpetrators muster capital investments and business rela- the full set of resources employed to monetize spam email— tionships to create value. Today we lack insight into even including naming, hosting, payment and fulfillment—using extensive measurements of three months of diverse spam data, the most basic characteristics of this activity. How many broad crawling of naming and hosting infrastructures, and organizations are complicit in the spam ecosystem? Which over 100 purchases from spam-advertised sites.
    [Show full text]
  • Passive Monitoring of DNS Anomalies Bojan Zdrnja1, Nevil Brownlee1, and Duane Wessels2
    Passive Monitoring of DNS Anomalies Bojan Zdrnja1, Nevil Brownlee1, and Duane Wessels2 1 University of Auckland, New Zealand, b.zdrnja,nevil @auckland.ac.nz { } 2 The Measurement Factory, Inc., [email protected] Abstract. We collected DNS responses at the University of Auckland Internet gateway in an SQL database, and analyzed them to detect un- usual behaviour. Our DNS response data have included typo squatter domains, fast flux domains and domains being (ab)used by spammers. We observe that current attempts to reduce spam have greatly increased the number of A records being resolved. We also observe that the data locality of DNS requests diminishes because of domains advertised in spam. 1 Introduction The Domain Name System (DNS) service is critical for the normal functioning of almost all Internet services. Although the Internet Protocol (IP) does not need DNS for operation, users need to distinguish machines by their names so the DNS protocol is needed to resolve names to IP addresses (and vice versa). The main requirements on the DNS are scalability and availability. The DNS name space is divided into multiple zones, which are a “variable depth tree” [1]. This way, a particular DNS server is authoritative only for its (own) zone, and each organization is given a specific zone in the DNS hierarchy. A complete domain name for a node is called a Fully Qualified Domain Name (FQDN). An FQDN defines a complete path for a domain name starting on the leaf (the host name) all the way to the root of the tree. Each node in the tree has its label that defines the zone.
    [Show full text]
  • Sidekick Suspicious Domain Classification in the .Nl Zone
    Master Thesis as part of the major in Security & Privacy at the EIT Digital Master School SIDekICk SuspIcious DomaIn Classification in the .nl Zone delivered by Moritz C. M¨uller [email protected] at the University of Twente 2015-07-31 Supervisors: Andreas Peter (University of Twente) Maarten Wullink (SIDN) Abstract The Domain Name System (DNS) plays a central role in the Internet. It allows the translation of human-readable domain names to (alpha-) numeric IP addresses in a fast and reliable manner. However, domain names not only allow Internet users to access benign services on the Internet but are used by hackers and other criminals as well, for example to host phishing campaigns, to distribute malware, and to coordinate botnets. Registry operators, which are managing top-level domains (TLD) like .com, .net or .nl, disapprove theses kinds of usage of their domain names because they could harm the reputation of their zone and would consequen- tially lead to loss of income and an insecure Internet as a whole. Up to today, only little research has been conducted with the intention to fight malicious domains from the view of a TLD registry. This master thesis focuses on the detection of malicious domain names for the .nl country code TLD. Therefore, we analyse the characteristics of known malicious .nl domains which have been used for phishing and by botnets. We confirm findings from previous research in .com and .net and evaluate novel characteristics including query patterns for domains in quar- antine and recursive resolver relations. Based on this analysis, we have developed a prototype of a detection system called SIDekICk.
    [Show full text]
  • Proactive Cyberfraud Detection Through Infrastructure Analysis
    PROACTIVE CYBERFRAUD DETECTION THROUGH INFRASTRUCTURE ANALYSIS Andrew J. Kalafut Submitted to the faculty of the Graduate School in partial fulfillment of the requirements for the degree Doctor of Philosophy in Computer Science Indiana University July 2010 Accepted by the Graduate Faculty, Indiana University, in partial fulfillment of the requirements of the degree of Doctor of Philosophy. Doctoral Minaxi Gupta, Ph.D. Committee (Principal Advisor) Steven Myers, Ph.D. Randall Bramley, Ph.D. July 19, 2010 Raquel Hill, Ph.D. ii Copyright c 2010 Andrew J. Kalafut ALL RIGHTS RESERVED iii To my family iv Acknowledgements I would first like to thank my advisor, Minaxi Gupta. Minaxi’s feedback on my research and writing have invariably resulted in improvements. Minaxi has always been supportive, encouraged me to do the best I possibly could, and has provided me many valuable opportunities to gain experience in areas of academic life beyond simply doing research. I would also like to thank the rest of my committee members, Raquel Hill, Steve Myers, and Randall Bramley, for their comments and advice on my research and writing, especially during my dissertation proposal. Much of the work in this dissertation could not have been done without the help of Rob Henderson and the rest of the systems staff. Rob has provided valuable data, and assisted in several other ways which have ensured my experiments have run as smoothly as possible. Several members of the departmental staff have been very helpful in many ways. Specifically, I would like to thank Debbie Canada, Sherry Kay, Ann Oxby, and Lucy Battersby.
    [Show full text]
  • Fast-Flux Botnet Detection Based on Traffic Response and Search Engines Credit Worthiness
    ISSN 1330-3651 (Print), ISSN 1848-6339 (Online) https://doi.org/10.17559/TV-20161012115204 Original scientific paper Fast-Flux Botnet Detection Based on Traffic Response and Search Engines Credit Worthiness Davor CAFUTA, Vlado SRUK, Ivica DODIG Abstract: Botnets are considered as the primary threats on the Internet and there have been many research efforts to detect and mitigate them. Today, Botnet uses a DNS technique fast-flux to hide malware sites behind a constantly changing network of compromised hosts. This technique is similar to trustworthy Round Robin DNS technique and Content Delivery Network (CDN). In order to distinguish the normal network traffic from Botnets different techniques are developed with more or less success. The aim of this paper is to improve Botnet detection using an Intrusion Detection System (IDS) or router. A novel classification method for online Botnet detection based on DNS traffic features that distinguish Botnet from CDN based traffic is presented. Botnet features are classified according to the possibility of usage and implementation in an embedded system. Traffic response is analysed as a strong candidate for online detection. Its disadvantage lies in specific areas where CDN acts as a Botnet. A new feature based on search engine hits is proposed to improve the false positive detection. The experimental evaluations show that proposed classification could significantly improve Botnet detection. A procedure is suggested to implement such a system as a part of IDS. Keywords: Botnet; fast-flux; IDS 1 INTRODUCTION locations DoS attack against the web site becomes very difficult as it must be effective on every server in the field The Domain Name System (DNS) is a hierarchical [7, 8].
    [Show full text]
  • Detection of Fast-Flux Networks Using Various DNS Feature Sets
    Detection of Fast-Flux Networks Using Various DNS Feature Sets Z. Berkay Celik and Serna Oktug Department of Computer Engineering Istanbul Technical University Maslak, Istanbul, Turkey 34469 { zbcelik,oktug}@itu.edu.tr Abstract-In this work, we study the detection of Fast-Flux imperfect, e.g., they may suffer from high detection latency Service Networks (FFSNs) using DNS (Domain Name System) (i.e., extracting features as a timescale greater than Time response packets. We have observed that current approaches do To Live (TTL), or multiple DNS lookups) or false positives not employ a large combination of DNS features to feed into detected by utilizing imperfect and insufficient features. the proposed detection systems. The lack of features may lead to high false positive or false negative rates triggered by benign The work presented here is related to the detection of activities including Content Distribution Networks (CDNs). In FFSNs, in particular, by jointly building timing, domain name, this paper, we study recently proposed detection frameworks to spatial, network and DNS answer features which are extracted construct a high-dimensional feature vector containing timing, network, spatial, domain name, and DNS response information. from the first DNS response packet. We consider many rather In the detection system, we strive to use features that are delay­ than a few features and also their combinations which are free, and lightweight in terms of storage and computational constructed by surveying the recent literature. The main aim of cost. Feature sub-spaces are evaluated using a C4.5 decision tree this survey is to study and analyze the benefits of the features classifier by excluding redundant features using the information and also, in some cases, the necessity of applying joint feature gain of each feature with respect to each class.
    [Show full text]
  • Acceptable Use and Takedown Policy
    ACCEPTABLE USE AND TAKEDOWN POLICY BNP Paribas (“the Registry”) as the operator of the TLD .bnpparibas attaches great value to the secure use and usability of the services available under the TLD .bnpparibas. Abuses of .bnpparibas are a threat to the stability and security of the Registry, registrars, registrants and the security of Internet users generally. This Acceptable Use Policy (« AUP ») sets forth the terms and conditions for the use by a Registrant of any domain name registered or renewed under .bnpparibas. The Registry reserves the right to modify or amend this AUP at any time in order to comply with applicable laws and terms and/or any conditions set forth by ICANN. Acceptable Use Overview All domain name registrants must act responsibly in their use of any .bnpparibas domain or website hosted on any .bnpparibas domain, and in accordance with this policy, ICANN registry agreement, and applicable laws, including those that relate to privacy, data collection, consumer protection (including in relation to misleading and deceptive conduct), fair lending, and intellectual property rights. The Registry will not tolerate abusive, malicious, or illegal conduct in registration of a domain name; nor will the Registry tolerate such content on a website hosted on a .bnpparibas domain name. This AUP will govern the Registry’s actions in response to abusive, malicious, or illegal conduct of which the Registry becomes aware. The Registry reserves the right to bring the offending sites into compliance using any of the methods described herein, or others as may be necessary in the Registry’s discretion, whether or not described in this Acceptable Use Policy.
    [Show full text]
  • Fast-Flux Networks While Considering Domain-Name Parking
    Proceedings Learning from Authoritative Security Experiment Results LASER 2017 Arlington, VA, USA October 18-19, 2017 Proceedings of LASER 2017 Learning from Authoritative Security Experiment Results Arlington, VA, USA October 18–19, 2017 ©2017 by The USENIX Association All Rights Reserved This volume is published as a collective work. Rights to individual papers remain with the author or the author’s employer. Permission is granted for the noncommercial reproduction of the complete work for educational or research purposes. Permission is granted to print, primarily for one person’s exclusive use, a single copy of these Proceedings. USENIX acknowledges all trademarks herein. ISBN 978-1-931971-41-6 Table of Contents Program . .. v Organizing Committee . vi Program Committee . vi Workshop Sponsors . vii Message from the General Chair . viii Program Understanding Malware’s Network Behaviors using Fantasm . 1 Xiyue Deng, Hao Shi, and Jelena Mirkovic, USC/Information Sciences Institute Open-source Measurement of Fast-flux Networks While Considering Domain-name Parking . 13 Leigh B. Metcalf, Dan Ruef, and Jonathan M. Spring, Carnegie Mellon University Lessons Learned from Evaluating Eight Password Nudges in the Wild . 25 Karen Renaud and Joseph Maguire, University of Glasgow; Verena Zimmerman, TU Darmstadt; Steve Draper, University of Glasgow An Empirical Investigation of Security Fatigue: The Case of Password Choice after Solving a CAPTCHA . 39 Kovila P.L. Coopamootoo and Thomas Gross, Newcastle University; Muhammad F. R. Pratama Dead on Arrival: Recovering from Fatal Flaws in Email Encryption Tools . 49 Juan Ramón Ponce Mauriés, University College London; Kat Krol, University of Cambridge; Simon Parkin, Ruba Abu-Salma, and M.
    [Show full text]
  • PREDATOR: Proactive Recognition and Elimination of Domain Abuse at Time-Of-Registration
    PREDATOR: Proactive Recognition and Elimination of Domain Abuse at Time-Of-Registration Shuang Hao∗ Alex Kantcheliany Brad Millerx Vern Paxson† Nick Feamsterz ∗ y University of California, Santa Barbara University of California, Berkeley x z Google, Inc. International Computer Science Institute Princeton University [email protected] {akant,vern}@cs.berkeley.edu [email protected] [email protected] ABSTRACT content [18, 53]. To mitigate these threats, operators routinely build Miscreants register thousands of new domains every day to launch reputation systems for domain names to indicate whether they are Internet-scale attacks, such as spam, phishing, and drive-by down- associated with malicious activity. A common mode for developing loads. Quickly and accurately determining a domain’s reputation reputation for DNS domain names is to develop a blacklist that curates (association with malicious activity) provides a powerful tool for mit- “bad domains”. A network operator who wishes to defend against an igating threats and protecting users. Yet, existing domain reputation attack may use a domain blacklist to help determine whether certain systems work by observing domain use (e.g., lookup patterns, content traffic or infrastructure is associated with malicious activity. hosted)—often too late to prevent miscreants from reaping benefits of Unfortunately, curating a DNS blacklist is difficult because of the attacks that they launch. the high rate of domain registrations and the variety of attacks. For As a complement to these systems, we explore the extent to which example, every day around 80,000 new domains are registered in features evident at domain registration indicate a domain’s subsequent the .com zone, with a peak rate of over 1,800 registrations in a sin- use for malicious activity.
    [Show full text]
  • Botnet Detection Using Passive DNS
    Botnet Detection Using Passive DNS Master Thesis Pedro Marques da Luz [email protected] Supervisors: Erik Poll (RU) Harald Vranken (RU & OU) Sicco Verwer (TUDelft) Barry Weymes (Fox-IT) Department of Computing Science Radboud University Nijmegen 2013/2014 Abstract The Domain Name System (DNS) is a distributed naming system fundamental for the normal operation of the Internet. It provides a mapping between user-friendly domain names and IP addresses. Cyber criminals use the flexibility provided by the DNS to deploy certain techniques that allow them to hide the Command and Control (CnC) servers used to manage their botnets and frustrate the detection efforts. Passive DNS (pDNS) data allows us to analyse the DNS history of a given domain name. Such is achieved by passively collecting DNS queries and the respective answers that can then be stored and easily queried. By analyzing pDNS data, one can try to follow the traces left by such techniques and be able to identify the real addresses of the botnet Command and Control servers. For instance, we expect malware-related domain names to have lower Time-to-Live (TTL) values than legitimate and benign domains. The aim of this research is the development of a proof-of-concept able to automatically analyze and identify botnet activity using pDNS data. We propose the use of machine learning techniques and devise a set of 36 different features to be used in the classification process. With two weeks of pDNS data we were able to set up, create and test different classifiers, namely k-Nearest Neighbours (kNN), Decision Trees and Random Forests.
    [Show full text]
  • Fast Flux Final Report
    Final Report on Fast Flux Hosting Date: 6 August 2009 Final Report of the GNSO Fast Flux Hosting Working Group STATUS OF THIS DOCUMENT This is the Final Report of the Working Group on fast flux hosting, for submission to the GNSO Council on 6 August 2009 following public comments on the Initial Report of 26 January 2009. SUMMARY This report is submitted to the GNSO Council following public comments to the Initial Report as a required step in the GNSO Policy Development Process on Fast Flux Hosting. Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 1 of 154 Final Report on Fast Flux Hosting Date: 6 August 2009 TABLE OF CONTENTS 1! EXECUTIVE SUMMARY 3! 2! REPORT PROCESS AND NEXT STEPS 15! 3! BACKGROUND 16! 4! APPROACH TAKEN BY THE WORKING GROUP 22! 5! DISCUSSION OF CHARTER QUESTIONS 25! 6! PUBLIC COMMENT PERIOD 54! 7! CHALLENGES 67! 8! CONCLUSIONS 69! 9! RECOMMENDED NEXT STEPS 71! ANNEX I CONSTITUENCY INPUT TEMPLATE 74! ANNEX II CONSTITUENCY STATEMENTS (SUMMARY) 76! ANNEX III CONSTITUENCY STATEMENTS (FULL) 78! ANNEX IV!!!!!FAST FLUX CASE STUDY 105! ANNEX V FAST FLUX METRICS 106! ANNEX VI THE MANNHEIM FORMULA 115! ANNEX VII INDIVIDUAL STATEMENTS 124! ANNEX VIII FAST FLUX WG ATTENDANCE SHEET 152 Draft Final Report on Fast Flux Hosting Author: Marika Konings Page 2 of 154 Final Report on Fast Flux Hosting Date: 6 August 2009 1 Executive summary 1.1. Background ! Following the publication of the SSAC Advisory on Fast Flux Hosting and DNS (SAC 025) in January 2008, the GNSO Council instructed ICANN staff on 6 March 2008 to prepare and Issues Report which ‘shall consider the SAC Advisory [SAC 025], and shall outline potential next steps for GNSO policy development designed to mitigate the current ability for criminals to exploit the DNS via fast flux IP or nameserver changes’.
    [Show full text]
  • Powerpoint Presentation
    SSAC since last RIPE 55 ICANN SSAC What is SSAC? • The Security and Stability Advisory Committee advises the ICANN community and Board on matters relating to the security and integrity of the Internet's naming and address allocation systems. – operational matters – administrative matters – registration matters • http://www.icann.org/committees/security/ SSAC Members Stephen Crocker <[email protected]> – Chair Dave Piscitello <[email protected]> – ICANN Senior Security Technologist Jim Galvin <[email protected]> – eList eXpress Alain Aina (Consultant) Russ Mundy (SPARTA, Inc.) Jaap Akkerhuis (NLnet Labs) Frederico Neves (NIC.br) Jeffrey Bedser (Internet Crimes Group) Ray Plzak (ARIN), Vice-Chair Lyman Chapin (Interisle), RSTEP Liaison Ramaraj Rajashekhar (Sequoia Capital, India) KC Claffy (CAIDA) Barbara Roseman (ICANN), IANA Liaison Steve Conte (ICANN) Mike St. Johns Patrik Faltstrom (Cisco Systems) Shinta Sato (JPRS) Robert Guerra (Privaterra), ALAC Liaison Mark Seiden (Yahoo!) Rodney Joffe (Neustar) Doron Shikmoni (ForeScout, ISOC-IL) Olaf Kolkman (NLNet Labs), IAB Point of Contact Bruce Tonkin (Melbourne IT) Mark Kosters (ARIN) Stefano Trumpy (IIT/CNR), GAC Liaison Warren Kumari (Google) Paul Vixie (ISC) Matt Larson (VeriSign) Rick Wesson (Support Intelligence) Danny McPherson (Arbor Networks, Inc.) Suzanne Woolf (ISC) Ram Mohan (Afilias) A few reports have been released • [SAC022]:Domain Name Front Running • [SAC023]:Is the WHOIS Service a Source for email Addresses for Spammers? • [SAC024]:Report on Domain Name
    [Show full text]