[NCSG-PC] [idea] Meeting with Dan Halloran?

[Ayden Férdeline]

I actually don't want to speak to him about WHOIS. I'm curious about what ICANN is doing internally to make sure it complies with the GDPR in its broader operations.

I thought it would be useful to ask Halloran questions that are within his scope of work. Is ICANN revising its privacy policy, for instance, and if so, what protections, if any, will it extend to registrants and to the community? What data does ICANN hold on community members, and how is it safeguarded (i.e. who has access to our constituency travel data? how are records for special travel accommodations, i.e. because of medical need, protected?)

In the Budget, resources are allocated to private investigations. Who is ICANN investigating? I've always presumed the backgrounds of incoming Board members or staff but we've never clarified this, I don't think. Does ICANN keep tabs on individual community members as a part of the threat/risk assessments that the Security Operations team conducts? In the January 2018 Executive Team report, this department mentioned providing internal teams with "security intelligence" and said they "provided successful safety and security support at various events including Board Workshop in Montevideo, ICANN60 in Abu Dhabi, Afrinic in Lagos, Nigeria, the DNS Forum in Minsk, Belarus, and the IGF in Geneva, Switzerland; [and] conducted site visits of Puerto Rico and Panama for ICANN61 and 62 respectively." They seem to be very thorough, so it would seem a gap in their work to not sometimes be paying attention to meeting delegates. How do they keep their intelligence reports safe, who can access them, and what personal data is inside of them? We know that ICANN maintains briefing notes on panelists speaking at conferences where senior ICANN staff will be present; does ICANN org similarly keep dossiers on community members, for instance?

To be very clear, these are just questions. I am not suggesting there is anything happening which is improper. I'm just wondering what data the organisation holds on us and whether they even know, too. This needs to be mapped...

Ayden

-------- Original Message --------
On 23 February 2018 5:04 AM, farzaneh badii <farzaneh.badii at gmail.com> wrote:

> Yes that is what I want to know too. because as always their response would be they are not interested in GDPR. so what specific questions do you have that is within his mission?
>
> Farzaneh
>
> On Thu, Feb 22, 2018 at 11:03 PM, Rafik Dammak <rafik.dammak at gmail.com> wrote:
>
>> Hi,
>>
>> if I am not mistaking Dan while he is the CDPO for  ICANN, he is not involved in GDPR which is the most pressing issue for us. Do we have something in particular for him as questions or is it seen as introduce him to NCSG?
>>
>> Best,
>>
>> Rafik
>>
>> 2018-02-23 12:59 GMT+09:00 farzaneh badii <farzaneh.badii at gmail.com>:
>>
>>> Stephanie, your response does not answer any of my serious questions about NCSG open meeting. Also I would like to know what want to talk about with Halloran.
>>>
>>> Farzaneh
>>>
>>> On Thu, Feb 22, 2018 at 9:41 PM, Stephanie Perrin <stephanie.perrin at mail.utoronto.ca> wrote:
>>>
>>>> Let me guess Ayden...it has been a really long day and your inner piranha is emerging....:-)
>>>>
>>>> Sure, lets do that.  I can take my inner piranha out for a walk as well.....
>>>>
>>>> cheers Steph
>>>>
>>>> On 2018-02-22 19:09, Rafik Dammak wrote:
>>>>
>>>>> Hi Ayden,
>>>>>
>>>>> Thanks,
>>>>> I guess that is for the NCSG meeting during constituency day, Farzaneh may respond to that since she is working on the agenda.
>>>>>
>>>>> Best,
>>>>>
>>>>> Rafik
>>>>>
>>>>> 2018-02-23 5:38 GMT+09:00 Ayden Férdeline <icann at ferdeline.com>:
>>>>>
>>>>>> Just had a thought - in San Juan, why don't we invite ICANN's newly appointed Chief Data Protection Officer to join us for half an hour to listen to us and to perhaps answer some of our questions; might make for an interesting conversation...
>>>>>> Ayden
>>>>>>
>>>>>> _______________________________________________
>>>>>> NCSG-PC mailing list
>>>>>> NCSG-PC at lists.ncsg.is
>>>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>>>
>>>>> ______________________________
>>>>>
>>>>> _________________
>>>>> NCSG-PC mailing list
>>>>> NCSG-PC at lists.ncsg.is[https://lists.ncsg.is/mailman/
>>>>>
>>>>> listinfo/ncsg-pc](https://lists.ncsg.is/mailman/listinfo/ncsg-pc)
>>>>
>>>> _______________________________________________
>>>> NCSG-PC mailing list
>>>> NCSG-PC at lists.ncsg.is
>>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
>>>
>>> _______________________________________________
>>> NCSG-PC mailing list
>>> NCSG-PC at lists.ncsg.is
>>> https://lists.ncsg.is/mailman/listinfo/ncsg-pc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ncsg.is/pipermail/ncsg-pc/attachments/20180223/61208fdf/attachment.htm>