[RSSAC Caucus] Security Incident Reporting Work Party Update

[Dessalegn Yehuala]

Here is a security incident report that supports our approach(covering
indirect incidents), i.e., including security incidents related to critical
infrastructure components upon which the RSS relies.

https://status.ripe.net/incidents/l3cz0rry823k

Dessalegn


On Tue, Apr 16, 2024 at 4:06 PM Ken Renard <kdrenard2 at gmail.com> wrote:

> On Tue, Apr 16, 2024 at 8:03 AM Robert Story <rstory at ant.isi.edu> wrote:
>
>> [..]
>> A random thought popped into my head while typing this response. I just
>> added a comment in section 5 (What to report): Thoughts on having two
>> severity impact fields: RSS impact, and RSO impact?
>>
>
> My opinion is to keep reporting focused only on the RSS.
>
> -Ken
> _______________________________________________
> rssac-caucus mailing list
> rssac-caucus at icann.org
> https://mm.icann.org/mailman/listinfo/rssac-caucus
>
> _______________________________________________
> By submitting your personal data, you consent to the processing of your
> personal data for purposes of subscribing to this mailing list accordance
> with the ICANN Privacy Policy (https://www.icann.org/privacy/policy) and
> the website Terms of Service (https://www.icann.org/privacy/tos). You can
> visit the Mailman link above to change your membership status or
> configuration, including unsubscribing, setting digest-style delivery or
> disabling delivery altogether (e.g., for a vacation), and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/rssac-caucus/attachments/20240422/aab3b8d5/attachment.html>