Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Next revisionBoth sides next revision | ||
public:contactlist [2007-06-06 11:22] – created Lofar admin | public:contactlist [2017-04-26 08:39] – [Observatory contact persons for LOFAR] Reinoud Bokhorst | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Contact list ====== | ====== Contact list ====== | ||
+ | |||
===== Wiki administrator ===== | ===== Wiki administrator ===== | ||
- | Your Wiki administrator is [[schoenmakers@astron.nl|Arno Schoenmakers]]. In his absence, contact | + | Your Wiki administrator is Arno Schoenmakers. In his absence, contact Teun Grit or Hanno Holties. Emails can be sent to [[ro_wiki@astron.nl|this address]]. |
- | ===== Lofar Internet Security Incident Response Team ===== | ||
- | * Teun Grit (administrator), | + | ===== Observatory contact persons for LOFAR ===== |
- | * John Romein (chair), 0521-595792, | + | |
- | * Chris Broekema, 0521-595181, | + | |
- | The Lofar organization has installed an Internet Security Incident Response Team (IRT). This team consists of | + | Note: There also is a [[operator: |
- | * John Romein (group leader) | + | |
- | * Chris Broekema (R&D scientific programmer) | + | |
- | * Teun Grit (System administrator) | + | |
- | * Roel Gloudemans (external advisor) | + | |
- | This team is responsible | + | \\ |
+ | ^ Observatory points of contact | ||
+ | | Operator on duty (access to systems, status updates, etc.) | Geert, Jurjen, Richard, Henk, Paul\\ (phone +31 521 595 701) | | ||
+ | | Science Operations and Support | ||
+ | | Operations, General | ||
+ | | Operations, Software & ICT | Jasper Annyas | ||
+ | ^ Observatory contact persons for LOFAR (sub) systems | ||
+ | | Infrastructure | ||
+ | | Station Systems/ | ||
+ | | Station Systems/ | ||
+ | | CEP (Processing Resources) & WAN | Teun Grit, Reinoud Bokhorst | | ||
+ | | CEP (Data Storage & Access) | ||
+ | | OLAP, SAS/MAC, User Software | ||
+ | | Offline Processing (FSI) | Adriaan Renting | ||
- | So if any illegal activity is detected on the network or systems, try to alert your systems manager first, but if that is not possible, or you are the systems manager, alert the IRT immediately (contact details above). The team will then: | + | Interfaces to the non astronomical LOFAR applications still need to be defined. |
- | * Investigate the incident | + | |
- | * Take inventory of the damage | + | |
- | * Gather evidence | + | |
- | * Stop the illegal activity | + | |
- | * Advise systems management on how to stop the gap (system/ | + | |
- | * Communicate with LOFAR management and local authorities (if allowed by LOFAR management) | + | |
- | * Communicate with managers of infrastructures around the LOFAR network (Astron/ | + | |
- | The team will use a structured approach for each incident. If needed, this approach will be updated regularly to create a best practice which can be used in the operational phase of LOFAR. The team will also | ||
+ | |||
+ | |||
+ | ===== Lofar Internet Security Incident Response Team ===== | ||
+ | |||
+ | * This is the [[securityresponseteam|list of people]] responsible for dealing with LOFAR network security. | ||
**Any Lofar user who has an indication for abuse attempts on Lofar systems has the duty to warn one of the team members immediately.** | **Any Lofar user who has an indication for abuse attempts on Lofar systems has the duty to warn one of the team members immediately.** |