Draft available at https://docs.google.com/document/d/176vzNaoK6KvKTMp8Glk2n1NaM6bxiS1QqH8M3_mu7NI/edit#
Objective
Provide new or evolving Research Communities and Infrastructures with the guidance they need to develop a complete policy suite supporting Federated Identity Management. This should be done with input from the wider community, through FIM4R, WISE and relevant bodies. For this work in AARC, the policy kit should be tightly scoped to the blueprint architecture but there is an expectation that the work be extended to be relevant for infrastructures in general.
Audience
Operational Management of Research Communities and their respective infrastructures
Process
- Identify key actors in Blueprint Architecture (Membership Manager, Proxy Operator, etc)
- Identify Policies Required for Compliance with Snctfi
- Identify Example Policies from other infrastructures to serve as inspiration
- Produce a training module to enable Research Communities to have a basic starter pack for policies
- Encourage RC actors to make policy decisions (e.g. log retention, minimum assurance etc)
- Translate those decisions into policy templates
Assumptions
- RCs/Infrastructures may not have a security focussed person, could just be a PI. Definitely can't assume CSIRT body
- Those using this policy pack are following the AARC blueprint
Pre-Requisites
- Stable DP CoCo Version
- Aligned AUP AARC Deliverable
Use Cases
- EPOS
- Life Sciences
- HelmHoltz Data Federation
Roles
- PI/Membership Manager (including Security Contact)
- Proxy Operator
- Users
- Service Management (including Security Contact)
- Infrastructure Management (including Security Contact)
Next Steps
- Design a top level policy, either modular or verbose
- Add templates for easy wins (IR, AUP, Privacy Policy from CoCo, Membership Management )
- More difficult modules (Authentication Assurance - Uros Stevanovic)
Which policies do we need?
| Policy Need | Source | Template Basis | Audience | Comment | Name | What should we produce? |
|---|---|---|---|---|---|---|
| Incident Response Procedure | Sirtfi | EGI Incident Response, should link to Sirtfi, AARC work | Proxy, Services | What about policies? | Incident Response Procedure | Template |
Policy on authentication, for all Constituents | Snctfi | EGI Operational Security Policy | Proxy, Services | Top level policy that covers physical and network security, vulnerability handling and refers to additional policies on Acceptable Assurance, Incident Response Procedure, Membership management We either make very modular or try to make this quite long | Top Level Policy | Template |
| AUP for end users | Snctfi | WISE Baseline AUP | Users | EGI seems to have 2 AUPS, Infrastructure and User Community | Infrastructure AUP | Template |
| Collections of users' aims and purposes | Snctfi | This is the User Community AUP. There is an example somewhere. Would be better if these could be combined. | ||||
Policies and procedures regulating the behaviour of the management of the Collection of users | Snctfi | EGI Membership Management | In XSEDE it's much more simple | Membership Management | Template | |
Data Protection Policy, e.g. DP CoCov2 | Snctfi | CoCo | Could be included in top level | Data Protection Code of Conduct | Framework description | |
Privacy Policy | CoCo | CoCo Template | Privacy Policy | Template | ||
| Policy on eligibility to join the infrastructure (i.e. services) | Elixir | NOT Similar to EGI Service Operations, there is some overlap with the Top Level Policy. Try and include in overall policy | Service Eligibility | Template | ||
| Risk Assessment (DPIA) | Data Privacy Statement | ?? | NOT A POLICY but could inform policy decisions | ?? | ?? |
Example Policy Sets
Differences with EGI Policies?
- Cannot assume a CSIRT for each Infrastructure
- Assume there is one AUP
- Resource Centres are not relevant
- There are not necessarily multiple User Communities