Hi,

I'm new to this working group but I now realise it should have been on my
radar before, because my employer (BT) is a provider of security to
consumers and enterprises. But in my view everyone (people and
organisations) needs security from attack. So thumbs up for trying to
tackle that never-ending problem here, and reduce the world's vulnerability.

Regarding the draft that is the subject of an adoption call, it makes a lot
of sense to me. The pyramid is a useful way to think about the issue. I
also reviewed the minutes of the 111 meeting. Clearly there is a tension
between privacy of communication and the ability of a network to spot
indicators of compromise. I tend to agree that it requires research to
identify ways to do both or to strike the right balance. In my mind the
ideal is full privacy of end users while at the same time being able to
reliably identify compromise in a complex heterogeneous network. Is that
impossible? I don't know, but it's worth trying.

On that basis I support adoption of the draft as a way to clearly state
this need. I'd also be happy to discuss or contribute to the document.

Chris


Hello,
> Ths email starts the WG adoption call for the following document:
> Title: "Indicators of Compromise (IoCs) and Their Role in Attack Defence"
> Link: 
> https://datatracker.ietf.org/doc/draft-paine-smart-indicators-of-compromise/03/
> Please read the document and respond to the list with your comments.
> Please state if you support (or don't support) the adoption.
> Also, if you are willing to contribute to the document, please include
> it in your response.
> Thank you!
_______________________________________________
OPSEC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsec

Reply via email to