DDoS attacks are serious problems. While ICANN’s role in mitigating these threats is limited, the Security Team offers these insights to raise awareness on how to report DDoS attacks

Distributed Denial of Service attacks have increased in scale, intensity and frequency. The wide range of motives for these attacks – political (hacktivism), criminal (coercion), or social (malice) – makes every merchant or organization with an online presence a potential target. The shared nature of the Internet infrastructure – whether hosting, DNS, or bandwidth – puts many merchants or organizations at risk of becoming collateral damage, as well. If you find that your site or organization is under attack, it’s important that you report such attacks quickly to parties that are best positioned to help you mitigate, weather, and restore normal service.

I’m under attack. What should I do? Whom should I call?

Any Internet service – web, DNS, Internet voice, mail – can be the target of a DDoS attack. If your organization uses a hosting provider for a service that is attacked, first contact the hosting provider. If your organization hosts the network or Internet service that is under attack, first take measures to contain or dampen the attack. Next, call the service provider that provides Internet access for your network. Most hosting providers and ISPs post emergency contacts on their web sites and many include at least general contact numbers on bills. If you only have a general contact number, explain that you are under attack and ask the customer care agent to escalate (forward) your call to operations staff with the ability and authority to investigate.

Helping Hands

Traffic associated with a single DDoS attacks may originate from hundreds or thousands of attack sources (typically compromised PC or servers). In many cases, your hosting provider or your Internet access provider should act on your behalf (and in self-interest). They will contact “upstream” providers and the ISPs that route traffic from the DDoS attack sources to notify these operators of the nature and suspected origins of the attack. These operators will investigate and will typically revoke routes or take other measures to squelch or discard traffic close to the source.

If you cannot find contacts, or if the contacts you find are unresponsive, try contacting a Computer Incident, Emergency, or Security Incident Response Team (CERT/CIRT/CSIRT), or a Trusted Introducer (TI) team. CERT/CIRT organizations (find a national list here) or TI teams will investigate an attack, notify and share information with hosting providers or ISPs whose resources are being used to conduct the attack, and work with all affected parties to coordinate an effective mitigation.

Should I contact Law Enforcement?

Contact your national law enforcement agency if you believe that a crime is being committed; for example, you should contact law enforcement if your organization received a threat prior to the attack, or received a demand for money in return for not being attacked, or if you believe that critical infrastructure or delivery of a critical service (such as Emergency 911) is threatened.

Contact law enforcement to report a crime, not to mitigate an attack. DDoS attacks are criminal acts in many jurisdictions. By filing a report, you and other victims provide valuable information that may be relevant in any subsequent investigation or prosecution of the attackers.

Provide Good Intel

At an operational level, you, your hosting provider or ISP should gather as much information related to the attack as possible. The Operations Security Trust Forum recommends collecting the following kinds information:

1. Provide as much time information as possible: identify the start of attack, end of attack, whether the attacks are repeated, and whether there are observable patterns or cycles to the attacks.
2. Share any insights or suspicions you have regarding the nature of the attack. Does it appear to correlate with a geo-political event? Did you receive threatening correspondence prior to or during the attack and if so, what was the nature of the threat?
3. Provide detailed traffic information including: type of traffic (ICMP, DNS, TCP, UDP, application), source and targeted IP addresses and port numbers, packet rate, packet size, and bandwidth consumed by the attack traffic.
4. Describe any unique traffic or packet characteristics you observe. Is the attack targeting a particular virtual host or domain? What have you observed from application protocol headers? Have you observed any unusual patterns of flag settings in underlying protocols (TCP, UDP, ICMP, IP)?
5. Identify any changes you observe in the attack over time (i.e., to packet sizes, rates, unique IPs seen per epoch, protocols, etc.). These may be indications that the attacker is reacting to mitigation efforts you or others have implemented.
6. Provide your assessment of the impact; for example, explain whether you are managing the attack using mitigations and assistance, or that your services or performance is {moderately, severely} affected, or that your services have been disrupted entirely.

Don’t Wait Until You Are a Victim

If you have not already prepared a plan to respond to a DDoS attack, please consider doing so. The article Preparing for the (Inevitable) DDOS Attack offers a checklist of contacts, information, and mitigation strategies. Some helpful resources to better understand different kinds of DDoS Attacks, mitigation techniques and how your organization can help reduce the overall threat of these attacks are included below:

