One of the major functions of the Firewalla is to manage traffic on your network, such as "rules", "routes" and "smart queue". All of these features require matching a "target" and applying an action to a device, a group, or a network segment. At the moment, to specify a target, the system only allows one IP/IP segment or one top-level domain. This results in more complex rules. Many of you suggested we should use a list instead.
Introducing Target List
A target list is a set of targets defined with domain(exact or all subdomains) or IP(exact or range), which can be used as a building block to create rules or prioritize a group of targets. If you have a lot of rules, this feature can help you to better organize them.
Firewalla Target List feature will allow you to
- Create your own target list to simplify rules.
- Use an existing pre-created list
Target Lists can be used with the following features
- Rules: access control, content filtering
- Smart Queue: regulate traffic flow
- Policy & Content-based Routing: routing of network traffic
Target List Definition:
- Target Lists can only be created and managed using the Firewalla Web interface
- Rules using Target Lists can be created/managed via the Firewalla Web or App
- Target List items for this version is restricted to 200 items
- Element of target list support following forms
- Exact-match IP - 1.1.1.1
- IP Range in CIDR notation - 192.168.0.1/24
- Exact-match domain- firewalla.com
- Match-all subdomains - *.firewalla.com
(ONLY support the exact form of a single '*.' before the domain name)
- You can only create up to 20 target lists
- Target List is NOT available on Firewalla Red.
Create Target List on Firewalla Web
Login to Firewalla web, click Target List on the left side, you'll see a list of pre-built target Lists owned by Firewalla.
Built-in Target Lists
These list items are maintained by Firewalla and you can use them where target lists are accepted (rules, smart queue, routes), while their definitions are kept proprietary.
| List Name | Description |
|---|---|
| Apple Private Relay |
Apple's iCloud Private Relay feature encrypts DNS requests. However, using it may mean that Firewalla has less information about network traffic and some of your policies may not work as intended. This target list blocks Apple's Private Relay Servers, banning their relay service and returning full visibility to your Firewalla.
|
|
Crypto List
|
This target list consists of known cryptocurrency mining sites and can be used to block cryptocurrency activities.
|
|
DShield Block List
|
DShield.org is a collaborative cyber threat logging system. We recommend that you block this list.
|
| DoH Services (beta) |
This is a list of well-known DNS-over-HTTPS (DoH) servers. Some browsers have built-in DoH services that encrypt DNS requests, which may get in the way of your rules and policies. You can block this list in order to prevent browser-based DoH from working and ensure that your rules will function as expected.
|
| OISD |
This OISD blocklist is a list of risky sites or sites that have unwanted content. You can read more at https://oisd.nl.
|
| Tor Exit Nodes |
A Tor exit node is the gateway between Tor encrypted traffic and the Internet. Blocking this list will block just these Tor nodes.
|
| Tor Full Nodes |
This list is of all Tor nodes. Be aware that this list is not just exit nodes.
|
| Log4j Attackers |
This is a list of known log4j attackers from a public list.
|
Create your Target Lists
To create your own, click the Create Target List button in the top right corner.
Security example: Here is an example where you can create a target list to identify the "Purple Fox" malware's command and control sites.
Parental Control Example: You can also create specific sites like "gaming" for kids.
Update a Target List
In addition to the web interface, on the Firewalla app, we've supported the ability to quickly add a domain or an IP address from a flow or an alarm to a target list you've created.
For example, if you already have a rule that blocks a list of targets, by simply adding a new domain to the target list, the rule will be updated automatically to block the new target.
Create Rules / Smart Queue/ Routes using Target List
On both Firewalla App and Web Interface, when you create a rule, a smart Queue rule, or a policy-based routing, you can choose to match a target list.
You can view the detail of the target list on the Firewalla App by tapping the "i" icon on the right side of any target list.
Example: Block iCloud Private Relay using pre-defined Target Lists
Apple iCloud Private Relay is one of the most exciting features coming in iOS 15 and macOS Monterey. It will encrypt and obfuscate your source IP address to protect your privacy while using Safari. This is perfect when you are using free Wi-Fi in a cafe or a store and you want to protect your privacy.
Unfortunately, this encryption will also block devices like Firewalla from operating at the network to filter and audit traffic.
Besides turning off iCloud Private Relay directly on your Apple devices, Firewalla has a way to disable the use of this feature on your network by creating a BLOCK rule using the pre-defined Firewalla target list called “Apple Private Relay”.
To create the rule, go to Rules -> Add Rule -> set the target to Target List " Apple Private Relay" -> apply to any device -> Save.
You can also block a list of IPs or domains from accessing a certain port on your local devices, by creating a rule matching a certain Local Port and a Target list.
Example: Prioritize traffic for online meetings
In addition to Firewalla's built-in Apps, you can create a target list and put all the sites you and your company are using for online meetings, then create a smart queue rule to prioritize the meeting traffic using the target list.
- Smart Queue -> Smart Queue rules -> Add Smart Queue Rule
- Set a target -> Target List -> Online Meeting
- Apply it to any devices/network you might use for online meetings.
- Set the Priority to High.
- Save the rule.
Example: Route your Netflix traffic to a certain VPN
If you want all the Netflix traffic on your Apple TV to go to a 3rd party VPN, you can create a target list with the primary domains Netflix is using, then create a policy-based routing rule using the target list.
- Routes -> Add Route
- Set a target -> Target List -> Netflix video
- Select a device -> MyMac
- Select a interface -> 3rd party VPN
- Save the Route
FAQ:
Do I need to import a security list for better security?
You do not have to. Behind Firewalla, there is a "huge list" already integrated with your box. This "huge list" is part of our Firewalla security intel. Please see https://help.firewalla.com/hc/en-us/articles/360049856394-How-to-Secure-Your-Network-with-Firewalla-Part-3-Protect
Since firewalla security intel is fairly dynamic and managed automatically by Firewalla, if you ever need an on/off switch in a list form that's part of your team/work/home policy, you can integrate it with the target list.
Can I create and manage Target List on the phone?
No, you can't, managing lists is a web-only function. Managing lists is a pretty complex process, any mistake is going to be much harder to debug.
I have a list that I think is good, can you integrate it?
Yes, please send the list/pointer to list, to help@firewalla.com
We can not integrate every list out there. The reason is, not all lists are equal, some are well maintained, and some need a lot of work.
Why is the target list limited to 100 elements?
The manual input lists are there for specific usages. For larger lists, it needs to be filtered and cleaned by the software and then imported. This means, a cut/paste of a large list may work in a day or two, without updating it, it just may not work a month out.
Comments
31 comments
So, we can also add our custom target list, nice feature.
Again, a new feature could be a sync with a github list like pi-hole does.
you add the github list like : https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt
then firewalla fetch on a daily basis and apply this to the custom target list.
best,
With the built-in list, I see OISD.nl which is great for me, as it's what I use in PiHole, but...it's only the basic list (~65,000) which targets just ads. The fill list there is ~1.1 million and blocks malware/tracking etc.
I'm sure you know all this. Is the reason because the big list is too big, or because the "additional" 1 million sites should be caught by firewalla without the list (since they are "bad" sites). I don't want to turn off my PiHole and use the "basic" list if it increases the likelihood of anything getting on computers on the network. The full list has been great, but if it's not needed, I'd love to cut back to the smaller one.
Will it be possible in future releases to be able to use wildcards in such a way that we can more specifically target subdomains? For example, instead of a target list entry "*.domain.com", which would match all subdomains, I'd like to use SQM with a target list entry that can match target1.domain.com and target2.domain.com. Having the ability to create a list entry of "target?.domain.com", where ? matches a single character, or even "target*.domain.com" would be great. Or, what would be even more powerful would be a way to match REGEX expressions to get even more precise, but I know that is a bigger ask and probably won't be as widely used.
If I want to block a domain and all subdomains, do I need to add two entires?
Eg:
google.com
*.google.com
The online meeting is just an example. It may have content for example from here https://support.zoom.us/hc/en-us/articles/201362683-Zoom-network-firewall-or-proxy-server-settings
@Robert apparently, matching rules for single domains vs domains in target lists work differently.
To match a domain + any-level-subdomain you would use:
Bare domain in a target list will only match the bare domain.
Updated my original comment.
+1
Agreed with Rich T. My PiHole monitored the full list too, plus others more specific to different categories (ie. crypto mining etc).
It would be good if FW had way more lists we could use (Full and Basic versions), or we have the ability to add our own list URL's.
Target lists do not seem to work if you apply it to "All Devices".
If Applied to a network then it works...
I mean the lists mentioned in the article (Online Meeting, Netflix Video)
This may seem like a stupid question to most of you, but I have seen some odd activities when using the Target List feature. I use the target list feature mostly to ALLOW certain traffic.I will provide an example list below.
*.amazon.com
*.a2z.com
*.amazonaws.com
However, it will still block the following:
compute-1.amazonaws.com
s3-w.us-east-1.amazonaws.com
api.amazon.com
arcus-uswest.amazon.com
My assumption was using the wildcard should allow anything associated with the listed domains. Would anyone be able to explain why my lists are working in this fashion?
Chris, can you explain or link to an explanation on the NordVPN in-bound exploit? By default, everything incoming is blocked. If you are using NordVPN, I can see how something might be possible, but if that's a concern I'd just stop using it.
Just like the "region" blocking and Pi-hole, unless you initiate a connection somewhere, a "response" or in-bound connection request from a random IP is blocked, right? So the outbound block essentially prevents the inbound.
@mozarella target list is supported on the blue/blue+/gold/purple
I am testing the latest beta which supports target lists editing/creation on the mobile app. Whilst it is now possible to add IPs/domains to a target list when creating a new rule, it doesn’t seem possible to “migrate” existing single IP/domain rules to a target list (new or existing). Would you be willing to consider adding also this functionality?
I think we need the ability to add larger lists. We also need to be able defang IP addresses and URLs. To be able to enter defanged entries that Firewalla enables for filtering behind the scenes. For example:
See: https://inquest.readthedocs.io/projects/iocextract/en/latest/
and my other comment at https://help.firewalla.com/hc/en-us/articles/1500003524781?page=1#comment_4966873945107
@Leonid Thanks for checking. This inconsistency may be why my allow lists didn't seem to be working.
@Shawn, target list should work on all devices, just created a ticket, so our developers can follow up with you.
Sure! here's what I've been able to come up with
https://github.com/minitacoslayer/BadPackets_IP/blob/main/ThisDoesThings.py
I like the PiHole idea, from my understanding, it is only DNS traffic that gets sent through this though (for a home network would probably be good enough). After reading some comments above, I agree having a feature to sync with a github list would be amazing!
*** Actually @Rich T, you are absolutely correct. Everything inbound is blocked - too much going on here. So the need to block in-bound per my list isn't really needed. Silly of me! Let me think more about that. It's not the use of by staff or internal people, it's evil doers accessing public websites and exposed services that is the risk.
NordVPN has been confirmed as being used by "hacker groups" to execute attacks. Many systems identify a users IP address and the geolocation of that address prior to permitting access. One test is if the distance between the geolocation of IP addresses between sequential access attempts is a realistic time/distance possibility.
For example, if I log in from Washington, DC and ten minutes later "I" am logging in from Moscow (Russia and not one of the 20 US "Moscows"). It is not possible to travel from Washington DC to Moscow in ten minutes. Such an access attempt can then be blocked.
To get around this, evil doers use VPNs (and NordVPN at a much higher rate than any other) to get around this. Use a NordVPN (or any VPN) that exits in Washington DC and then, in this example, this security protection isn't effective.
This is, in part, how Microsoft's vendor's contractor was compromised even when using MFA. The threat I am trying to address is related to MFA access to internal services.
Blocking in-bound VPN IP addresses is a prudent protection these days.
We, and my clients, are actively being scanned and attacked and every layer of protection needs to be put in place. No effort is too small.
The lists in this article do not show up on my fwg. I'm on the beta version.
So for target lists, I just need to enter the base domain, and all sub-domains will be automatically included. Is this also the case with domain-specific rules or do I still need to use wildcards there? Ideally, the syntax and scope should be consistent between features.
what's behind the "online-meetings" target list ? which websites ? there's a way to change this ?
Target lists are not available with firewalla red?
I’m seeing seven built in target lists (FWG) today. Only two listed in this article. Please update with short descriptions of each. Thanks!
Could someone please tell me: When I create a custom list, is it stored on Firewalla's server, or is it stored somewhere on the box itself as a text file?
These are custom lists added to Pi-Hole
I created a script to pull deduplicated IPs from a threat feed, I'm trying to automate the import of these IPs into my own target list, has anyone been able to find the actual folder location for these target lists?
Good question. I was never able to find how to do what you are doing.even if you identify how to do this I suspect it wouldn’t persist through a reboot.
Much easier to create your own custome list for PiHole. That’s what we do.
Can you please share your script? Would like to add to my list maintained on Github at https://raw.githubusercontent.com/C0ntr07/Pi-Hole/main/Iranian_Russian_Ukrainian_IPs.txt
I think I put the same request months ago and still waiting to see in action.
1. Ability to use wild characters in target list
2. Ability to assign single rule to multiple devices (grouping doesn't solve the requirement).
Looks like hard to code.....
This is a great feature. It would be great to have more than 200 entries because there are a lot of bad actors working on malicious attacks. For example my list of Russian, Ukrainian, Iranian, and NordVPN IOA and IOC URLs and IPs is about 5,300 entries today.
My workaround is to create a list that I add to Pi-Hole - but his protects against outbound only. This is my current list shared in an effort to keep the Firewalla community safe during the current geopolitical situation.
https://raw.githubusercontent.com/C0ntr07/Pi-Hole/main/Iranian_Russian_Ukrainian_IPs.txt
The NordVPN in-bound blocks are critical. We have found - in coordination with law enforcement - that there are attacks exiting from NordVPN’s network. The “group” is using NordVPN exit points to bypass “impossible travel” check protections. This has lead to success MFA compromise. There are just over 3,000 such IP addresses and want to block them on all of our, and our clients, Firewalla Golds. THIS is why the 200 entry limit needs to be removed unless it’s in place for performance reasons.
Will it work only on ip address or will work with site names also?
Please sign in to leave a comment.