[lac-discuss-en] RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks

Sun Jan 18 15:20:05 UTC 2015

[[--Translated text (es -> en)--]]

 Subject: Re: RV: Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks 
 From: asoto at ibero-americano.org

 I forgot a point on the risk classification, which is synthetically the following: 

 1. Credits 

 2. Legal 

 3. Marketing / Prices 

 4. Strategy 

 5. Reputation 

 Greetings! 

 Alberto 

 From: Alejandro Pisanty [mailto: apisanty at gmail.com] 
 Posted on: Sunday, January 18, 2015 3:39 a.m. 
 To: Alberto Soto 
 CC: LACRALO Spanish 
 Subject: Re: [lac-discuss-en] FW: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks 

 Alberto, 

 Thanks for taking this initiative, productive and concrete. 

 I think the issue we can better develop risk is the change in the model of governance that point out about the change in the rules of decision making GAC; would increase from consensus to voting and will &quot;rub off&quot; the Board. 

 As isolated and punctual element is important, but much more if it is associated with a change in culture to produce a departure from the more general consensus. 

 How would order other / as representatives of organizations LACRALO the risks we have identified so far? How do would compare with other orders (financial, IT security, etc.) has pointed Alberto? 

 Alejandro Pisanty 

 01/17/2015 22:35 GMT-06: 00 Alberto Soto <asoto at ibero-americano.org> : 

 Alejandro and everyone. Discussion is always beneficial to bring these issues.I do not know if I could rely, very particular systemic risk in financial issues, although I admit that maybe we could get to determine a risk to produce a cascading effect within the organization. 

 But we can propose risks. 

 So we can quickly understand and perhaps propose something, partially quote the charter of the Board Risk Committee as set out in 2009: 

 &quot;A: Monitoring risk management of ICANN as an organization, including the following: 

 1. Review and advise on ICANN policies, plans and related risk management programs; 

 2. Monitoring the effectiveness of risk management programs, including the management and control of operational risk; 

 3. The monitoring of exposure to significant non-financial risk to ICANN and the steps taken to monitor and control such exposures;

 4. Keep informed about ICANN conditions and gaining familiarity with ICANN processes in order to identify potential risks and advise on future plans to address these risks, as appropriate; and 

 5. Review other areas appropriate risk concentration. 

 B: Monitoring operational activities including reviewing the information and monitoring the effectiveness of the management of operational activities such as: 

 1. The effectiveness of the technology used by ICANN; 

 2. The adequacy of the policies of ICANN business continuity; and 

 3. Facing the changes in the business environment that may be important for ICANN operations. &quot; 

 In addition to this charter, we must bear in mind that the issue of risk has been divided into: 

 - Credits

 - Legal 

 - Marketing / Prices 

 - Reputation 

 With that maybe we could focus on A.3 and B. in three points. 

 And suggest as risks: 

 - System Safety ICANN: The hacking of time recently Whois systems - wiki - CZDS. What technology are you using? It hurt a lot the reputation of ICANN. 

 - Change in Board voting system to assimilate it to the GAC. Relates to the B.2. but the results go against the system of multiple stakeholders. If the foundation is that the GAC meets less often, and until today was more effective system of Board of ICANN, the GAC meets once a year and more assimilated to ICANN. 

 - When the ICG was created only to certain components of the multi-stakeholder model was taken into account.As far as we were concerned, was not expected to ALAC send a participatory report. The individual user to which we represent is not within business continuity ICANN, IANA before the transition? 

 I hope there is participation, and although we can not make a formal report LACRALO, maybe we can send suggestions individually. I say we can not formally make them not only by time, but because there are those who understand that there is no need for LACRALO make propositions. Are discussing a procedure thereon. 

 Best Regards 

 Alberto Soto 

 From: Alejandro Pisanty [mailto: apisanty at gmail.com <mailto:apisanty at gmail.com> ] 
 Posted on: Saturday, January 17, 2015 10:01 pm 
 To: Alberto Soto 
 CC: LACRALO Spanish 
 Subject: Re: [lac-discuss-en] FW: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN Enterprise Risks 

 Alberto, 

 two weeks left. Would not it be a topic suitable for LACRALO discussion? Although we do not produce a collective expression discussion could feed the individual views. 

 I cause its inception proposed as a risk worth inclusion &quot;unlimited expansion of At Large without accountability and effectiveness measures&quot; ... (there are others, but this may be one that allows calibrate the way to enter discuss). 

 Do you what you consider to be the most important systemic risk on which we could argue constructively and effectively? 

 Best regards. 

 Alejandro Pisanty 

 On Sat, Jan 17, 2015 at 2:55 PM, Alberto Soto <asoto at ibero-americano.org <mailto:asoto at ibero-americano.org> &gt; Wrote:

 I estimate, please ask them if they have any suggestions on this 
 subject, sent directly to the indicated mail. Time is short. 
 Thanks and best regards 

 Alberto Soto 

 ----- Original Message ----- 
 From: alac-bounces at atlarge-lists.icann.org <mailto:alac-bounces at atlarge-lists.icann.org>
 [Mailto: alac-bounces at atlarge-lists.icann.org <mailto:alac-bounces at atlarge-lists.icann.org> ] On behalf of Alan Greenberg 
 Posted on: Saturday, January 17, 2015 1:03 pm 
 To: ALAC 
 Subject: Re: [ALAC] Board Risk Committee Request for Feedback on Top 5 ICANN 
 Enterprise Risks 

 If anyone has any thoughts on This, por favor forward and I will collate them 
 and send them in. 

 Alan 

 01/17/2015 At 10:10 a.m., David Olive wrote: 
 > 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 metodología That Is 
 > Used to Identify, mitigate and monitor Risks. 
 > 
 > The purpose of esta email is to reach out to you, the SO / AC / SG 
 > Leadership, to ask your group to identify identity factotum believes it what are the top 
 > Five enterprise-wide Risks to ICANN. This feedback process Allows us to 
 > Calibrate and evaluate- internally With Those Identified Risks 
 > Identified by the community. 
 > 
 > We envision a response as an enumerated list of the top five enterprise 
 > Risks That your SO or AC group factotum 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 in Original Identified Risks in the SO / AC 
 > Constituency meetings With The Board During ICANN 52 in Singapore. 
 > Please send all written responses Directly to 
 > <mailto:Enterprise-Risk at ICANN.Org <mailto:Enterprise-Risk at ICANN.Org> &gt; Enterprise-Risk at ICANN.Org <mailto:Enterprise-Risk at ICANN.Org> . 
 > 
 > We Understand that you 'the May not have any time to Develop a Formal 
 > Response from your SO or AC group.In That case, we would appreciate 
 > Reviews us with you providing your own views or staff 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 increase it and comments on possible 
 > Improvements are most welcome. 
 > 
 > Again, thank you in advance and we look forward to your input. 
 > 
 > Regards, 
 > Mike Silber &amp; Ram Mohan 
 > ICANN Board Risk Committee Co-Chairs 
 > 
 > 
 > 
 > David A. Olive 
 > Vice President, Policy Development Support General Manager, ICANN 
 > Regional Headquarters -istanbul Hakki Yeten Selenium Square Cad. 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: <mailto:david.olive at icann.org <mailto:david.olive at icann.org> &gt; David.olive at icann.org <mailto:david.olive at icann.org>
 > Www.icann.org <http://www.icann.org>
 > 
 _______________________________________________ 
 ALAC mailing list 
 ALAC at atlarge-lists.icann.org <mailto:ALAC at atlarge-lists.icann.org>
 https://atlarge-lists.icann.org/mailman/listinfo/alac 

 At-Large Online: http://www.atlarge.icann.org ALAC Working Wiki: 
 https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALA 
 C) 

 --- 
 Avast antivirus software scanned this email for viruses. 
 http://www.avast.com 

 _______________________________________________ 
 lac-discuss-en mailing list 
 lac-discuss-es at atlarge-lists.icann.org <mailto:lac-discuss-es at atlarge-lists.icann.org>
 https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es 

 http://www.lacralo.org 

 - 

 - - - - - - - - - - - - - - - - - - - - - - - - - - - 
     Dr.Alejandro Pisanty 
 Faculty of Chemistry UNAM 
 University Av 3000. 04510 Mexico DF Mexico 
 + 52-1-5541444475 FROM ABROAD 
 FROM MEXICO SMS +525541444475 +525541444475 
 Blog: http://pisanty.blogspot.com 
 LinkedIn: http://www.linkedin.com/in/pisanty 
 Join the LinkedIn group UNAM, http://www.linkedin.com/e/gis/22285/4A106C0C8614 
 Twitter: http://twitter.com/apisanty 
 ---- &gt;&gt; Join ISOC Mexico, http://www.isoc.org 
 . . . . . . . . . . . . . . . . 

  _____ 