• SAC004, Securing The Edge
• SAC008, DNS Distributed Denial of Service (DDoS) Attacks [PDF, 963 KB]
• BCP 38, Network Ingress Filtering
• BCP 140, Preventing Use of Recursive Nameservers in Reflector Attacks
• Protecting the World from YOUR Network
• Mitigating DNS Denial of Service Attacks
• The Worrisome Threat of DNS DDoS Amplification Attacks
• Do More to Prevent DDoS Attacks
• Firewall Best Practices – Egress Traffic Filtering
• Distributed Denial of Service (Attacks/Tools)

In recent weeks, numerous high profile organizations and financial institutions have been targets of massive service disruption attacks. Several of these attacks are characteristically similar to attacks against top level domain name servers in 2006. ICANN’s Security and Stability Advisory Committee published an Advisory, SAC008 [PDF, 963 KB]: Distributed Denial of Service (DDoS) Attacks, shortly after the 2006 incidents. Recommendations from that Advisory remain relevant today.

We encourage private organizations, service operators and governments to carefully consider the recommendations from SAC 008, which describe the best known means to mitigate DDoS attacks.

“the most effective means of mitigating the effects of… numerous DoS attacks is to adopt source IP address verification” – SAC008

DDoS attacks commonly use IP addresses that are not allocated to the subscriber or IP addresses from reserved/private space to make it difficult to identify sources of attack traffic. This is called IP address spoofing. Access service providers or corporations should apply network ingress filtering (described in SAC004 and recommended by the Internet IAB in BCP038) to prevent spoofing. Squelching attack traffic close to its origins has the added benefit of relieving ISPs from forwarding malicious or criminal traffic. Everyone benefits when every operator filters spoofed source addresses, except would be attackers.

“Document operational policies relating to countermeasures… to protect [your] name server infrastructures against attacks that threaten [your] ability to offer service, give notice when such measures are implemented, and identify the actions affected parties must take to have the measures terminated.” – SAC008

I recently wrote an article, Preparing for the (Inevitable) DDoS Attack, that describes how to develop policies and prepare a response should your organization come under attack.

“disable open recursion on name servers from external sources and only accept DNS queries from trusted sources to assist in reducing amplification vectors for DNS DDoS attacks – SAC008

When open recursion is enabled on a DNS server, that server will accept DNS queries from any client (any IP source address). Attackers exploit open recursive servers in DDoS attacks and amplification attacks. US-CERT Alert TA13-088A recommends that all DNS operators:

• Disable recursion on authoritative name servers
• Limit recursion to authorized clients, and
• Rate limit responses of recursive name servers

Alert TA13-088A also identifies ways for every organization to test whether any of its name servers are open resolvers, and lists sources that describe how to do so for major operating system and name server software. (Note: TA13-088A does not have a resource for Microsoft DNS server, try here.)

The ICANN Security Team encourages you to help mitigate this increasing threat to security, stability, and resiliency.

DNS-OARC is a forum where DNS operators, implementors, and researchers collaborate in a trusted environment to share information, experiences and expertise, coordinate responses to attacks and other concerns, and improve DNS operations worldwide. Read more about DNS-OARC at https://www.dns-oarc.net/. ICANN has hosted DNS-OARC at previous meetings, such as in San Francisco and Toronto, and has been a long supporter of DNS-OARC’s mission as a non-profit, membership-driven organization promoting research and information sharing on the Domain Name System.

