3 ms·
Looks neat, very clean. What factors go into determining whether an IP is a threat, and how often is this reviewed? One of the problems I have with most publi
by jstarfish 9y ago
Looks neat, very clean.
What factors go into determining whether an IP is a threat, and how often is this reviewed?
One of the problems I have with most public intel (don't care if it's FireHOL, Crowdstrike, Alienvault or US-CERT) is that inevitably some GoDaddy (for example) site gets used by an APT and so a GoDaddy IP makes it onto a public blacklist, flagged as being abusive. But a billion other sites also share that IP on that host (or it gets reassigned, as in AWS) which leads to a deluge of false positives anytime anyone else happens across it by means of a legitimate site. Some of these IPs remain blacklisted for years despite any malicious infrastructure long being dismantled.
Do you add any value by mitigating this, or do you just suck down the same public blacklists every other product uses?
- jonathan-kosgei 9y agoThanks! You make a valid point. A number of VPN providers for example use GCE/AWS/Softlayer to host their services. And these IPs do get reassigned. One of the ways we mitigate this is by limiting the age of IP addresses in our lists to a maximum of 30 days. If an IP address hasn't been reported to have been responsible for malicious behavior for a period of 30 days it shouldn't be in our lists. We're also mulling adding an is_cloud_provider field to the threat response object.
- taf2 9y agois_cloud_provider, would be great!
- jonathan-kosgei 9y agoThanks for the feedback!We'll probably push this by the weekend :)