Hi Michele
Yes you can allow any customer with an assignment to have their own
abuse-c contact. But the database query will only return a single
abuse contact for any IP address. If the assignment object has an
abuse-c then a query on any IP address in the range of that assignment
will only return
There are many things to consider (some semi random topics to consider).
* what do you consider abuse?
* only technical abuse (portscanes, spam, brute force attacks etc)
* or also 'content abuses' (doxxing, hate speech, csam etc)
* what about harmful content, will that be considered abuse
*
Am 10.02.22 um 10:25 schrieb Brian Nisbet:
Colleagues,
Since we last spoke about the proposed training the NCC have been working with various community members to put a
draft syllabus in place for further discussion.
This is a link to the feedback document for this draft:
https://docs.google
Michele Neylon - Blacknight via anti-abuse-wg wrote on 10/02/2022 10:49:
I also find the ridiculously broad definition of abuse so broad that it
renders any output without much merit.
"It's always DNS!"
A comparable style of analysis could find that TCP was a good root cause
candidate for abu
That’s not entirely true.
It’ll depend on how granular the LIR is with their allocations to their clients.
Speaking on behalf of my company we do assign blocks and abuse-c contacts to
quite a few of our clients.
However we wouldn’t do that for every single IP address and due to the nature
of so
Exactly
And unfortunately this is a trend with a lot of the EC’s activities that push
towards more and more regulation of digital
I also find the ridiculously broad definition of abuse so broad that it renders
any output without much merit.
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Co
Colleagues,
Since we last spoke about the proposed training the NCC have been working with
various community members to put a draft syllabus in place for further
discussion.
This is a link to the feedback document for this draft:
https://docs.google.com/document/d/1M9Wrqu-VKGGwMfJQGK0NlTs5UzH6