Security Duty

From GridPP Wiki
Jump to: navigation, search


This provides guidance for the UK NGI Security team and what the person on UK security duty should do in the absence of the GridPP Security Officer.

UKNGI Security duty rota is at SD rota

Note that this is different from the EGI CSIRT rota duty.

EGI meetings

The GridPP Security Officer attends the EGI CSIRT and IRTF meetings. Other NGI security team members are not currently expected to attend EGI security meetings as part of their team duties.

Security Duty tasks

  • Respond to any e-mails to UKNGI-Security list which require a response. If a UK site needs help which you do not have the knowledge to give, ask the other UKNGI-Security members or CSIRT. Be particularly prepared to ask if sites need help dealing with incidents, critical vulnerabilities, or interpreting information sent from CSIRT to site security contacts.
  • Respond if a security incident is reported in the UK NGI. If this happens you will probably have a busy week! See more information here about procedures for reporting and handling incidents.
  • Take care to take note of anything that is going on in CSIRT, especially incidents that may affect UK NGI
  • and update the live minutes for that meeting.
  • Be aware of any interesting meetings or other information relevant to the UKNGI security team, and briefly inform the team.

Dashboard checking

When on duty check the Security Dashboard. This is now a separate panel on the same page as the ROD dashboard

Other sources of monitoring information to check include:

Critical Vulnerabilities from Pakiti are handled by EGI CSIRT duty person, and are not the UK duty responsibility. However, a polite "heads-up" to the site can sometimes be useful in avoiding a ticket (but check More Notes below on timings).

Note that the Security Dashboard results are built by combining EGI Pakiti with additional, targeted EGI Nagios tests for in-place mitigation. The Security Dashboard actually fetches its results from EGI Nagios, not directly from the EGI Pakiti server. This means that machines reported as vulnerable by Pakiti may not appear on the Security Dashboard. The result is that the Security Dashboard is generally the authoritative source.

For UK NGI Vulnerabilities which are 'High' inform sites if they remain for a day. (These should show in Pakiti)

Similarly for Nagios. Note that Nagios errors reporting 'Critical' e.g. CRL, file permission etc are handled by us. These are not what are meant by Critical Vulnerabilities.

Find the CSIRT contact for the site in the GOCDB, send e-mail to them, CC UKNGI-security

Security Duty Templates may help you draft appropriate mails.

Handover report

On Friday, just before you go home, please provide a brief report on what has happened during your duty week to ukngi-security at This will assist the GridPP Security Officer and/or the follow-on rota duty person in understanding what is going on. Provide this report anyway, even if 'nothing to report'.

Be prepared to give a brief summary of relevant information at the UK Security Team meetings if appropriate.

More notes

Emails to CSIRT lists may set off alarms to on-call site security teams so communications should be sent well within office hours unless it is urgent and should not be left until the next working day.

Examples of what may be sent at any time and should not be left until the next working day (but always keep EGI CSIRT informed):

  • Updates to ongoing incidents which the site may be involved in.
  • Advisories on Critical vulnerabilities which are known to be being aggressively exploited.

Examples of what should be sent during office hours

  • Advisories less than 'Critical'
  • Information on ongoing incidents which don't require immediate response.

Emails to individuals may obviously be sent as you wish.

Always CC anything appropriate to UKNGI-Security.

Common sense is an appropriate tool!

Useful links

EGI csirt public wiki CSIRT Public Wiki

EGI CSIRT private wiki CSIRT Private Wiki

GridPP Wiki Security Information

This page is a Key Document, and is the responsibility of David Crooks. It was last reviewed on 2018-01-16 when it was considered to be 90% complete. It was last judged to be accurate on 2018-01-16.