...
logs of ETLR servers (contain IPaddress, MAC address, outer-identity, CUI, ON, ...)
| GEANT central ops | NROs | IdPs | SPs | |
| Dataset description: | Logs from the European top level servers | Logs from the national radius servers | Logs from the IdP radius server | Logs from the SP radius server |
| 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. Logs of all authentication requests and responses SHOULD be kept. The minimum log retention time is six months, unless national regulations require otherwise. The information in the requests and responses SHOULD as a minimum include:
Troubleshooting issues and resolving security incidents. Requirement by the eduroam service definition. fff The time the authentication request was exchanged. The value of the User-Name attribute in the request ('outer EAP-identity').
Troubleshooting issues and resolving security incidents. Requirement by the eduroam service definition. Sufficient logging information MUST be kept to be able to correlate between a client’s layer 2 (MAC) address and the layer 3 (IP) address that was issued after login if public addresses are used. This requirement is void if NAT is used. | |
| Data source: | Data is logged in the ETLR servers when an RADIUS authentication or response passes. (user access eduroam in another country) | Data is logged in the FTLR server(s) when an RADIUS authentication or response passes. (user accesses eduroam in another institution) | Data is logged in the IdP RADIUS server(s) when an RADIUS authentication or response passes. (user accesses eduroam anywhere) | Data is logged in the SPs RADIUS server(s) when an 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: | ? | Depends on 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 policy. | Personal data processed: | Yes | Yes | Yes | Yes
Troubleshooting issues and resolving security incidents. Requirement by the eduroam service definition. | ||||
| Data source: | Data is logged in the ETLR servers when an RADIUS authentication or response passes. (user access eduroam in another country) | Data is logged in the FTLR server(s) when an RADIUS authentication or response passes. (user accesses eduroam in another institution) | Data is logged in the IdP RADIUS server(s) when an RADIUS authentication or response passes. (user accesses eduroam anywhere) | Data is logged in the SPs RADIUS server(s) when an 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: | ? | Depends on 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 policy. |
| Personal data processed: | Yes | Yes | Yes | Yes |
Dataset content
| Data item | central ops | NRO | IdP | SP | Is personal data (DPO fills in) | |
|---|---|---|---|---|---|---|
| 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-Iidentity - username@institution_domain | |||||
| 4 | Calling-Station-Id - users MAC address |
| ||||
| 5 | Authentication result |
| ||||
| 6 | Chargeable-User-Identity - users anonymous ID |
| ||||
| 7 | IP address assigned by the SP after the sucessfull authenticaiton |
|
|
|
eduroam F-ticks
Data is processed by GEANT central ops and NROs.
| 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 |
Dataset content
| Data item | Is personal data (DPO fills in) | |
|---|---|---|
| 1 | REALM - As in users EPPN used for the authentication (for example “@education.lu”) - contains the user’s country of origin and the institution of origin | No ? |
| 2 | Calling-Station-Id - User’s device MAC address | No ? |
| 3 | Viscountry - ISO country code of the NRO that generated the log message | No ? |
| 4 | Visinst - Identifier of visited institution i.e. operator-name RADIUS attribute | No ? |
| 5 | Result - Authentication outcome: OK / FAIL | No ? |
...
| Dataset description: | National Roaming Operator information. |
| Purpose of processing: | Data is used to feed the central data repository for eduroam service. It provides information about National Roaming Operators that participate in the eduroam service. The data is used for providing public available information about eduroam service, available at https://monitor.eduroam.org/. |
| Data source: | The eduroam database has been build as a central database with the mechanism that enables automatic data collection from (National) Roaming Operators - (N)ROs. (N)ROs should provide general data in the defined XML or JSON format. The data should be available at the specific, predefined URLs: http://www.eduroam.<tld>/general/<dataset-name>. |
| Data storage and access: | Data is 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. |
| Data transfer: | Data is not transferred to any other party or system. |
| Data retention: | Data is kept permanently. |
| Personal data processed: | Yes |
Dataset content
| Data item | Is personal data (DPO fills in) | Comment | |
|---|---|---|---|
| 1 | ROid - Unique identifier provided by the database operator during the RO registration | No | |
| 2 | country - two letter country code | No | |
| 3 | stage - 0=preproduction/test, 1=active | No | |
| 4 | org_name - (N)RO corporate name | No | |
| 5 | address_street - (N)RO address | No | |
| 6 | address_city - (N)RO address | No | |
| 7 | coordinates - longitude, latitude, altitude | No | |
| 8 | contact_name - (N)RO contact: name | Yes | If contact is person |
| 9 | contact_email - (N)RO contact: e-mail | Yes | If contact is person |
| 10 | contact_phone - (N)RO contact: phone no. | Yes | If contact is person |
| 11 | contact_type - 0=person, 1=service/department | No | |
| 12 | contact_privacy - 0=private, 1=public | No | |
| 13 | info_URL - (N)RO web page URL | No | |
| 14 | policy_URL - (N)RO Policy URL | No | |
| 15 | ts - date: last changed | No |
...
Data is processed by the eduroam central operations and NROs
| GEANT central operations | NROs | |
| Dataset description: | Institution information (IdP or SP), participating in eduroam service. | Institution information (IdP or SP) participating in eduroam service and belonging to the given NRO. |
| Purpose of processing: | Data is used to feed the central data repository for eduroam service. It provides information about Institutions that participate in the eduroam service as IdPs and SPs. The data is used for providing public available information about eduroam service, available at https://monitor.eduroam.org/. | Data is requested by the eduroam service definition. |
| Data source: | The eduroam database has been build as a central database with the mechanism that enables automatic data collection from (National) Roaming Operators - (N)ROs. (N)ROs should provide general data in the defined XML or JSON format. The data should be available at the specific, predefined URLs: http://www.eduroam.<tld>/general/<dataset-name> | Data is collected from the institutions participating in the eduroam in that NRO. Exact process is a matter of local implementation in a NRO. |
| Data storage and access: | Data is 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. | Data is stored in the national eduroam web site. Data access is public. Additional storing locations may be implemented based on NROs practices. |
| Data transfer: | Data is not transferred to any other party or system. | - |
| Data retention: | Data is kept permanently. | |
| Personal data processed: | Yes | Yes |
Dataset content
| Data item | Is personal data (DPO fills in) | Comment | |
|---|---|---|---|
| 1 | instid - provided by the NRO | No | |
| 2 | ROid - Unique identifier provided by the database operator during the RO registration | No | |
| 3 | type - IdP, SP, IdP+SP | No | |
| 4 | stage - 0=preproduction/test, 1=active | No | |
| 5 | inst_realm - (only for IdP or IdP+SP) | No | |
| 6 | inst_name - institution’s corporate name | No | |
| 7 | address_street - institution’s address | No | |
| 8 | address_city - institution’s address: city | No | |
| 9 | coordinates - longitude, latitude, altitude of institution’s location | No | |
| 10 | inst_type - IEEE 802.11-2012, clause 8.4.1.34 Venue Info | No | |
| 11 | contact_name - institution’s contact: name | Yes | If contact is person |
| 12 | contact_email - institution’s contact: e-mail | Yes | If contact is person |
| 13 | contact_phone - institution’s contact: phone no. | Yes | If contact is person |
| 14 | contact_type - 0=person, 1=service/department | No | |
| 15 | contact_privacy - 0=private, 1=public | No | |
| 16 | info_URL - institution’s web page with the information related to the service | No | |
| 17 | policy_URL - institution’s Policy | No | |
| 18 | ts - date: last changed | No |
eduroam Database - Service Location information
| GEANT central ops | NROs | |
| Dataset description: | Service Location information | Service Location infromations, from SPs belonging to the given NRO. |
| Purpose of processing: | Data is used to feed the central data repository for eduroam service. It provides information about Service Locations that are provided in eduroam by participating SPs. The data is used for providing public available information about eduroam service, available at https://monitor.eduroam.org/. | Data is requested by the eduroam service definition. |
| Data source: | The eduroam database has been build as a central database with the mechanism that enables automatic data collection from (National) Roaming Operators - (N)ROs.(N)ROs should provide general data in the defined XML or JSON format. The data should be available at the specific, predefined URLs: http://www.eduroam.<tld>/general/<dataset-name>. | Data is collected from the service providers participating in the eduroam in given NRO. Exact process is a matter of local implementation in a NRO. |
| Data storage and access: | Data is 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. | Data is stored in the national eduroam web site. Data access is public. Additional storing locations may be implemented based on NROs practices. |
| Data transfer: | Data is not transferred to any other party or system. | - |
| Data retention: | Data is kept permanently. | |
| Personal data processed: | Yes | Yes |
Dataset content
| Data item | Is personal data (DPO fills in) | Comment | |
|---|---|---|---|
| 1 | instid - provided by the NRO | No | |
| 2 | ROid - Unique identifier provided by the database operator during the RO | No | |
| 3 | locationid - provided by the NRO | No | |
| 4 | coordinates - longitude, latitude, altitude | No | |
| 5 | stage - 0=preproduction/test, 1=active | No | |
| 6 | type - 0=single spot; 1=area; 2=mobile | No | |
| 7 | loc_name - location’s name | No | |
| 8 | address_street - location’s address | No | |
| 9 | address_city - location’s address: city | No | |
| 10 | location_type - IEEE 802.11-2012, clause 8.4.1.34 Venue Info | No | |
| 11 | contact_name - on site contact: name | Yes | If contact is person |
| 12 | contact_email - on site contact: e-mail | Yes | If contact is person |
| 13 | contact_phone - on site contact: phone no. | Yes | If contact is person |
| 14 | contact_type - 0=person, 1=service/department | No | |
| 15 | contact_privacy - 0=private, 1=public | No | |
| 16 | SSID - SSID used | No | |
| 17 | enc_level - supported encryption levels | No | |
| 18 | AP_no - number of APs | No | |
| 19 | wired_no - number of enabled sockets for wired access | No | |
| 20 | tag - specific characteristic(s): port_restrict, transp_proxy, IPv6, NAT, HS2.0 | No | |
| 21 | availability - 0=default, 1=physical access restrictions | No | |
| 22 | operation_hours - If service is not available 24 hours per day | No | |
| 23 | info_URL - info page with additional info in case of any restrictions | No | |
| 24 | ts - date: last changed | No |
...
| Dataset description: | |
| Purpose of processing: | |
| Data source: | |
| Data storage and access: | |
| Data transfer: | |
| Data retention: | |
| Personal data processed: |
Dataset content
| Data item | Is personal data (DPO fills in) | |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 |
...