The Commonwealth Cybercrime Initiative (CCI) seeks to provide coherent, comprehensive and sustainable assistance to member states so that states are better able to combat cybercrime. As a member of the EMG, Dave will provide advice on the overall operations of the CCI. (Read more about the CCI at http://www.commonwealthigf.org/cigf/cybercrime/). ICANN has hosted the CCI at recent meetings such as in Prague and Costa Rica, and is working with the CCI on DNS training and capability building initiatives.

Diigo is a social annotation and bookmarking service that millions of individuals, educators, and students use daily to manage and share information, conduct research and collaborate. On October 24th, an attacker gained control of Diigo’s domain registrar account. Domain was hijacked away from Diigo’s control, into the hands of an attacker and Diigo’s services were lost to an estimated five million users for more than two days. TechCrunch has published a detailed account of the incident which should serve as a sobering reminder for everyone who registers a domain: your domain name is a critical component of your online presence and you must take measures to monitor and safeguard against attacks that can disrupt the services you offer, impede research, cause you material loss or reputational harm.

Domain hijacking is not new. ICANN’s Security, Stability and Advisory Committee (SSAC) began raising awareness of the threat in 2006 in its first Domain Hijacking Report. Since 2006, SSAC and members of ICANN’s Security Team have recommended measures registrants can take to protect their domain name registration accounts and ways that registrars can assist them (SAC040, SAC044).

The Diigo incident is a case involving user account compromise, extortion, and unauthorized transfer of domain. Among other measures recommended, these reports emphasize the importance of protecting accounts with credentials (usernames and passwords) that are not easily guessed or obtained through social engineering. Remember: any party who has access to your credentials – you, staff you contract with to host your web site, or registrar staff – can be a target and victim of a social engineering attack.

The reports also explain the importance of using “locks” to prevent unauthorized transfers. Another SSAC reports explain how a domain name can be hijacked by a phishing attack: here, a registrar-impersonating phisher lures a registrar’s customer to a bogus copy of the registrar’s customer login page, where the customer may unwittingly disclose account credentials to the attacker who can then modify or assume ownership of the customer’s domain names.

Our “short list” of measures all registrants should take to protect against domain hijacking or other domain name attacks includes:

1. Protect domain name account credentials. Most registrar account portals are password protected, so create strong passwords, and safeguard them. You may also want to shop for a registrar that offers multi-factor authentication (e.g., token).
2. Use SSL (HTTPS) when you access your domain name registration account.
3. Use ICANN accredited registrars. Ask about the reputation and service record of registrars. If you’re not entirely comfortable with a registrar, you can and should consider transferring your domain to a party you trust.
4. Ask your registrar to apply registrar locks on your domain names. Locks (formally, status codes) prevent changes to your domain name registrations, and block attempts to transfer or delete your domain names (see SAC044, pp 22-23). A number of TLD registry operators offer registry lock to prevent unintended changes to registry accounts. This service is offered in addition to lock services offered by registrars, and often includes manual support (1, 2).
5. Pay attention to “routine” registrar correspondence, as these may be phishing emails. In these email messages, phishers often use HTML to embed malicious links in seemingly innocuous or “safe” links. Don’t click on a hyperlink; instead, type the link in manually.
6. Monitor your domain’s WHOIS and DNS information. Check both routinely so you can detect any unauthorized or suspicious changes (see SAC044, pp 20-22).
7. Keep your domain name registrant account information private, secure, and recoverable.

For more information, you may also find these articles helpful:

Measures to protect (University) domain registrations and DNS against attacks
http://securityskeptic.typepad.com/the-security-skeptic/2011/07/measures-to-protect-university-domains-against-attacks.html

Podcast: How to protect your domain registration accounts against attack or misuse
http://securityskeptic.typepad.com/the-security-skeptic/2011/02/podcast-how-to-protect-your-domain-registration-accounts-against-attack-or-misuse.html

Why You Need To Add “Protect Domain Name” To The Security Checklist
http://www.networkcomputing.com/data-protection/why-you-need-to-add-protect-domain-name/229616011

How To Protect Yourself Against Domain Name Hijackers
http://www.informationweek.com/how-to-protect-yourself-against-domain-n/170000337

Want to Register a Domain Name? Easy Consumer Advice
http://blog.consumerwebwatch.org/2007/12/want_to_register_a_domain_name_1.html

Top Ten Things to Consider when Registering A Domain Name
http://www.consumerwebwatch.org/pdfs/domainname.pdf

He was the keynote speaker at the Russian IGF, but the local organizers, the Russian Coordination Center for the .ru ccTLD decided to use him even more, and invited Jeff also to join a panel discussion on DDoS attacks, with Natalia Kaspersky and Andrea Rigoni.

At the panel, Jeff spoke after some other prominent panelist, who discussed the topic “Combat with cybercrime: cooperation and collective initiatives” – like Michel Moren, Acting Assistant Deputy Director, INTERPOL and Alexey Moshkov, Head of the Bureau for Special Technical Measures of Department “K” of the Ministry of Interior of Russian Federation, Police Major General. Full program of the event (in English) is at their web site.

After the panel was over, and without giving Jeff a break, the Minister of telecom and mass communications, I.O. Schegolev, invited Jeff to officially open the 23rd international exhibition SvyazExpoCom. Jeff was in a good company – besides the Russian minister, the other dignitaries, who spoke at the opening of the exhibition included Slovenian member of the cabinet Ziga Turk, ITU deputy Secretary-General Houlin Zhao, and the deputy-chairman of the Russian Chamber of Commerce Vladimir Strashko. Interesting moment, and hardly with equivalent, was that Jeff’s speech was translated by the deputy-minister of communications (sic!).

After the opening of the exhibition, Jeff was rushed back to the main plenary hall, where hundreds of people were patiently waiting to hear his keynote (video to be posted soon).

I won’t write here about the presentation, but will note that after it was over, we had a number of meetings, one after the other, until late at night, with people from across the Internet specter – from law-enforcement, through academia, through business and non-profit, and government representatives.

Here’s what the CEO of the Russian Coordination Center for the .ru ccTLD, Andrei Kolesnikov, wrote about Jeff’s presentation and interaction with the participants at the event:

“Having spoken with a number of our guests, including government representatives and professionals, I am pleased to let you know everyone cited your presentation as a candid and provocative account which helped raise awareness of critical challenges in the cybersecurity area and ways to address them.”

I can also confirm that this opinion was indeed shared by many.

The Russians now want Jeff to visit again, and not only for a one day stay, but to stay longer. Some are already asking if he could join, in 2013, the 16th Russian Internet Forum, or the 20th Relarn Internet geeks boat cruise on the Volga river.

I am thinking, “Maybe I should recommend him to take part in both!”

14 March — ICANN welcomed members of the Commonwealth Cybercrime Initiative (CCI) Steering Group to Costa Rica as part of its efforts to improve the security, stability and resiliency of the global Domain Name System (DNS).

The meeting offered Steering Group members the opportunity to explain the purpose of the Initiative to the ICANN community.

The proposal for the Initiative was developed through the COMNET Foundation for ICT development, an independent foundation which leads the Commonwealth Internet Governance Forum.

The objectives of this Initiative, as stated on the CCI web page, are “to assist developing Commonwealth countries to build their institutional, human and technical capacities with respect to policy, legislation, regulation, investigation and law enforcement with the aim of, making their jurisdictions more secure by denying safe havens to cyber criminals, and enabling all member countries to become effective partners in the globally coordinated effort to combat Cybercrime.” <http://www.commonwealthigf.org/cybercrime/the-commonwealth-cybercrime-initiative/>

These objectives encompass a wide range of anticrime activities, including preventing abuse of the DNS, and are thus consistent with ICANN’s core values and its obligation to enhance and protect the security and stability of the Internet name system. ICANN participates on the Initiative Steering Group and has expressed its willingness to assist the Initiative in capacity building associated with DNS operations and security. 

ICANN Chief Security Officer, Jeff Moss, said, “Through this cooperative relationship, ICANN will also assist Commonwealth member countries with DNSSEC deployment. An important goal for ICANN and the Initiative is to work to have all member countries sign their Top Level Domain zones.”

The workshop at the ICANN meeting in Costa Rica is part of an effort to “translate the CCI concept into an operational reality in assisting member countries in building coherent and sustainable capacity on the ground to help make the Internet a safer place,” said Joseph Tabone, Chairman of COMNET Foundation for ICT Development. “We thank partners for their continued support and especially thank ICANN for their opportunity to present the Initiative to their community.”

Workshop presentations from Steering Group members and ICANN staff can be viewed at http://costarica43.icann.org/node/29901.

3 月 14 日 — ICANN 欢迎联邦网络犯罪打击行动（Commonwealth Cybercrime Initiative，CCI）指导小组成员前往哥斯达黎加，为提高全球域名系统 (DNS) 的安全性、稳定性和灵活性贡献力量。

会议给指导小组成员提供了向 ICANN 机构群体阐述这一行动宗旨的机会。

行动方案是通过 COMNET 的 ICT 发展基金会制定的，该基金会是领导联邦互联网管理论坛 (Commonwealth Internet Governance Forum) 的独立基金会。

如 CCI 网页上所述，此行动的目标是”协助发展中的联邦国家在政策、立法、监管、调查和执法方面发展自己的机构、人员和技术能力，旨在通过拒绝给网络罪犯提供庇护，让所有成员国有效加入全球打击网络犯罪的协调行动，加强其辖区的安全。” <http://www.commonwealthigf.org/cybercrime/the-commonwealth-cybercrime-initiative/>

这些目标包括一系列打击犯罪的活动，包括防止 DNS 的滥用等，且这些目标均符合 ICANN 的核心价值及其加强和保护互联网名称系统的安全性和稳定性的义务。ICANN 加入了行动指导小组，并表达了在与 DNS 运营和安全性相关的能力建设上协助这一行动的意愿。

ICANN 首席安全官 Jeff Moss 说：”透过这种合作关系，ICANN 还将在 DNSSEC 的部署上协助联邦成员国。ICANN 和此行动的一个重要目标就是努力让所有成员国签署他们的顶级域名区域。”

此次在 ICANN 哥斯达黎加会议上举办的研讨会是为”本着让互联网更加安全的目的，将 CCI 概念转化为运营现实，帮助成员国进行协调一致和可持续的能力建设。”COMNET ICT 发展基金会主席 Joseph Tabone 说，”我们感谢合作伙伴一直以来的支持，特别是要感谢 ICANN 让我们有机会向他们的机构群体介绍这一行动。”

14 марта — ICANN приветствовала участников координационной группы «Инициативы стран Содружества по борьбе с киберпреступностью» (CCI) в Коста-Рике в рамках мероприятий, направленных на повышение безопасности, стабильности и отказоустойчивости глобальной системы доменных имен (DNS).

Конференция предоставила возможность членам координационной группы объяснить цель инициативы сообществу ICANN.

Предложение по этой инициативе было выработано COMNET Foundation for ICT development — независимым фондом, возглавляющим Форум управления Интернетом стран Британского содружества наций.

Цель данной инициативы, как отмечено на веб-странице CCI — «помогать развивающимся странам Содружества строить институциональные, гуманитарные и технические ресурсы с учетом политики, законодательства, нормативных актов, исследований и охраны правопорядка, чтобы сделать свои территории более безопасными за счет исключения возможности создания «безопасных гаваней» для киберпреступников и дать возможность всем странам-участницам стать эффективными партнерами в глобальной борьбе с киберпреступностью». <http://www.commonwealthigf.org/cybercrime/the-commonwealth-cybercrime-initiative/>

Данные цели охватывают широкий спектр мер по борьбе с преступностью, включая предотвращение злоупотреблений в отношении DNS, что совпадает с основными ценностями ICANN и обязательством корпорации укреплять и защищать безопасность и стабильность системы имен Интернета. ICANN участвует в координационной группе Инициативы и выражает свою готовность оказывать помощь Инициативе в укреплении потенциала, относящегося к операциям с DNS и безопасности.

Джефф Мосс (Jeff Moss), руководитель службы безопасности ICANN, заявил: «В рамках этого сотрудничества ICANN будет также помогать странам Содружества в развертывании DNSSEC. Важная цель ICANN и Инициативы — добиться того, чтобы все страны-участницы подписали свои зоны доменов верхнего уровня».

Семинар на конференции ICANN в Коста-Рике — это часть мероприятий, направленных на «перевод концепции CCI в конкретные оперативные действия по оказанию помощи странам-участницам в построении последовательного и устойчивого потенциала для обеспечения безопасности Интернета» — заявил Джозеф Табоун (Joseph Tabone), председатель фонда COMNET Foundation for ICT Development. «Мы благодарим партнеров за постоянную поддержку, в особенности мы благодарны ICANN за предоставленную возможность представить Инициативу своему сообществу».

14 mars — L’ICANN donne la bienvenue aux membres du groupe d’orientation de l’initiative Commonwealth sur le Cybercrime (Commonwealth Cybercrime Initiative – CCI) au Costa Rica dans le cadre de ses efforts pour améliorer la sécurité, la stabilité et la résilience du système mondial des noms de domaine (DNS).

Pendant la réunion, les membres du groupe d’orientation ont eu l’occasion d’expliquer les objectifs de l’initiative à la communauté de l’ICANN.

La proposition pour l’initiative a été développée à travers la fondation COMNET pour le développement ICT, une fondation indépendante qui conduit le forum sur la gouvernance d’Internet du Commonwealth.

Les objectifs de cette initiative, tel que mentionnées sur le site Web du CCI sont « d’assister les pays en développement du Commonwealth à construire leurs capacités institutionnelles, humaines et techniques concernant la politique, la législation, la régulation, la recherche et les organismes du respect de la loi dans le but que leurs juridictions soient plus sures du fait de refuser de donner de l’abri aux cybercriminels et permettant à tous les pays membres de devenir des partenaires actifs des efforts coordonnés mondialement pour combattre le cybercrime ». <http://www.commonwealthigf.org/cybercrime/the-commonwealth-cybercrime-initiative/>

Ces objectifs regroupent un ensemble d’activités contre le crime, y compris la prévention des abus du DNS, cela étant cohérent avec les principales valeurs de l’ICANN et avec son obligation d’améliorer et de protéger la sécurité et la stabilité du système de noms de domaine. L’ICANN participe de l’initiative du groupe d’orientation et a exprimé sa volonté d’aider le groupe à développer les capacités associés aux opérations du DNS et à la sécurité.

Jeff Moss, chef du service de sécurité de l’ICANN a manifesté qu’ « à travers cette relation coopérative, l’ICANN aidera également les pays membres du Commonwealth au déploiement du DNSSEC. Un objectif important pour l’ICANN et pour l’Initiative est de travailler pour que tous les pays membres signent leurs zones de domaines de premier niveau ».

L’atelier réalisé lors de la réunion de l’ICANN au Costa Rica fait partie de l’effort pour « traduire le concept du CCI dans une réalité opérationnelle en aidant les pays membres à construire des capacités cohérentes et durables sur le terrain afin d’aider à ce que l’Internet devienne de plus en plus sure » a dit Joseph Tabone, président de la fondation COMNET pour le développement ITC. « Nous remercions nos partenaires de leur soutien continu et tout spécialement l’ICANN de l’opportunité de présenter l’initiative à sa communauté ».

14 de marzo — La ICANN le dio la bienvenida a los miembros del Equipo Directivo de Commonwealth Cybercrime Initiative (CCI) a Costa Rica, como parte de su esfuerzo para mejorar la seguridad, estabilidad y flexibilidad del Sistema de Nombres de Dominio (DNS).

La reunión ofreció a los miembros del Equipo Directivo la oportunidad de explicar la finalidad de la Iniciativa a la comunidad de la ICANN.

La propuesta de la Iniciativa fue desarrollada a través de la Fundación COMNET para el Desarrollo de la Tecnología de la Información y las Comunicaciones (ICT), una fundación independiente que lidera el Foro de la Gobernanza de Internet de la Commonwealth (Commonwealth Internet Governance Forum).

Los objetivos de esta Iniciativa, como se encuentran indicados en el sitio web de CCI, son de “asistir a los países en vías de desarrollo de la Commonwealth para fortalecer sus capacidades institucionales, humanas y técnicas relativas a políticas, legislación, regulación, investigación y cumplimiento de la ley, con el fin de lograr que sus jurisdicciones sean más seguras al negar refugio a los ciber-delincuentes y al permitir que todos los países miembros a se conviertan en socios efectivos en el esfuerzo coordinado global para combatir la ciber-delincuencia”. <http://www.commonwealthigf.org/cybercrime/the-commonwealth-cybercrime-initiative/>

Estos objetivos abarcan una amplia variedad de actividades en contra de la delincuencia, incluyendo la prevención del uso indebido del DNS, y por lo tanto son consistentes con los valores principales de la ICANN y con su obligación para mejorar y proteger la seguridad y estabilidad del sistema de nombres de Internet. La ICANN participa del Equipo Directivo de la Iniciativa y ha manifestado su voluntad de asistir con la misma en lo que respecta al desarrollo de capacidades relacionadas a las operaciones y seguridad del DNS.

El Director de Seguridad de la ICANN, Jeff Moss, comentó, “A través de esta relación cooperativa, la ICANN también asistirá a los países miembros de la Commonwealth en lo que respecta al despliegue de Extensiones de Seguridad para el Sistema de Nombres de Dominio (DNSSEC). Una meta importante para la ICANN y para la Iniciativa es la de trabajar para lograr que todos los países miembros firmen sus zonas de Dominio de Alto Nivel”.

El taller que se realizó durante la reunión de la ICANN que se llevó a cabo en Costa Rica, forma parte de un esfuerzo para “traducir el concepto de CCI a una realidad operativa relacionada a la asistencia a países miembros para desarrollar capacidades coherentes y sostenibles con el fin de ayudar a lograr que Internet sea un lugar más seguro”, expresó Joseph Tabone, Presidente de la Fundación COMNET para el Desarrollo de la Tecnología de la Información y las Comunicaciones (ICT). “Agradecemos a nuestros socios por su apoyo constante y agradecemos especialmente a la ICANN por habernos dado la oportunidad de presentar la Iniciativa a su comunidad”.