-- draft --
goal is to evaluate the service level, recognise excellence and identify possible weak spots all in order to maintain and improve the over quality of the service
once a year - initial audit (2 months) + audit for those who failed (1 month)
requirements and recommendations = norms = MUST, SHOULD, MAY
audit marks:
audit results:
audit tools:
audit process:
Number | Name | Description | Status | Tools |
---|---|---|---|---|
1 | policy | NRO has signed the appropriate version of the policy | MUST | OT checks in official archive |
policy | NROs should appoint at least one representative to the eduroam SG | SHOULD | OT checks meeting participation | |
policy | Scheduled maintenance work performed by the NRO within the respective federation should be announced two (2) days in advance through the SG mailing list. For unscheduled maintenance the announcement should preferably be made 24 hours in advance. A ticket on TTS should be opened by the respective NRO representative, and closed with a short comment on the performed action. | SHOULD | OT checks SG mailing list archive and TTS as well as outages in the FTLR connections from the monitoring systems | |
policy | NROs should regularly report to the OT about the number and type of security incidents | SHOULD | OT cross-checks its archives with other security incident archives |
Number | Name | Description | Status | Tools |
---|---|---|---|---|
1. | Physical signage | NRO advises member organisations to deploy physical signage in areas where eduroam is available (e.g. to assist visitors with medical prosthetics) | Should | Evidence: copy of documentation/web page |
eduroam Compliance Statement https://www.eduroam.org/support/eduroam_Compliance_Statement.pdf
European Confederation eduroam policy https://www.eduroam.org/wp-content/uploads/2016/05/GN3-12-194_eduroam-policy-for-signing_ver2-4_1_18052012.pdf
eduroam Service Definition https://www.eduroam.org/wp-content/uploads/2016/05/GN3-12-192_eduroam-policy-service-definition_ver28_26072012.pdf