[IntelMQ-users] Introducing proposals to IntelMQ Data Format (IEP008 and 9)

Homma, L.J. (Luitzen) l.j.homma at minezk.nl
Mon Nov 27 10:43:17 CET 2023


Great!
We are looking forward to it.

Kind regards,

Luitzen Homma

-----Oorspronkelijk bericht-----
Van: Kamil Mankowski <mankowski at cert.at> 
Verzonden: maandag 27 november 2023 10:12
Aan: Homma, L.J. (Luitzen) <l.j.homma at minezk.nl>; 'intelmq-users at lists.cert.at' <intelmq-users at lists.cert.at>
Onderwerp: Re: [IntelMQ-users] Introducing proposals to IntelMQ Data Format (IEP008 and 9)

Thanks for the reply! I'll implement the changes hopefully in this year

Best regards

// Kamil MaƄkowski <mankowski at cert.at> - T: +43 676 898 298 7204 // CERT Austria - https://www.cert.at/ // CERT.at GmbH, FB-Nr. 561772k, HG Wien

On 11/23/23 11:53, Homma, L.J. (Luitzen) via IntelMQ-users wrote:
> Hi Kamil,
> 
> Sorry for the late response. I just joined the mailing list. We think this would be a very nice feature to have.
> Since the current version does not have this option, we built our own complex routing.
> By making it possible to use a constituency field, it would make our routing less complex and more flexible.
> 
> Met vriendelijke groet,
> 
> Luitzen Homma
> 
> Digital Trust Center (DTC)
> 
> -----Oorspronkelijk bericht-----
> Van: mankowski at cert.at (Kamil Mankowski) <mankowski at cert.at 
> (Kamil Mankowski)>
> Verzonden: donderdag 2 november 2023 16:02
> Onderwerp: [IntelMQ-users] Introducing proposals to IntelMQ Data 
> Format (IEP008 and 9)
> 
> Dear IntelMQ Developers & Users,
> 
> I'd like to propose two changes to the IntelMQ data format to make it more suitable for current use cases.
> 
> 1. IEP008 - add constituency identifier (this has already been shared, 
> but only on the developer list): 
> https://github.com/certtools/ieps/pull/9
> 2. IEP009 - add product and vulnerability information:
> https://github.com/certtools/ieps/pull/10
> 
> I'd like to hear your feedback on these suggestions. Feel free to comment here or on the Github pull requests. My plan is to implement them, unless rejected, by December.
> 
> --
> Best regards,
> Kamil Mankowski
> CERT.at GmbH
> www.cert.at
> -------------- next part -------------- A non-text attachment was 
> scrubbed...
> Name: OpenPGP_signature.asc
> Type: application/pgp-signature
> Size: 833 bytes
> Desc: OpenPGP digital signature
> URL: 
> <http://lists.cert.at/pipermail/intelmq-users/attachments/20231102/464
> 4ae15/attachment.sig> Dit bericht kan informatie bevatten die niet 
> voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht 
> abusievelijk aan u is gezonden, wordt u verzocht dat aan de afzender 
> te melden en het bericht te verwijderen.
> De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard 
> ook, die verband houdt met risico's verbonden aan het elektronisch 
> verzenden van berichten.
> 
> This message may contain information that is not intended for you. If 
> you are not the addressee or if this message was sent to you by 
> mistake, you are requested to inform the sender and delete the message.
> The State accepts no liability for damage of any kind resulting from 
> the risks inherent in the electronic transmission of messages.
> 
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u
niet de geadresseerde bent of dit bericht abusievelijk aan u is gezonden,
wordt u verzocht dat aan de afzender te melden en het bericht te
verwijderen.
De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard
ook, die verband houdt met risico's verbonden aan het elektronisch
verzenden van berichten.

This message may contain information that is not intended for you. If you
are not the addressee or if this message was sent to you by mistake, you
are requested to inform the sender and delete the message.
The State accepts no liability for damage of any kind resulting from the
risks inherent in the electronic transmission of messages.


More information about the IntelMQ-users mailing list