Filtering Artifacts in Driftnet: Add to Query vs. Add Filter
A quick demonstration of the two ways to filter results in Driftnet while pivoting on artifacts and when to use each one.
Step 1: Two Kinds of Filters
There are two main ways to narrow down results in Driftnet:
- Add to Query: adjusts your overall query as you go, permanently changing what the query returns.
- Add Filter: doesn’t change your query it only changes the data presented in the current tab.
Both are adjustable and can be applied as positive or negative additions.
Step 2: Starting Point for the Can of Worms Query
The demo starts from a query built from recent Can of Worms research: leaf certificate issuer data found across all the certificates presented in that mesh network.
From there, going to Internet Wide Scans and clicking Visible Services shows 899 current visible services (within the last several days) presenting this information. That’s not the same as unique IPs the Summary page shows 450 unique IPs, since each IP can present more than one service with this data. In fact, the research found that each IP typically had two or three different services tied to this signature.
Step 3: Applying a Filter (Non-Destructive)
To narrow in on a specific service in this case, the Squid Cache proxy HTTP service used across almost all of the detected nodes click into one of the results. From there you can see:
- The issuer and subject data
- The server banner (Squid)
- The product tag (Squid Cache)
- A more specific tag (Squid HTTP proxy)
Clicking the Squid HTTP proxy tag opens a dropdown with three options: add to query, exclude from query, or apply as a filter.
Applying it as a filter reloads the page and cuts the results from 899 down to 417 more than half showing only services that present this signature. The filter tag appears at the top, but critically, the underlying query hasn’t changed: going back to the Summary page still shows the full 450 IPs. Removing the filter and reloading brings the count right back to 899.
This is useful for filtering through a long list of artifacts without altering the original query helpful when you’re not sure yet whether a narrower view is the direction you want to commit to.
Step 4: Adding to the Query (Persistent)
If you decide the narrower view is exactly what you want, click the same Squid HTTP proxy tag and choose add to query instead. The query itself now updates to include both the original issuer information and the new product tag.
The visible results are the same 417 as the filtered view, but this time the change is persistent: the Summary page now shows only 417 IPs the other 33 no longer appear, since they don’t present this service.
When to use which:
- Use add to query when you want to permanently narrow your search as you go.
- Use apply as a filter when you want to explore within a fixed dataset without altering the original query, so you don’t lose access to the full result set.
Step 5: Excluding from the Query
The same dropdown also supports the opposite move. Selecting exclude from the query on the Squid HTTP proxy tag adds it to the query as a negative condition rather than a positive one.
The query now reads as the original issuer data, excluding services that present the Squid HTTP proxy signature. This surfaces 482 services that do not show that signature likely the SOCKS proxy services also seen in the research. This is a fast way to zero in by ruling artifacts out rather than filtering them in.
Step 6: Starting a Fresh Search
If you want to look at a signature more broadly outside the context of the original research middle-clicking new search summary opens a new tab with a query built from only that one filter, no longer scoped to the original leaf certificate data.
For example, applying this to the Squid HTTP proxy tag opens a new search showing all services across the wider internet not just the ones tied to the original research that have presented that product tag within the last ten days, along with the full summary of IPs behind them.
Step 7: Using Filters to Test Query Changes
Filters are also a safe way to preview a query change before committing to it. For example, applying subject certificate information (in addition to the existing issuer data) as a filter showed no change in results at all. That confirmed the issuer and subject data were identical across these certificates — so adding it to the query permanently was safe, and it produced the same results.
That covers the core ways to filter artifacts in Driftnet: apply a filter to explore without commitment, add to or exclude from the query to make it permanent, or spin up a fresh search to look at a signature with no scope restrictions at all.