Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spamhaus ASN Drop list - json format #8391

Open
2 tasks done
ronin3510 opened this issue Mar 3, 2025 · 1 comment
Open
2 tasks done

Spamhaus ASN Drop list - json format #8391

ronin3510 opened this issue Mar 3, 2025 · 1 comment

Comments

@ronin3510
Copy link

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

Spamhaus DROP ASN announcement

Further to requests from the community we've reinvigorated the ASN-DROP. With a new >algorithm, ASN-DROP is now available in JSON format, listing ASNs associated with the worst of the worst behavior. These are ASNs that our researchers wouldn’t recommend engaging with and are >highly likely to announce or supply transit to IP ranges associated with malicious behavior. From networks hosting botnet command and >control systems, to "bulletproof" networks selling connectivity/hosting to cybercriminals, to hardcore spammers, and more.

Describe the solution you like

Adding support for this ASN list presents a double opportunity for OPNsense CE and BE.

In the first stage, the new functionality is announced - hopefully in a yy.m.x release - users can start using it.

In the second stage, new yy.m releases start presenting the users with a new screen in the initial setup wizard where the users are being prompted to enable this ASN list as a Floating rule on LAN - "Reject Source any Destination ASNdrop any". A floating rule can then be modified easily to add additional VLANs when they're deployed.

Implementing the second stage raises the bar of the default security posture and is a mitigating factor for the default Allow Any Outbound IPv4+IPv6 rules that may allow for unwanted data exfiltration when new deployments happen on compromised networks.

Describe alternatives you considered

There's always the manual option, which is error prone, untimely and time consuming: collecting the ~300 ASNs and adding it to a ASN alias.

Additional context

DROP ASN json

Thank you.

@ronin3510
Copy link
Author

Tried opening this as a feature request...doesn't seem to have worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant