Differences

This shows you the differences between two versions of the page.

--- public:contactlist [2007-06-06 11:28] – Lofar admin
+++ public:contactlist [2025-07-15 14:18] (current) – [Wiki administrator] Adriaan Renting
@@ Line 1: / Line 1: @@
 ====== Contact list ======
 ===== Wiki administrator =====
-Your Wiki administrator is [[schoenmakers@astron.nl|Arno Schoenmakers]]. In his absence, contact [[grit@astron.nl|Teun Grit]] or [[holties@astron.nl|Hanno Holties]].
+Your Wiki administrator is Adriaan Renting. In his absence, contact Marco Drost.
+===== Observatory contact persons for LOFAR =====
-===== Lofar Internet Security Incident Response Team =====
+Note: There also is a [[:operator:contactinfo_people|restricted page for internal use]] (with nice pictures and such).
+<code>
-  * This is a [[securityresponseteam|list of people]] responsible for dealing with LOFAR network security.
+\\  ^ Observatory points of contact for LOFAR operations                                ^^
-  * Teun Grit (administrator),  0521-595717, 0593-332394, 06-25018054, grit@astron.nl
+</code>
-  * John Romein (chair), 0521-595792, romein@astron.nl
-  * Chris Broekema, 0521-595181, 050-3639347, broekema@astron.nl
-The Lofar organization has installed an Internet Security Incident Response Team (IRT). This team consists of
+| Operator on duty (access to systems, status updates, etc.) | Jurjen, Richard, Henk, Paul\\
-  * John Romein (group leader)
+(control room phone +31 521 595 701) |
-  * Chris Broekema (R&D scientific programmer)
-  * Teun Grit (System administrator)
-  * Roel Gloudemans (external advisor)
-This team is responsible for dealing with time critical computer security related incidents (hacks/abuse/denial of service) . The tasks of this team are purely reactional. Creation of a security policy and a secure infrastructure is left te systems management. The team is a temporary organization until a LOFAR security policy is agreed upon, but the team has received permission from management to disable any Lofar service needed to avoid further damage.
+|Science Operations and Support  |Roberto Pizzo  |
+|Operations, General  |Marco Drost  |
+|Operations, Software & ICT  |Jasper Annyas  |
+^Observatory contact persons for LOFAR (sub) systems  ^|
+|Infrastructure  |Jan Pieter de Reijer  |
+|Station Systems/Analogue (Antenna & Receiver)  |Menno Norden  |
+|Station Systems/Digital (Digital Processing)  |Menno Norden  |
+|CEP (Processing Resources) & WAN  |Jasmin Klipc, Walter Greenwood|
+|LTA (Data Storage & Access)  |Hanno Holties, Jasmin Klipic, Walter Greenwood  |
+|OLAP, SAS/MAC, User Software  |Arno Schoenmakers, Auke Klazema  |
+|Offline Processing (FSI)  |Adriaan Renting, Jorrit Schaap  |
-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/service restoration is also left to systems management)
-* Communicate with LOFAR management and local authorities (if allowed by LOFAR management)
-* Communicate with managers of infrastructures around the LOFAR network (Astron/RUG/Sara)
-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.**