...
| Name of NREN/Project/Institute | Example Project Institute Homepage |
|---|---|
| General Overview | Public link for this project or NREN |
| Security Emergency contact | How to contact in an emergency E.g. E-mail(s) or link to instructions |
| How to report a security incident | Incident reporting e-mail(s) preferably, and/or links to instructions |
| RFC 2350 | Link to relevant public document if you have one, or who to contact |
| Security officer | individual e-mail if you wish, some make public, some don't |
| Data Protection Officer (GDPR) | |
| Hosting Organisation | |
| Who is in charge of the NREN/Project | Could include deputies |
| ISM | Link to ISM for this project, or person to contact if not public |
| Policy Documents (incl. AUP) | Link to policy docs for this project, or person to contact if not public |
| Software Vulnerability handling | Link to procedure/web, or who to contact |
| Security Monitoring | Link to security monitoring information, if present, or who to contact |
| Other incident Prevention | Any other incident prevention work |
| Incident handling | Incident handling procedure - if public, if not who to contact |
| Any other contact information | As you wish |
| Compliance with standards | Standards complied with, including |
| ipv4/ipv6 prefixes | (more suitable for NRENs or sites than very dist. infrastructures) |
| Identity information | |
| Authorization information | |
| Links to blogs, reports, anything you wish. | |
| Other functions | |
| Individual members | (as you wish) |
| Projects people work on | (if you wish) |
| People's expertise | |