[NCUC-DISCUSS] Fwd: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks

Stephanie Perrin stephanie.perrin at mail.utoronto.ca
Mon Jan 19 00:59:07 CET 2015


Where is the framework they are using?  Seems un-useful to just stargaze 
and come up with 5 risks, before looking at how they are framing risk.
cheers Steph
On 2015-01-18 4:09, William Drake wrote:
> Thoughts?
>
>> Begin forwarded message:
>>
>> *From: *David Olive <david.olive at icann.org 
>> <mailto:david.olive at icann.org>>
>> *To: *"byron.holland at cira.ca <mailto:byron.holland at cira.ca>" 
>> <byron.holland at cira.ca <mailto:byron.holland at cira.ca>>, 
>> "jonathan.robinson at ipracon.com 
>> <mailto:jonathan.robinson at ipracon.com>" 
>> <jonathan.robinson at ipracon.com 
>> <mailto:jonathan.robinson at ipracon.com>>, "louie at louie.net 
>> <mailto:louie at louie.net>" <louie at louie.net <mailto:louie at louie.net>>, 
>> "thomas.schneider at bakom.admin.ch 
>> <mailto:thomas.schneider at bakom.admin.ch>" 
>> <thomas.schneider at bakom.admin.ch 
>> <mailto:thomas.schneider at bakom.admin.ch>>, "alan.greenberg at mcgill.ca 
>> <mailto:alan.greenberg at mcgill.ca>" <alan.greenberg at mcgill.ca 
>> <mailto:alan.greenberg at mcgill.ca>>, "patrik at frobbit.se 
>> <mailto:patrik at frobbit.se>" <patrik at frobbit.se 
>> <mailto:patrik at frobbit.se>>, "tsinha at umd.edu <mailto:tsinha at umd.edu>" 
>> <tsinha at umd.edu <mailto:tsinha at umd.edu>>, "liman at netnod.se 
>> <mailto:liman at netnod.se>" <liman at netnod.se <mailto:liman at netnod.se>>, 
>> "Metalitz, Steven" <met at msk.com <mailto:met at msk.com>>, 
>> "Elisa.Cooper at markmonitor.com <mailto:Elisa.Cooper at markmonitor.com>" 
>> <Elisa.Cooper at markmonitor.com <mailto:Elisa.Cooper at markmonitor.com>>, 
>> "tonyarholmes at btinternet.com <mailto:tonyarholmes at btinternet.com>" 
>> <tonyarholmes at btinternet.com <mailto:tonyarholmes at btinternet.com>>, 
>> "rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>" 
>> <rafik.dammak at gmail.com <mailto:rafik.dammak at gmail.com>>, 
>> "william.drake at uzh.ch <mailto:william.drake at uzh.ch>" 
>> <william.drake at uzh.ch <mailto:william.drake at uzh.ch>>, 
>> "rudi.vansnick at isoc.be <mailto:rudi.vansnick at isoc.be>" 
>> <rudi.vansnick at isoc.be <mailto:rudi.vansnick at isoc.be>>, 
>> "Michele at blacknight.com <mailto:Michele at blacknight.com>" 
>> <Michele at blacknight.com <mailto:Michele at blacknight.com>>, 
>> "kdrazek at Verisign.com <mailto:kdrazek at Verisign.com>" 
>> <kdrazek at Verisign.com <mailto:kdrazek at Verisign.com>>
>> *Cc: *"mike.silber at icann.org <mailto:mike.silber at icann.org>" 
>> <mike.silber at icann.org <mailto:mike.silber at icann.org>>, 
>> "rmohan at afilias.info <mailto:rmohan at afilias.info>" 
>> <rmohan at afilias.info <mailto:rmohan at afilias.info>>
>> *Subject: **Board Risk Committee Request for Feedback on Top 5 ICANN 
>> Enterprise Risks*
>> *Date: *January 17, 2015 at 4:10:36 PM GMT+1
>>
>> Below is a note from the ICANN Board Risk Committee Co-Chairs.
>>
>> ---------------------------------------------
>>
>> Dear SO/AC/SG:
>>
>> The Board Risk Committee (BRC) is tasked to provide oversight and 
>> guidance into enterprise risk identification and remediation for 
>> ICANN. ICANN has developed a risk management framework and 
>> methodology that is used to identify, mitigate and monitor risks.
>>
>> The purpose of this email is to reach out to you, the SO/AC/SG 
>>  Leadership, to ask your group to identify what it believes are the 
>> _top five enterprise-wide risks_ to ICANN. This feedback process 
>> allows us to calibrate and evaluate risks identified internally with 
>> those identified by the community.
>>
>> We envision a response as an enumerated list of the top five 
>> enterprise risks that your SO or AC group believes ought to be 
>> ICANN’s top priorities.
>>
>> We ask to provide a written response *via email* by *5 February 
>> 2015*. We anticipate discussion on these identified risks in the 
>> SO/AC Constituency meetings with the Board during ICANN 52 in 
>> Singapore. Please send all written responses directly to 
>> Enterprise-Risk at ICANN.Org <mailto:Enterprise-Risk at ICANN.Org>.
>>
>> We understand that you may not have the time to develop a formal 
>> response from your SO or AC group. In that case, we would appreciate 
>> you providing us with your own personal views or those of a small 
>> sub-set of your SO or AC group, but please let us know if you have 
>> done so. We will iterate the process to improve it and comments on 
>> possible improvements are most welcome.
>>
>> Again, thank you in advance and we look forward to your input.
>>
>> Regards,
>> Mike Silber & Ram Mohan
>> ICANN Board Risk Committee Co-Chairs
>>
>>
>> David A. Olive
>> Vice President, Policy Development Support
>> General Manager, ICANN Regional Headquarters –Istanbul
>> Hakki Yeten Cad. Selenium Plaza No:10/C K:10 34349 Fulya, Besiktas, 
>> Istanbul
>> Internet Corporation for Assigned Names and Numbers (ICANN)
>>
>> Direct Line: +90.212.999.6212
>> Mobile:       + 1. 202.341.3611
>> Mobile:       +90.533.341.6550
>> Email: david.olive at icann.org <mailto:david.olive at icann.org>
>> www.icann.org <http://www.icann.org>
>>
>
> ***********************************************
> William J. Drake
> International Fellow & Lecturer
>   Media Change & Innovation Division, IPMZ
>   University of Zurich, Switzerland
> Chair, Noncommercial Users Constituency,
>   ICANN, www.ncuc.org <http://www.ncuc.org>
> william.drake at uzh.ch <mailto:william.drake at uzh.ch> (direct), 
> wjdrake at gmail.com <mailto:wjdrake at gmail.com> (lists),
> www.williamdrake.org <http://www.williamdrake.org>
> ***********************************************
>
>
>
> _______________________________________________
> Ncuc-discuss mailing list
> Ncuc-discuss at lists.ncuc.org
> http://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncuc.org/pipermail/ncuc-discuss/attachments/20150118/8cc87617/attachment-0002.html>


More information about the Ncuc-discuss mailing list