Project

General

Profile

Actions

Feature #7725

open

Import Metacentrum networks as an externally updated feed

Added by Pavel Kácha about 2 months ago. Updated 5 days ago.

Status:
Resolved
Priority:
Normal
Category:
Development - Tools
Target version:
Start date:
04/10/2024
Due date:
% Done:

0%

Estimated time:
To be discussed:
No

Description

Currently we have the GRID group. Unfortunately it's not curated/updated.
The "official" list is at "https://security.metacentrum.cz/export/metacentrum_hosts.csv", and we'd like it to

We could use mentat-netmgr machinery to import it as a new regularly updated feed.

That means downloading the CSV, adding correct contact information, spit it out as Negistry-like JSON and feed it tu mentat-netmgr. (Pretty much as Negistry import does it, just one more conversion step is needed.).

The target address is , however should get a copy for CESNET network (but I guess this should happen automatically as networks of Mentat group will be also consulted during reporting).


Related issues

Related to Mentat - Bug #7726: Import Casablanca network as an externally updated feedResolvedRajmund Hruška04/10/2024

Actions
Has duplicate Mentat - Bug #6209: Reenable Metacentrum network list updateClosed01/31/2020

Actions
Actions #1

Updated by Jakub Judiny about 2 months ago

  • Related to Bug #7726: Import Casablanca network as an externally updated feed added
Actions #2

Updated by Pavel Kácha about 1 month ago

Note from discussion: it might make sense to import CESNET-VIRTUAL* networks as a separate feed (from Meta iteself). (We now have a "Negistry-like" export with ambition to replace Negistry one, and CERTS members using that over OTRS can act a bit differently to general Meta/Grid clients and clean virtualisation machines.)

Actions #3

Updated by Pavel Kácha about 1 month ago

  • Has duplicate Bug #6209: Reenable Metacentrum network list update added
Actions #4

Updated by Rajmund Hruška about 1 month ago

Pavel Kácha, should this group map to __GRID__ group which we have in Mentat? Currently, __GRID__ is a manual group and its reporting setting for low is . Or should there be two groups, and the new one would be named and it should report to ?

Actions #5

Updated by Pavel Kácha about 1 month ago

The unmaintained GRID data should go away together with , no matter whether with group name or without, so we can keep the name or change it as we see fit.
I'd say to keep the name sufficiently different to make it visibly distinct, and I'd also vote for keeping new group names independent from mail address format (we've already decoupled it). However, dunders are unnecessary and quite superfluous, so I guess Metacentrum or Grid would do.
And target mail just (parent network mail would be carboncopied implicitly, I presume).

Actions #6

Updated by Rajmund Hruška about 1 month ago

  • Status changed from New to Resolved
Actions #7

Updated by Rajmund Hruška 27 days ago

  • Status changed from Resolved to In Review
Actions #8

Updated by Rajmund Hruška 6 days ago

  • Status changed from In Review to In Progress
Actions #9

Updated by Rajmund Hruška 5 days ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF