You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 4
Next »
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.
Background
The REFEDS Assurance Framework defines 2 profiles covering identification and subsequent authentication -
- Cappuccino profile for low risk use cases
- Espresso profile for demanding use cases
Further information: Draft Assurance Framework (Presentation / Document )
Use Cases
Community | ELIXIR AAI |
---|
Contributor | Pre-existing information to be updated or refined |
---|
Description | ELIXIR 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. |
---|
References | Full discussion of senarios and problems are discussed in this document (google doc) together with the pilot roadmap (google doc). |
---|
Community | BBMRI |
---|
Contributor | Pre-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.)
|
---|
References | See document (Overleaf doc). |
---|
Community | Community Name |
---|
Contributor | Your Name |
---|
Description | ... |
---|
References | URLs |
---|
Community | Community Name |
---|
Contributor | Your Name |
---|
Description | ... |
---|
References | URLs |
---|
Community | Community Name |
---|
Contributor | Your Name |
---|
Description | ... |
---|
References | URLs |
---|