...
GEANT central ops | NRO | IdP | SP | |
Dataset description: | Logs from the European top level RADIUS servers (ETLR) | Logs from the national top level RADIUS server(s) (FTLR) | Logs from the IdP RADIUS server(s) | Logs from the SP RADIUS server(s) |
Purpose of processing: | Troubleshooting issues and resolving security incidents. | Troubleshooting issues and resolving security incidents. Recommendation by the eduroam Service Definition. | Troubleshooting issues and resolving security incidents. Requirement by the eduroam Service Definition. | Troubleshooting issues and resolving security incidents. Recommendation by the eduroam Service Definition. Requirement by the eduroam Service Definition is to keep the logs of public IP addresses assigned to users and its relation to users MAC address. |
Data source: | Data is logged in the ETLR servers when a RADIUS authentication or response passes (user accesses eduroam in another country) | Data is logged in the FTLR server(s) when a RADIUS authentication or response passes (user accesses eduroam in another institution) | Data is logged in the IdP RADIUS server(s) when a RADIUS authentication or response passes (institution user accesses eduroam anywhere) | Data is logged in the SPs RADIUS server(s) when a RADIUS authentication or response passes. (user accesses eduroam at that SPs location) |
Data storage and access: | Data is stored in the ETLR servers, accessible only to the eduroam operational team personnel. | Data is stored in the FTLR server(s), accessible only to the NRO operational team personnel. (This may vary based on local practices) | Data is stored in the IdP server(s), accessible only to the IdP operational team personnel. (This may vary based on local practices) | Data is stored in the SP server(s), accessible only to the IdP operational team personnel. (This may vary based on local practices) |
Data transfer: | No | No | No | No |
Data retention:? | All data related to roaming are kept for a period of six months. | Depends on the local policy. eduroam Service Definition recommendation is: The minimum log retention time is six months, unless national regulations require otherwise | Depends on the local policy. eduroam Service Definition recommendation is: The minimum log retention time is six months, unless national regulations require otherwise. | Depends on local the policy. eduroam Service Definition recommendation is: The minimum log retention time is six months, unless national regulations require otherwise. |
Personal data processed: | Yes | Yes | Yes | Yes |
...
Data item | Is personal data? | ||||
central ops | NRO | IdP | SP | ||
---|---|---|---|---|---|
1 | Timestamp - The time the authentication request was exchanged i.e usert tried to access the eduroam service | ||||
2 | Outer EAP-identity - username@institution_domain, username can be anonymised but not all users do that | ||||
3 | Inner EAP-identity - username@institution_domain | ||||
4 | Calling-Station-Id - users MAC address, MAC address can be randomized but that's not the default in all clients | ||||
5 | Authentication result | ||||
6 | Chargeable-User-Identity - users anonymous ID | ||||
7 | IP address assigned by the SP after the sucessfull authenticaiton, including its relation to users MAC address |
|
eduroam F-ticks
GEANT central ops | NROs | |
Dataset description: | Usage log messages for each international and national roaming authentication request. | Usage log messages for international and national roaming authentication request coming from IdPs belonging to that NRO. |
Purpose of processing: | Log data provides basic statistical information about service usage. It provides statistics about the number of logins for national and international roaming. The data is used for generation of usage statistics that are publicly available at https://monitor.eduroam.org and for reporting to EC and other stakeholders. | Log data provides basic statistical information about the service usage. It provides statistics about the number of logins for national and international roaming. The data is sent to the GEANT central operations as requested by the eduroam service definition. Depending on the NRO practices, the data can processed by the NRO for creating usage statistics. |
Data source: | NROs Federation top level Radius servers. | F-ticks data are generated by the data from RADIUS authentication requests or responses sent by the IdP, and that transverses the NROs Federation top level Radius servers. This happens in the event when a user access eduroam at a visited SP location and authenticates. |
Data storage and access: | F-ticks data are stored in the SQL database that is operated in the infrastructure provided by CARNet. The raw data is accessible only by the personnel of eduroam operations team. | Depending on the NRO practices, data can be kept and stored by NRO as well. |
Data transfer: | F-ticks data are not transferred to any other party or system. | F-ticks data are sent to the eduroam core operations. |
Data retention: | F-ticks data are kept permanently. | Depends on the NRO practices if they keep a copy and for how long. |
Personal data processed: | Yes | Yes |
...
Data item | Is personal data? | Comment | |
---|---|---|---|
1 | REALM - As in users EPPN username used for the authentication (for example “@education.lu”) - contains the user’s country of origin and the institution of origin | Yes | |
2 | Calling-Station-Id - User’s device MAC address | Yes | |
3 | Viscountry - ISO country code of the NRO that generated the log message | Yes | No (VP proposal) |
4 | Visinst - Identifier of visited institution i.e. operator-name RADIUS attribute | Yes | No (VP proposal) |
5 | Result - Authentication outcome: OK / FAIL | No |
...
Dataset description: | Configuration Assistant Tool operator database (NRO administrator and institution-level administrator) |
Purpose of processing: | allowing administrators to upload and maintain the information needed to create eduroam installation programs ("installers") within their country / institution |
Data source: | eduroam database - NRO information & institution information (see datasets above), eduroam SP proxy authentication data (see dataset above), administrator input, produces web server and application logs (cat-ams.eduroam.org) |
Data storage and access: | Data is stored in the SQL database on the virtual machine that is operated in the infrastructure provided by SURFNETSURF. The raw data is accessible only by the personnel of eduroam operations team. The virtual machine is maintained by the OT. |
Data transfer: | System sends emails with invitation tokens (one variant to institution administrators for sign-up, one variant to NRO personnel for general status updates) |
Data retention: |
|
Personal data processed: | Yes |
...
Dataset description: | eduroam Managed IdP is a derivative of eduroam CAT (see above), which additionally produces per-user personalised installation programs and maintains a database of these end users. It also authenticates the end users based on the installed programs |
Purpose of processing: | allowing administrators to upload and maintain the information needed to manage their end user base to the end of creating eduroam installation programs ("installers") within their country / institution, and to authenticate their users in eduroam |
Data source: | eduroam database - NRO information & institution information (see datasets above), eduroam SP proxy authentication data (see dataset above), administrator input, produces web server and application logs (cat-pilot.eduroam.org / auth-test.hosted.eduroam.org / auth-test-2.hosted.eduroam.org / ocsp-test.hosted.eduroam.org) |
Data storage and access: | this needs to be filled in by the sys admins of the servers - not yet decided where exactly the production servers will be,but in principle same info as for CAT Data is stored in the database on the virtual machine that is operated in the infrastructure provided by GÉANT. The raw data is accessible only by the personnel of eduroam operations team. The virtual machine is maintained by the OT. |
Data transfer: | System sends emails with invitation tokens (one variant to institution administrators for sign-up, one variant to end-users for credentialing, one variant to NRO personnel for general status updates) |
Data retention: |
|
Personal data processed: | Yes |
...
Data item | Is personal data ? | |
---|---|---|
1-5 | Dataset content items 1 to 5 are IDENTICAL to those of eduroam CAT (see above) | Yes |
6 | Deployment details of Managed IdP for NRO (from NRO admin input)
| No |
7 | Deployment details of Managed IdP for institution
| Yes because of pseudonymous usernames ? |
8 | eduroam credentials (X.509 certificates)
| ? |
9 | end-user invitation tokens (URLs with unique, random long identifier)
| ? |
10 | RADIUS authentication logs The RADIUS server is an eduroam IdP in the sense of the dataset "eduroam RADIUS server logs → IdP" above, and the same data set considerations apply. | Yes |
11 | certificate status server logs
|
eduroam Managed SP
eduroam Managed SP Web Frontend | eduroam Managed SP RADIUS Servers | Local hotspot | |
Dataset description: | Data required to manage deployment properties of eduroam Managed SP hotspots | Logs from the Managed SP RADIUS Servers | Logs from the hotspot's APs/controllers |
Purpose of processing: | Allowing hotspot administrators to log into the system, add/edit/delete their Managed SP deployment, and to check usage logs of their hotspot | Troubleshooting issues and resolving security incidents. Recommendation by the eduroam Service Definition. | Troubleshooting issues and resolving security incidents. Requirement by the eduroam Service Definition is to keep the logs of public IP addresses assigned to users and its relation to users MAC address (no requirement imposed when using NAT). |
Data source: | eduroam database - NRO information & institution information (see datasets above), eduroam SP proxy authentication data (see dataset above) administrator input web server and application logs | Data is logged in the Managed SP RADIUS servers when a RADIUS authentication or response passes (user accesses eduroam at a hotspot connected to Managed SP) | Data is logged in the equipment when a RADIUS authentication or response passes (user accesses eduroam at that SPs location) |
Data storage and access: | Data is stored in the database on the virtual machine that is operated in the infrastructure provided by GÉANT. The raw data is accessible only by the personnel of eduroam operations team. The virtual machine is maintained by the OT. | Data is stored in the Managed SP RADIUS servers, accessible to the eduroam operational team personnel and the registered hotspot operator | Data is stored in the equipment, accessible only to the hotspot operating personnel. |
Data transfer: | System sends emails with invitation tokens (one variant to institution administrators for sign-up, one variant to end-users for credentialing, one variant to NRO personnel for general status updates) | No | No |
Data retention: |
| ? | Depends on local the policy. |
Personal data processed: | Yes | Yes | Yes |
Dataset content
Data item | Component | Is personal data ? | |
---|---|---|---|
1 | eduPersonTargetedId or equivalent user identifier Of NRO or SP administrator | eduroam Managed SP Web Frontend | Yes |
2 | First name and Last name Of NRO or SP administrator | eduroam Managed SP Web Frontend | Yes |
3 | Of NRO or SP administrator | eduroam Managed SP Web Frontend | Yes |
4 | Outer EAP-identity Users username@institution_domain, username can be anonymised but not all users do that | eduroam Managed SP RADIUS Servers | Yes |
5 | Calling-Station-Id Users MAC address | eduroam Managed SP RADIUS Servers | Yes |
6 | Chargeable-User-Identity Users anonymous ID | eduroam Managed SP RADIUS Servers | Yes |
Description of fields
The details of service related datasets (data collections) should be filled with a list of all kinds of data which is collected or processed by this service. The table should be filled by the Service Manager and afterwards reconciled with the GEANT Data Protection Officer in order to address GDPR requirements. One service often incorporates several datasets. <dataset_name> - name of dataset (collection of data processed in similar way). Dataset description: brief explanation of the kind of information or entities the dataset contains. Purpose of processing: what is purpose of data collecting and processing. Data source: what are source(s) of data - list of services, systems, applications, databases or similar source components, including user's input, from which data are being received. E.g. RIPE database, service ABC, organisation LDAP directory... Data storage and access: describe where the data are stored, backup-ed etc. and who has access to the data. Data transfer: list of other services, systems, applications, databases or similar destinations to which data are being sent. E.g. RIPE database, service ABC, GÉANT's database XYZ... Data retention: describe data retention policy ie. for how long data are stored before being deleted. E.g. 1 year, 2 years after contract ending, forever... Dataset content
|
...