Difference between revisions of "Verify Configuration Records"
Jump to navigation
Jump to search
Line 38: | Line 38: | ||
|NGI_AEGIS | |NGI_AEGIS | ||
|https://ggus.eu/index.php?mode=ticket_info&ticket_id=127562 | |https://ggus.eu/index.php?mode=ticket_info&ticket_id=127562 | ||
| | |SOLVED | ||
|- | |- | ||
|NGI_ARMGRID | |NGI_ARMGRID | ||
Line 50: | Line 50: | ||
|NGI_CH | |NGI_CH | ||
|https://ggus.eu/index.php?mode=ticket_info&ticket_id=127565 | |https://ggus.eu/index.php?mode=ticket_info&ticket_id=127565 | ||
| | |In progress | ||
|- | |- | ||
|NGI_CHINA | |NGI_CHINA |
Revision as of 09:37, 20 April 2017
2017-04-07
On a yearly basis, the information registered into GOC-DB need to be verified. NGIs and RCs have been asked to check them. In particular:
- NGI managers should review the people registered and the roles assigned to them, and in particular check the following information:
- ROD E-Mail
- Security E-Mail
- NGI Managers should also review the status of the "not certified" RCs, in according to the RC Status Workflow;
- RCs administrators should review the people registered and the roles assigned to them, and in particular check the following information:
- telephone numbers
- CSIRT E-Mail
- RC administrators should also review the information related to the registered service endpoints.
The process should be completed by Apr 28th.
To track the process, the following tickets have been opened: