Security, Stability, and Resiliency of the DNS Review (SSR)
Sign up to learn more
Learn more about Reviews, their purpose and process for conducting and opportunities to participate
Find the schedule to observe SSR2 Review Team Meetings
See the progress of the SSR2 Review Team towards completing the Review
Provide input by sending an email to the SSR2 Review Team
See progress of implementation of Recommendations from past Reviews
Objectives of the SSR Review
Under the Bylaws, Section 4.6(c), ‘The Board shall cause a periodic review of ICANN’s execution of its commitment to enhance the operational stability, reliability, resiliency, security, and global interoperability of the systems and processes, both internal and external, that directly affect and/or are affected by the Internet’s system of unique identifiers that ICANN coordinates (“SSR Review”).’
The issues that the review team for the SSR Review (“SSR Review Team”) may assess are the following:
- security, operational stability and resiliency matters, both physical and network, relating to the coordination of the Internet’s system of unique identifiers;
- conformance with appropriate security contingency planning framework for the Internet’s system of unique identifiers;
- maintaining clear and globally interoperable security processes for those portions of the Internet’s system of unique identifiers that ICANN coordinates.
The SSR Review Team shall also assess the extent to which ICANN has successfully implemented its security efforts, the effectiveness of the security efforts to deal with actual and potential challenges and threats to the security and stability of the DNS, and the extent to which the security efforts are sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the DNS, consistent with ICANN’s Mission.
The SSR Review Team shall also assess the extent to which prior SSR Review recommendations have been implemented and the extent to which implementation of such recommendations has resulted in the intended effect.
The SSR Review shall be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened (see Bylaws, Section 4.6(c)).
Timeline of Review
- The first SSR Review concluded in 2012; the second review (SSR2) commenced with a Call for Volunteers in June 2016.
- Further reviews to be conducted no less frequently than every five years, measured from the date the previous SSR Review Team was convened.
One SSR Review has been completed to date, to assess the extent to which "ICANN has successfully implemented its security plan, the effectiveness of the plan to deal with actual and potential challenges and threats, and the extent to which the security plan is sufficiently robust to meet future challenges and threats to the security, stability and resiliency of the Internet DNS, consistent with ICANN's limited technical mission."
|Review||Call for Volunteers||Review Team Announced||Final Report Issued||Board Action||Details|
30 Jun 2016 - original announcement
12 Aug 2016 - extension
|14 Feb 2017|
|SSR||1 Jun 2010||30 Sep 2010||20 Jun 2012||18 Oct 2012|
Watch a brief video by David Conrad, ICANN's CTO, as he discusses the 2nd Security, Stability and Resiliency of the DNS Review Team.
The graphic below illustrates phases and status of each review - a indicates that all activities within a given phase have been completed. The chart that follows the graphic provides further details of key activities and milestones within each phase – you can view these details by clicking on each of the phases in the graphic. The table also contains links to relevant documents.
|Assemble Review Team||Call for Volunteers||Public announcement inviting volunteers to submit application||30 Jun 2016|
|Call for Volunteers Extension||Application Extended for the Second Security, Stability and Resiliency (SSR-2) Review Team||12 Aug 2016|
|Review Team Announced||Selection of the Second Security, Stability, and Resiliency of the DNS Review Team Members Announced||14 Feb 2017|
|Appointment of Board Designee||Board appoints Kaveh Ranjbar to serve as a member of the Second SSR Review Team||3 Feb 2017|
|Plan Review||Various||Review team activities and detailed information available on the community wiki||30 Jun 2016|
|Assemble Review Team||Call for volunteers||Public announcement inviting volunteers to submit application||1 Jun 2010|
|Appointment of review team members||Appointment of review team members||30 Sep 2010|
|Applications received||Applications received for SSR||12 Sep 2010|
|SO/AC Requirements||SO/AC Requirements for Review Team Volunteers||1 Jun 2010|
|Call for Independent Experts||Call for Independent Experts – Preserving Security, Stability and Resiliency of the DNS Review (AoC)||1 Jul 2010|
|Review Team Selection Approach||General Approach to Review Team Member Selection for the SSR DNS and WHOIS Review Teams||3 Sep 2010|
|Plan Review||Call for Public Comments||Questions and request for input from the community based on the SSR-RT||21 Feb 2011|
|Terms of Reference||Document outlining the scope of work adopted by the review team||23 Jun 2011|
|Various||Review team activities and detailed information available on the community wiki||20 Oct 2015|
|Conduct Review||RFP for independent experts||Call for Independent Experts||26 Jul 2010|
|Draft Report||Draft report posted for public comment||12 Mar 2012|
|Draft Statement||Draft statement posted for public comment on the Review Team’s draft Recommendations #1 and #3||17 May 2012|
|Final Report||Final report submitted to ICANN Board||20 Jun 2012|
|Public comment on Final Report||Final report posted for public comment||21 Jun 2012|
|Applications received||Applications received for independent expert on SSR||6 Sep 2010|
|Board Action||Board receipt of the Final Report||Board action and resolution||13 Sep 2012|
|Board action on review team recommendations||Board action and resolution||18 Oct 2012|
|Plan Implementation||Plan implementation||Plan implementation||19 Oct 2012|
|Implement Improvements||Details of implementation and periodic updates||Information available on the ICANN website||31 Dec 2015|
Please provide your feedback here