This Wiki is available to view but still under maintenance. PLEASE DO NOT EDIT THE WIKI UNTIL FURTHER NOTICE. We are attempting to restore missing edits which took place between Monday 8 and Thursday 11 April 2019, therefore the site is likely to be taken off line at any time. Updated 20:43 CEST 16 April 2019.
Child pages
  • Federation Incident Response Plans
Skip to end of metadata
Go to start of metadata
Do you have an incident response plan?answerlocation
SIRyes 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–)
InCommonyesInCommon Incident Response Handling Framework
SIFULAN Malaysian Access Federationyes
Litnet FEDIyes
Fédération Éducation-Rechercheyes
SWAMIDyeshttps://www.sunet.se/swamid/incidenthantering/ (in Swedish with a short startup introduction in English)
IDEMyes
SURFconextyeshttps://wiki.surfnet.nl/display/surfconextdev/Sirtfi+and+SURFconext
KAFEyes
DFN-AAIyeshttps://www.aai.dfn.de/en/security/
Australian Access Federationyeshttps://aaf.edu.au/support/notices.html
AFIREyes
OMAN-KIDyes
WAYFyes
SWITCHaaiyesSWITCH has an internal document on how to handle an incident. This would also be used for federation related incidents.
edu.id Luxembourgyes
Hakayes
AAI@EduHryes
ARNaaiyes
IRFEDyesWe 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




  • No labels