...
Do you have an incident response plan? | answer | location |
---|---|---|
SIR | yes | Información sobre el soporte de SIRTFI en las federaciones SIR/SIR2 (in Spanish; see the wiki link for a deeper explanation –in Spanish, too–) |
InCommon | yes | InCommon Incident Response Handling Framework |
SIFULAN Malaysian Access Federation | yes | |
Litnet FEDI | yes | |
Fédération Éducation-Recherche | yes | |
SWAMID | yes | https://www.sunet.se/swamid/incidenthantering/ (in Swedish with a short startup introduction in English) |
IDEM | yes | |
SURFconext | yes | https://wiki.surfnet.nl/display/surfconextdev/Sirtfi+and+SURFconext |
KAFE | yes | |
DFN-AAI | yes | https://www.aai.dfn.de/en/security/ |
Australian Access Federation | yes | https://aaf.edu.au/support/notices.html |
AFIRE | yes | |
OMAN-KID | yes | |
WAYF | yes | |
SWITCHaai | yes | SWITCH has an internal document on how to handle an incident. This would also be used for federation related incidents. |
edu.id Luxembourg | yes | |
Haka | yes | |
AAI@EduHr | yes | |
ARNaai | yes | |
IRFED | yes | We plan to assemble a security team from federation members in future, and until then we use operator's security team to handle federation security incidents |