TLD-OPS Standing Committee: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
==Work Products== | ==Work Products== | ||
* The TLD-OPS has developed a series of documents called the [https://community.icann.org/display/ccnsowkspc/TLD-OPS?preview=/111388239/123797732/TLD-OPS%20DR%20BCP%20Playbook%20-%20v-1.0.2%20-%202019-12-03.pdf TLD-OPS Disaster Recovery/Business Continuity (DR/BCP) Playbook] to help ccTLDs with their [[DR/BCP]] posture and the tools to perform their own tabletop exercises. The playbook offers a hands-on guide for implementing a business continuity strategy within smaller registry operators. It is oriented toward upper and middle management and assumes that the registry operators have their supervising bodies' commitment, sponsorship, and mission approval to develop resilience against disruptive events via a business continuity plan. It includes practical example tables for copying and using as a template at different stages of development and implementation.<ref>[https://community.icann.org/display/ccnsowkspc/TLD-OPS TLD-OPS, ccNSO Workspace</ref> | * The TLD-OPS has developed a series of documents called the [https://community.icann.org/display/ccnsowkspc/TLD-OPS?preview=/111388239/123797732/TLD-OPS%20DR%20BCP%20Playbook%20-%20v-1.0.2%20-%202019-12-03.pdf TLD-OPS Disaster Recovery/Business Continuity (DR/BCP) Playbook] to help ccTLDs with their [[DR/BCP]] posture and the tools to perform their own tabletop exercises. The playbook offers a hands-on guide for implementing a business continuity strategy within smaller registry operators. It is oriented toward upper and middle management and assumes that the registry operators have their supervising bodies' commitment, sponsorship, and mission approval to develop resilience against disruptive events via a business continuity plan. It includes practical example tables for copying and using as a template at different stages of development and implementation.<ref>[https://community.icann.org/display/ccnsowkspc/TLD-OPS TLD-OPS, ccNSO Workspace]</ref> | ||
* https://ccnso.icann.org/sites/default/files/field-attached/tld-monitoring-tools-05jul17-en.pdf | * The working group also maintains TLD monitoring tools.<ref>[https://ccnso.icann.org/sites/default/files/field-attached/tld-monitoring-tools-05jul17-en.pdf TLD Monitoring Tools, ccNSO, ICANN]</ref> | ||
==References== | ==References== | ||
Revision as of 20:12, 11 November 2021
The TLD-OPS Standing Committee is the governing body that oversees the incident response community for and by ccTLD operators.[1]
Members[edit | edit source]
The working group is composed of representatives of ccTLDs and liaisons from SSAC, IANA, and ICANN Organization's security team.[2]
Work Products[edit | edit source]
- The TLD-OPS has developed a series of documents called the TLD-OPS Disaster Recovery/Business Continuity (DR/BCP) Playbook to help ccTLDs with their DR/BCP posture and the tools to perform their own tabletop exercises. The playbook offers a hands-on guide for implementing a business continuity strategy within smaller registry operators. It is oriented toward upper and middle management and assumes that the registry operators have their supervising bodies' commitment, sponsorship, and mission approval to develop resilience against disruptive events via a business continuity plan. It includes practical example tables for copying and using as a template at different stages of development and implementation.[3]
- The working group also maintains TLD monitoring tools.[4]
References[edit | edit source]
- ↑ [https://ccnso.icann.org/en/resources/tld-ops-secure-communication.htm TLD-OPS Homepage, ICANN Resources
- ↑ https://ccnso.icann.org/en/workinggroups/tld-ops-standing.htm TLD-OPS Standing Committee, ICANN Working Groups]
- ↑ TLD-OPS, ccNSO Workspace
- ↑ TLD Monitoring Tools, ccNSO, ICANN