Repository navigation
Category known shared infrastructure - #460
Merged
Merged
Conversation
…ists as `known` MISP core has a `warninglists.category` column validated against `false_positive` / `known`, but no shipped list set it, so every list defaulted to `false_positive`. Lists describing shared or multi-tenant infrastructure (cloud/CDN ranges, URL shorteners, dynamic DNS, VPN providers, research scanners, sinkholes, ...) do not mean "this value is a false positive": a report naming it as malicious can still be true, acting on it just has collateral. - schema.json: admit an optional `category` (enum false_positive|known) - README: document the field - 25 lists: set `"category": "known"` and bump `version` so consumers re-import them - generators for the generated ones (aws, azure, gcp, cloudflare, akamai, stackpath, disposable-email, vpn, tenable, check-host-net) emit the field so it survives the next regeneration Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…`known` Found while reviewing the remaining lists against the same test (can a report naming the value as malicious still be true?): - smtp-sending-ips, google-gmail-sending-ips: free-mail/ISP SPF ranges; phishing sent from free-mail accounts really originates there - microsoft-office365-ip, microsoft-office365-cn: EOP outbound and SharePoint/OneDrive, routinely used for tenant-sent phishing - zscaler: cloud proxy egress shared by every customer, same shape as the VPN provider lists smtp-receiving-ips and the Office 365 URL list stay `false_positive`. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…-infrastructure Conflicts were the refreshed lists and three generators. Resolution: - lists: take main's content, re-apply `"category": "known"`, and bump `version` to 20261014 (above main's latest, 20261012) - generate-akamai/-vpn/-zscaler: take main's version, re-add `category` - generate-vpn now also writes datacenter-ipv4/6 (split out of the old "VPN providers and datacenters" list), so those lists are flagged `known` as well - new generators for roster lists (ovh, fastly, public-ipfs-gateways) emit `category`; openfilters-scanners carries an existing list's category over like it already does for name/description, so censys-scanning keeps it. dynamic-dns and sinkholes regenerate from the committed list and keep it unchanged. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…s introduced Applied the same test to the 136 lists main gained: can a report naming the value as malicious still be true? `known` (118 lists): - cloud / VPS: alibaba-cloud, coreweave, digitalocean, godaddy, hetzner, huawei-cloud, ibm-cloud, leaseweb, linode, oracle-oci, rackspace, scaleway, tencent-cloud, vultr - CDN / WAF: bunny-net, cachefly, cdn77, gcore, imperva, sucuri - multi-tenant platforms: github, salesforce, telegram-ips, lots-project - anonymising egress: tor-exit-nodes, icloud-private-relay - every scanner list (*-scanning, *-nt-scanning, driftnet, modat-scanner, onyphe-scanner, internetcleanup-scanner, shadowserver, circl-*, palo-alto-networks-cortex-*, umich-cse-connection-attempts), as for censys-scanning and tenable-cloud-* Left `false_positive` (18): cisco_top1m and cloudflare-top* (popularity), apple-domains / apple-ipv4 / apple-ipv6 (vendor, like apple/google/ microsoft), microsoft-win11-connection-endpoints, microsoft-mdca-proxy, windows-binary-hashes. Generators emit the field so it survives regeneration; openfilters- scanners defaults new scanner lists to `known` while keeping an existing list's category. telegram-ips regenerates from the committed list and keeps it as is. google-vpn's generator is covered too, though its list is not committed yet. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.