12.07.2015 Views

Minutes of the 1st TF-CSIRT meeting - Terena

Minutes of the 1st TF-CSIRT meeting - Terena

Minutes of the 1st TF-CSIRT meeting - Terena

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

close colleagues in <strong>the</strong> NRENs who were working on PKI and setting up a certificationauthority.Karel Vietsch mentioned that PKI/CA had come up recently in a number <strong>of</strong> TERENAactivities: in <strong>TF</strong>-<strong>CSIRT</strong> but also in <strong>the</strong> Middleware Workshop and in <strong>the</strong> new TERENATask Force on LDAP service deployment. Adjacent to <strong>the</strong> TERENA General Assembly<strong>meeting</strong> in Paris in October <strong>the</strong>re would be a mini-symposium on PKI with speakers fromCREN and IBM. TERENA planned to set up a separate activity for harmonisationbetween PKI/CA work <strong>of</strong> NRENs in Europe.There followed a discussion as to whe<strong>the</strong>r a PKI hierarchy should be set up for <strong>CSIRT</strong>sin Europe. Could <strong>the</strong> TI act as a certification authority for this community? Don Stikvoortfelt that technically it would not be difficult to issue certificates but managerially it was acompletely different matter. For <strong>the</strong> moment this seemed like a bridge too far. It wasagreed to discuss this matter fur<strong>the</strong>r at <strong>the</strong> next <strong>TF</strong>-<strong>CSIRT</strong> <strong>meeting</strong>; Don Stikvoort andChristoph Graf would prepare that discussion.The third session had been on <strong>the</strong> Incident Description and Exchange Format, with YuriDemchenko presenting <strong>the</strong> draft and participants in <strong>the</strong> <strong>meeting</strong> providing usefulfeedback.8. Security contact entry in <strong>the</strong> RIPE databaseIn <strong>the</strong> previous <strong>meeting</strong> Wilfried Wöber had volunteered to take on this action item, butunfortunately he could not attend this <strong>meeting</strong>. Shortly before <strong>the</strong> <strong>meeting</strong> he had sent aprogress report by e-mail, but that report consisted mostly <strong>of</strong> an object format descriptionand it was unclear exactly what <strong>the</strong> current status <strong>of</strong> <strong>the</strong> discussion in RIPE was. It wasalso not clear if <strong>the</strong> discussion in <strong>TF</strong>-<strong>CSIRT</strong> could be postponed until <strong>the</strong> next <strong>meeting</strong> ordecisions would have to be taken before <strong>the</strong>n.Gorazd Bozic would ask Wilfried Wöber to explain <strong>the</strong> current status on <strong>the</strong> <strong>TF</strong> -<strong>CSIRT</strong>mailing list, and <strong>the</strong>n conduct <strong>the</strong> discussion fur<strong>the</strong>r on that mailing list.9. Requirements for a Training Workshop for New (Staff <strong>of</strong>) <strong>CSIRT</strong>sIn <strong>the</strong> previous <strong>meeting</strong> it had become clear that whe<strong>the</strong>r existing <strong>CSIRT</strong>s would beinterested to send <strong>the</strong>ir new staff to a training workshop depended very much on <strong>the</strong>content and form <strong>of</strong> <strong>the</strong> workshop. It had been decided to discuss <strong>the</strong> requirements forsuch a workshop in this <strong>meeting</strong>.Andrew Cormack reported that he had learned from CERT/CC that <strong>the</strong>y are consideringfranchising <strong>the</strong> training courses that <strong>the</strong>y had organised before in Pittsburgh. It wasunclear if <strong>TF</strong>-<strong>CSIRT</strong> could use that material; some <strong>of</strong> it might be useful. It was remarkedthat <strong>the</strong>se courses are long (3 days) and expensive. Andrew Cormack would find outmore about <strong>the</strong>m.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!