<http://www.avast.com/>

<http://www.avast.com/> Avast antivirus software scanned this email for viruses. 
 www.avast.com 

<http://www.avast.com/>

<http://www.avast.com/>

<http://www.avast.com/>

<http://www.avast.com/> -

<http://www.avast.com/> - - - - - - - - - - - - - - - - - - - - - - - - - - - 
     Dr. Alejandro Pisanty 
 Faculty of Chemistry UNAM 
 University Av 3000. 04510 Mexico DF Mexico 
 + 52-1-5541444475 FROM ABROAD 
 FROM MEXICO SMS +525541444475 +525541444475 
 Blog: http://pisanty.blogspot.com 
 LinkedIn: http://www.linkedin.com/in/pisanty 
 Join the LinkedIn group UNAM, http://www.linkedin.com/e/gis/22285/4A106C0C8614 
 Twitter: http://twitter.com/apisanty 
 ---- &gt;&gt; Join ISOC Mexico, http://www.isoc.org 
 . . . . . . . . . . . . . . . . 

 --- 
 Avast antivirus software scanned this email for viruses. 
 http://www.avast.com 
 _______________________________________________ 
 lac-discuss-en mailing list 
 lac-discuss-es at atlarge-lists.icann.org 
 https://atlarge-lists.icann.org/mailman/listinfo/lac-discuss-es 

 http://www.lacralo.org 

[[--Original text (es)
http://mm.icann.org/transbot_archive/b5f44c197f.html
--]]