ICANN 72: Difference between revisions
Line 33: | Line 33: | ||
===DNS Abuse=== | ===DNS Abuse=== | ||
* In the [[NCSG]] membership meeting, [[Theo Geurts]], of [[ | * In the [[NCSG]] membership meeting, [[Theo Geurts]], of [[Realtime Register#RiskReact|RiskReact]], presented a demonstration of [[Realtime Register]]'s DNS abuse monitoring system<ref>[https://realtimeregister.com/blog/security-threat-monitoring-beta/ Security Threat Dashboard, Realtime Register Blog]</ref> and discussed the implications of one significant finding: that 82% of malicious activity is happening at the [[URL]] level, and thus, out of the technical and policy reach of ICANN's contracted parties. Abuse happening at this level falls under the remit of resellers. | ||
* In the [[CSG]]-[[ICANN Board]] joint meeting, [[Avri Doria]] explained that the [[CCT]] and [[Second Security, Stability, and Resiliency Review]] (SSR2) generated a significant number of recommendations that address [[DNS Abuse]] and [[DNS Abuse Responses|threat mitigation]] and should be considered together in a comprehensive way to fully understand how [[ICANN]] can approach their implementation. | * In the [[CSG]]-[[ICANN Board]] joint meeting, [[Avri Doria]] explained that the [[CCT]] and [[Second Security, Stability, and Resiliency Review]] (SSR2) generated a significant number of recommendations that address [[DNS Abuse]] and [[DNS Abuse Responses|threat mitigation]] and should be considered together in a comprehensive way to fully understand how [[ICANN]] can approach their implementation. | ||
* [[Trusted Notifier|Trusted Notifier Framework]] | * [[Trusted Notifier|Trusted Notifier Framework]] |