As more communities share their science resources through the federation, data of higher value, or in need of specific controls (such as biomedical data, but obviously much more), will change the risk assessment that underlies the baseline and differentiated assurance developed in AARC.

The policy harmonisation work package (NA3) seeks input on requirements from communities seeking to implement strong assurance profiles, e.g. "Espresso" or with even higher assurance components, to support their AAI. Please edit this page and provide your input (description and/or links) under "Use Cases" below.

Background

The REFEDS Assurance Framework defines 2 profiles covering identification and subsequent authentication -

Further information: Draft Assurance Framework (Presentation / Document  )

Use Cases

CommunityELIXIR AAI
ContributorPre-existing information to be updated or refined
DescriptionELIXIR AAI requires MFA when accessing sensitive data. Principal issues relate to which attribute is associated with the MFA, and what is the resultant reliability, usefulness and cost. A pilot has been run to test a preferred senario with MFA linked to ORCID ID.
ReferencesFull discussion of senarios and problems are discussed in this document (google doc) together with the pilot roadmap (google doc).


CommunityBBMRI
ContributorPre-existing information to be updated or refined
Description

Issues identified with the REFEDS AF are related to

  • lack of prescribed attributes and
  • timely removal of attributes (1 day required rather than 1 month following termination of employment.)
ReferencesSee document (Overleaf doc).


CommunityCommunity Name
ContributorYour Name
Description...
ReferencesURLs


CommunityCommunity Name
ContributorYour Name
Description...
ReferencesURLs


CommunityCommunity Name
ContributorYour Name
Description...
ReferencesURLs