The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "EGI CSIRT:Monitoring"
| Line 1: | Line 1: | ||
{{Egi-csirt-header}} | {{Egi-csirt-header}} | ||
= About EGI-CSIRT Security monitoring activities = | |||
See the description of the [[EGI_CSIRT:SMG|Security Monitoring Group]] for general description of the activity. | See the description of the [[EGI_CSIRT:SMG|Security Monitoring Group]] for general description of the activity. | ||
Revision as of 17:01, 14 September 2011
| Mission | Members | Contacts
| Incident handling | Alerts | Monitoring | Security challenges | Procedures | Dissemination
About EGI-CSIRT Security monitoring activities
See the description of the Security Monitoring Group for general description of the activity.
Security monitoring with Nagios
Pakiti
Pakiti is a client-server tool to collect and evaluate data about packages installed on Linux machines, primarily meant to identify vulnerable SW that have not been properly updated. The EGI CSIRT operates the EGI Pakiti instance that is used to monitor the state of the EGI sites.
A site can also choose to install its own Pakiti instance. There is a documentation guide available from the Pakiti homepage that describes the steps needed to deploy the server and clients. The Nagios probes used to launch the Pakiti client in the EGI are also available. Note, the Pakiti distribution available at the moment doesn't support all the features supported by the EGI instance of Pakiti, nevertheless it is fully working and can be used to monitor the site status.
Currently we are working on the new version of the Pakiti v3, more information is available here.