Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

EGI-Engage:TASK JRA1.1 Proposal for Levels of Assurance

From EGIWiki
Revision as of 17:34, 25 November 2016 by Skanct (talk | contribs)
Jump to navigation Jump to search
EGI-Engage project: Main page WP1(NA1) WP3(JRA1) WP5(SA1) PMB Deliverables and Milestones Quality Plan Risk Plan Data Plan
Roles and
WP2(NA2) WP4(JRA2) WP6(SA2) AMB Software and services Metrics Project Office Procedures


This wiki pages is a work in progress and it contains a draft proposal for the categorization of the levels of assurance in the scope of the EGI CheckIn service. The CheckIn service aggregates authentication and authorization information from different sources, which have different levels of assurance and may release only a subset of the required attributes. The combined information from the aggregated sources of authentication information results in an overall LoA that is embedded in the assertion sent to the services provider in the EGI Federation.

Level of Assurance

This section contains the proposed categories of level of assurance as interpreted and published by the EGI AAI Proxy (CheckIn service).

LoA: null

This category groups the credentials with basically no LoA associated. Examples are social-identity credentials with no vetting and no uniqueness of the ID guaranteed.

This catogory does not allow to access most of the EGI services, but could be used to access read-only open datasets and track in a qualitative way the number of accesses to a dataset. No sensitive activities can be accessed with this basic credential.

For this category no LoA is assigned

LoA: A

This category groups accounts coming from Identity Providers, which participate in one of the eduGAIN Federations

This category is expressed with LoA: A

LoA: B

This category groups accounts coming from Identity Providers, which support SIRTFI and the Research & Scholarship Entity Category

This category is expressed with LoA B and it is equivelant to IGTF DOGWOOD

LoA: 3

This category groups credentials with an higher LoA for both the authentication and the attributes distributed in the assertion. At the moment EGI does not have use cases for an higher LoA than #2 but some applications have stricter requirements and therefore a placeholder is created. Service providers in EGI shall not expect LoA higher than #3


REF1: AARC MNA3.1:Recommendations on Minimal Assurance Level Relevant for Low-risk Research Use Cases

Notes and comments

Side discussion about LoA definitions

Currently we are using Low/Substantial/High:

Proposal to use 4 levels:

History of edits

First version from Peter Solagna 30-09-2016