Versions Compared

Old Version 50

changes.mady.by.user Marina Adomeit

Saved on

compared with

New Version 51

changes.mady.by.user Stefan Winter

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...


Data itemIs personal data ?
1-5Dataset 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)

  • Whether it is enabled or not
  • max number of users per institution profile
  • EAP termination settings
No
7

Deployment details of Managed IdP for institution

  • whether the admin has accepted the system's ToU
  • (pseudonymous) usernames of the institution's users
  • expiry date of said pseudonymous usernames
  • list of eduroam credentials issued to these users (properties of these credentials in 8, below), linked to the respective username
  • list of pending invitation tokens with which users can create new credentials and inquire about their account status (properties of invitation toekns in 9, below)
  • status of the usernames (active, inactive)
  • data freshness: when were the set of users last checked by the administrator for continued validity?
Yes because of pseudonymous usernames ?
8

eduroam credentials (X.509 certificates)

  • unique, randomly generated username as certificate Subject (original pseudonymous username is not contained, but system maintains an internal link between pseudonymous username and the Subject of the certificate)
  • date of issue and expiry of certificate
  • unique, randomly chosen serial number for certificate
  • device type for which certificate was generated
  • revocation status of certificate
  • invitation token (see 9, below) which was used to generate certificate
?
9

end-user invitation tokens (URLs with unique, random long identifier)

  • pseudonymous username to which invitation token pertains
  • number of devices which can be credentialed witht his token
  • expiry date of invitation token
?
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

  • logs the timestamp when a revocation assertion was requested for a given eduroam credential - revocation assertions typically coincide exactly with the actual authentication happening on the RADIUS server. Does not log the actual revocation state that was returned.

eduroam Managed SP


eduroam Managed SP Operations
Local hotspot
Dataset description:Logs from the Managed SP RADIUS ServersLogs from the hotspot's APs/controllers
Purpose of processing:

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:

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 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:

No

No
Data retention:?

Depends on local the policy.

Personal data processed:YesYes


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

  • Data item: a specific dataset item. It may be an attribute, component or structure within a dataset that can be clearly described in terms of content. If attribute, it is usually described with the formally assigned name and corresponding explanation of meaning, purpose, expected content or allowed values. Property values characterise all or some items (records, members...) within the dataset.
  • Is personal data (DPO fills in): whether this item is (a part of) personal data. Decided and entered by the GÉANT Data Protection Officer while analysing the GDPR requirements. Answer Yes of No.

...