Domain Abuse Activity Reporting: Difference between revisions
No edit summary |
|||
(5 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
'''Domain Abuse Activity Reporting (DAAR)''' is a system for studying and reporting on domain name registration and [[DNS Abuse]]. The aim of the DAAR project is to develop a methodology for analyzing security threats to inform ICANN policy decisions.<ref>[https://www.icann.org/octo-ssr/daar DAAR, OCTO, ICANN]</ref> | '''Domain Abuse Activity Reporting (DAAR)''' is a system for studying and reporting on domain name registration and [[DNS Abuse]]. The aim of the DAAR project is to develop a methodology for analyzing security threats to inform [[ICANN]] policy decisions.<ref>[https://www.icann.org/octo-ssr/daar DAAR, OCTO, ICANN]</ref> | ||
==Process== | ==Process== | ||
DAAR collects [[TLD]] zone data and complements them with third-party [[RBL|Reputation Block List]]s based on crowdsourcing, spam filters, and | DAAR collects [[TLD]] zone data and complements them with third-party [[RBL|Reputation Block List]]s based on crowdsourcing, spam filters, and [[Honeypot]]s that have identified [[Phishing]], [[Malware]], [[Spam]], and [[Botnet Attacks]]. The [[iThreat Cyber Group]] (ICG) collects and reports to DAAR three data sets.<ref>[https://www.icann.org/en/system/files/files/daar-monthly-report-04feb19-en.pdf Understanding the DAAR Monthly Report]</ref> | ||
===Zone Data=== | ===Zone Data=== | ||
Line 15: | Line 15: | ||
# [[PhishTank]] | # [[PhishTank]] | ||
# [[Malware Patrol]] | # [[Malware Patrol]] | ||
# [ | # [https://abuse.ch Abuse.ch] | ||
# [https://urlabuse.com URLAbuse] | |||
==Reporting== | ==Reporting== | ||
===For gTLDs=== | |||
DAAR data are currently released to registries via ICANN's [https://www.icann.org/news/multimedia/2801 Service Level Agreement Monitoring] ([[SLAM]]) system and shared in [https://www.icann.org/octo-ssr/daar monthly reports] with a median aggregate, aggregated statistics, and time-series analyses. | DAAR data are currently released to registries via ICANN's [https://www.icann.org/news/multimedia/2801 Service Level Agreement Monitoring] ([[SLAM]]) system and shared in [https://www.icann.org/octo-ssr/daar monthly reports] with a median aggregate, aggregated statistics, and time-series analyses. | ||
===For ccTLDs=== | |||
In January 2021, DAAR began providing personalized monthly reports for [[ccTLD]]s.<ref>[https://www.icann.org/en/blogs/details/daar-activity-project-now-providing-personalized-monthly-reports-for-cctlds-20-1-2021-en DAAR Reports for ccTLDs begins, ICANN Blog]</ref> | |||
==Critiques== | ==Critiques== | ||
Line 29: | Line 33: | ||
==References== | ==References== | ||
[[Category:ICANN Tools]] | |||
[[Category:DNS Abuse Responses]] |
Latest revision as of 08:58, 12 November 2024
Domain Abuse Activity Reporting (DAAR) is a system for studying and reporting on domain name registration and DNS Abuse. The aim of the DAAR project is to develop a methodology for analyzing security threats to inform ICANN policy decisions.[1]
Process[edit | edit source]
DAAR collects TLD zone data and complements them with third-party Reputation Block Lists based on crowdsourcing, spam filters, and Honeypots that have identified Phishing, Malware, Spam, and Botnet Attacks. The iThreat Cyber Group (ICG) collects and reports to DAAR three data sets.[2]
Zone Data[edit | edit source]
- Top-Level Domain Zone Data (through ICANN’s Centralized Zone Data Service)[3]
- Sponsoring Registrar Registration Data (contractually mandated for gTLDs and volunteered by ccTLDs), and
- Domain Reputation Data
Reputation Data Sources[edit | edit source]
Reporting[edit | edit source]
For gTLDs[edit | edit source]
DAAR data are currently released to registries via ICANN's Service Level Agreement Monitoring (SLAM) system and shared in monthly reports with a median aggregate, aggregated statistics, and time-series analyses.
For ccTLDs[edit | edit source]
In January 2021, DAAR began providing personalized monthly reports for ccTLDs.[4]
Critiques[edit | edit source]
At ICANN 71, several issues were raised during the discussion on RBLs and, by extension DAAR. They included that:
- Neither DAAR nor the RBLs distinguish between maliciously registered and compromised domains;
- DAAR does not address mitigation or reflect how quickly abuse is addressed;
- Not immediately up-to-date;
- Concerns over the inclusion of content-based complaints (see also Bambenek's 2018 validation report,[5] which also mentioned the outsized impact of activity on small registars' risk scores); and
- False positives.