Changes

Line 93: Line 93:  
===Internet Governance Organizations===
 
===Internet Governance Organizations===
 
====ICANN====
 
====ICANN====
So far, ICANN has been steadfast in its focus on technical DNS abuse and avoidance of policymaking around content abuse. ICANN's determination of the org's definition for DNS Abuse is based on the work product of GAC and the base gTLD Registry Agreement. Thus, ICANN considers DNS security threats to be limited to attacks involving phishing, malware, botnet command and control, pharming, and spam as a vector.<ref>[https://www.icann.org/en/blogs/details/update-on-icanns-dns-security-threat-mitigation-program-19-7-2021-en Update on DNS Security Threats, ICANN Org]</ref> As recently as [[ICANN 71]], the ICANN board was criticized by members of the [[ALAC]], the [[BC]], and other [[Internet Governance]] bodies for not doing enough to steward contracted parties and non-contracted parties toward involvement in reducing abuse. However, ICANN and [[SSAC]], in particular, have begun pointing to [[SAC115]] and [[DAAR]] as evidence of their work on addressing DNS abuse.
+
ICANN has been steadfast in its focus on technical DNS abuse and avoidance of policymaking around content abuse. ICANN's determination of the org's definition for DNS Abuse is based on the work product of GAC and the base gTLD Registry Agreement. Thus, ICANN considers DNS security threats to be limited to attacks involving phishing, malware, botnet command and control, pharming, and spam as a vector.<ref>[https://www.icann.org/en/blogs/details/update-on-icanns-dns-security-threat-mitigation-program-19-7-2021-en Update on DNS Security Threats, ICANN Org]</ref> As recently as [[ICANN 71]], the ICANN board was criticized by members of the [[ALAC]], the [[BC]], and other [[Internet Governance]] bodies for not doing enough to steward contracted parties and non-contracted parties toward involvement in reducing abuse. However, ICANN and [[SSAC]], in particular, have begun pointing to [[SAC115]] and [[DAAR]] as evidence of their work on addressing DNS abuse.
 
Parts of ICANN Org, Board, and Community dedicated to resolving DNS Abuse issues:
 
Parts of ICANN Org, Board, and Community dedicated to resolving DNS Abuse issues:
 
:*[[OTCO]] monitors gTLD zone files and runs  
 
:*[[OTCO]] monitors gTLD zone files and runs  
Line 99: Line 99:  
:*[[Contractual Compliance]] is not beholden to the DNS Abuse Framework; instead, the office can reprimand registrars or registries that do not maintain abuse contacts (or a webform) to receive abuse complaints or promptly investigate allegations of DNS Abuse in good faith.
 
:*[[Contractual Compliance]] is not beholden to the DNS Abuse Framework; instead, the office can reprimand registrars or registries that do not maintain abuse contacts (or a webform) to receive abuse complaints or promptly investigate allegations of DNS Abuse in good faith.
 
:*[[Domain Abuse Activity Reporting|DAAR]]
 
:*[[Domain Abuse Activity Reporting|DAAR]]
 +
:*[[DNS Security Threat Mitigation Program]]<ref>[https://www.icann.org/en/system/files/files/presentation-dns-security-threat-mitigation-program-update-22jul21-en.pdf DNS Security Threat Mitigation Program Update, ICANN Presentation, July 2021]</ref>
 +
:*[[Domain Name Security Threat Information Collection and Reporting Project]] (DNSTICR)<ref>[https://www.icann.org/en/announcements/details/adding-linguistic-diversity-to-the-domain-name-security-threat-information-collection-and-reporting-project-14-6-2021-en Adding Linguistic Diversity to the DNSTICR project, ICANN Announcements]</ref>
    
====IGF====
 
====IGF====
Bureaucrats, Check users, lookupuser, Administrators, translator
14,932

edits