Page tree
Skip to end of metadata
Go to start of metadata

Central emergency suspension procedure

The document describing the central emergency suspension procedure is available at EGI CSIRT Operational Procedure for Compromised Certificates.

Argus Infrastructure Deployment

  • Central Argus Instance at CERN
  • NGI Argus Instance: EGI CoreArgus Service Group
    • All NGIs should run a Argus instance
    • NGIs that don't have a Site/RC that uses Argus don't need to run a Argus service
    • NGI Argus instance should be registered in GOC DB with service type ngi.ARGUS
    • The NGI-Argus servers have to be configured/maintained carefully. A potential attacker getting privileged access to this system could block all jobs that are submitted to the sites using this NGI-Argus service.
    • NGI-Argus Systems contain personal data and shall limit access this service to the site Argus (like) systems in the NGI.
    • ACLs can be constructed by pulling the list of egi.Argus'es for the resp. NGI from goc-db
  • Site Argus Instance
    • Sites in the NGIs pull policies from NGI Argus
    • Small sites that don't have the expertise to run a local Argus could use the NGI Argus
    • Site Argus instance should be registered in GOC DB with service type emi.ARGUS
  • Non Argus Sites/RCs

Argus Monitoring

NGI Argus Monitoring

The eu.egi.Argus-DNs metric checks if an Argus server is properly configured and still pulling suspension information from the Central Argus Instance.

Every day the Central Argus Instance suspends a new DN: the probe verifies if this DN is present on the NGI argus.

The return values of that probe can indicate the following problems:

Return valueProblemPotential solution
ARGUS WARN - connection errorThe probe was not able to connect to the Argus serverPlease make sure that the argus pap port (8150) is accessible remotely from argo-mon.egi.eu, argo-mon2.egi.eu and argo-mon-test.cro-ngi.hr
ARGUS WARN - Authorization errorThe probe was able to connect but was denied accessPlease make sure that the following certificates are given the "POLICY_READ_LOCAL|POLICY_READ_REMOTE|CONFIGURATION_READ" permissions are given to "/DC=EU/DC=EGI/C=HR/O=Robots/O=SRCE/CN=Robot:argo-egi@cro-ngi.hr" and "/DC=EU/DC=EGI/C=GR/O=Robots/O=Greek Research and Technology Network/CN=Robot:argo-egi@grnet.gr"
ARGUS CRIT - Expected DN not found!The probe didn't find a recent DN in the Argus configurationPlease check your argus logs to see what is blocking the synchronisation
ARGUS WARN - Found outdated DNThe probe only found an outdate DN and not the current onePlease check your argus logs to see what is delaying the synchronisation. The synchronisation delay might be too long
ARGUS OK - Found expected DNEverything is good!

The code of this probe can be found on the public repository of the security probes

For more details on the Argus configuration see bellow.

Site Monitoring

Site Arguses (or equivalent solutions) should not be exposed to the internet and thus cannot be directly monitored However the EGI CSIRT is considering submitting jobs from suspended DNs, but such monitoring of the sites' emergency suspension systems is not yet in place.

Argus Support

Support is provided through ARGUS Support unit in GGUS

Documentation

Documentation on possible problems and solutions with certain deployment scenarios are in Nikhef wiki, Argus Global Banning Setup Overview