...
- Read the initial Baseline Assurance requirements coordinated by major RIs and e-Infrastructures in our MNA3.1 document
- Participate in the process to establish differentiated assurance profiles
- Support the design and requirements gathering of a self assessment tool for assurance profiles and best practices in federations
- Support the development of higher assurance through an inventory of use cases for AARC2 communities (which will be the basis for evaluation of e.g. RAF Espresso suitability)
Exchange of assurance information between Infrastructures
See the draft AARC guideline JRA1.1A. In support of the inter-infrastructure use cases and the BPA, Guideline G021 on the exchange of specific assurance information has been adopted by AEGIS. These guidelines SHOULD be used when exchanging assurance information between SP-IdP-Proxy components of Infrastructures (“Infrastructure Proxies”), and MAY be used when conveying assurance information between an SP-IdP-Proxy and service providers that are part of a coordinated set or consortium and bound to one or more Infrastructure Proxies.
If the exchange involves authentications involving user-held credentials based on social media accounts (like Google, LinkedIn, Facebook, &c), also take Guideline G041 into account, which describes bow REFEDS RAF assurance components should be expressed by the BPA Proxies and how these may be combined on 'outbound' assertions.
Differentiated LoA recommendations
...