In an effort to further simplify setup, ThreatSTOP has revised our installation script for ThreatSTOP IP Firewall on Juniper Filter devices to allow all three Juniper device types to be setup from one simple script. TS-JunOS 4.01 allows for rapid setup of Juniper SRX, MX, and EX devices without the creation of multiple security groups. It also adds the advantage of only requiring one setup script to cover all filter devices, instead of unique scripts for each device.
The resulting install will still provide full ThreatSTOP protection to your devices, rules will be put in place, prefix_lists will be automatically updated, and logs will optionally be uploaded to us in order to complete the holistic approach to security our service provides.
To install ThreatSTOP's IP Firewall on a Juniper device the following requirements need to be met:
- device must be a Juniper SRX, MX, or EX device
- an active internet connection to the device must be provided
This does not need to be a direct connection, but the device must be able to reach ThreatSTOP's DNS servers.
- a terminal that can SSH into the Juniper device will be needed
- root access to the device must be available
The scripts create a number of prefix lists and combine them to form a single filter called ThreatSTOP which can then be applied to the device interfaces. If you are already using firewall filters, please contact ThreatSTOP support about the best method to combine ThreatSTOP with your existing filters.
Before beginning the Installation process you will need to check that your device can communicate with the outside world. To do this:
- Open your SSH program.
- SSH into your Juniper device and login with root credentials.
Issue a ping to ftp.threatstop.com:
- If the ping comes back successful then the rest of the installation should go smoothly. Next we'll create a backup of your existing setup as a fallback point.
Creating a backup
To create a backup of your Juniper device's current configuration:
SSH into the device (if you are not currently SSH'ed in).
- Enter CLI mode by typing cli.
- Enter Configuration mode by typing configure.
- Save the current configuration with an explanatory name, e.g. prethreatstop, by entering save prethreatstop.
- Exit Configuration and CLI modes by entering exit twice.
We have discovered there can be a problem committing ThreatSTOP's configuration changes on smaller SRX devices, particularly in cluster mode, if the device has not been rebooted in a while. If the device is a three digit SRX (i.e., SRX-210 or, SRX-240) reboot the device before proceeding.
Setup can be performed semi-automatically through the command line via the following steps. A fully manual procedure is also available and detailed in the Manual Installation section.
- Setup your Juniper device in the ThreatSTOP portal. Detailed instructions can be located in Introduction, but a quick summary is:
- Log in to your ThreatSTOP account at https://www.threatstop.com
- Click on Devices
- Click on + Add Device
Enter a Nickname for the device, then select Juniper and the model of your device, under the Manufacturer and Model fields respectively. Set the IP type to static, and provide the external network IP address for your device.
If you aren't certain of the external IP address for your device, visiting https://www.threatstop.com/cgi-bin/validip.pl will provide the correct IP address.
- Select a Policy name, and click Next. This will add your device to your account.
- SSH into the Juniper device.
- Enter CLI mode using the command cli.
Copy and paste the following line into the SSH session.
This will automatically download the ts-juniper filters software from ThreatSTOP's FTP service, extract it, and run the setup with your chosen settings.
Press enter at all prompts to accept the default values, download the latest Threat Intelligence to your device and immediately add ThreatSTOP protection to your network.
If any values are omitted from the command string above, the device setup will require the missing data to be provided during the setup process.
- Jump to Applying the ThreatSTOP Configuration to complete device setup, and Cluster Setup for special notes about installing in Juniper cluster environments.
Applying the ThreatSTOP Configuration
Since every firewall configuration is different, ThreatSTOP does not automatically apply the filter it has created. Normally the filter is applied on the input side to all interfaces that receive traffic from the Internet or may send traffic to the Internet. If you have grouped interfaces in a range it is simpler to apply the filter to the entire range at once. In the example to the right there is one external interface (ge-0/0/0.0)
To apply the configuration:
- SSH into your device.
- Enter CLI mode by typing cli.
- Enter Configuration mode by typing configure.
- Set the system's syslog policy to apply the group named ThreatSTOP set system syslog apply-groups ThreatSTOP.
- Set the system's policy options to apply the group named ThreatSTOP set policy options apply-groups ThreatSTOP.
- Set the system's firewall policy to apply the group named ThreatSTOP set firewall apply-groups ThreatSTOP.
- commit the changes.
Applying the Filter to the Interface
The last step to enable ThreatSTOP IP Firewall is to enable the filter on your interface.
- Set the interfaces and unit to use the inet family and filter the input using the ThreatSTOP group. For example:
set interfaces ge-0/0/2 unit 0 family inet filter input ThreatSTOP
- commit the change.
This last step will enable the Juniper device to use Juniper's archive site feature to upload syslogs via FTP to ThreatSTOP.
In a cluster environment, the script needs to be installed on all the cluster nodes. The scripts will only run on the primary node. Due to how SRX clusters work, the secondary nodes may not be able to access the internet, and it will be easier to copy the script from the primary node.
To copy the scripts to the secondary nodes, access the node with SSH and run:
Replace "IP_ADDRESS_OF_PRIMARY_NODE" with the IP address of the primary node.
After the script is copied, extract it and run the 'tsinstall.sh' script:
When the ts-setup script is run, it will automatically detect that it is not the primary node and will only create the cronjob that will run the ts-update script. This script will also detect that it is not the primary node and will not run. It will only run if the cluster failed over and the node becomes primary.
Downloading and installing ThreatSTOP IP Firewall can be simplified by cutting and pasting the following commands. You will want to be SSH'ed into the device, and logged in with root permissions to successfully run these commands:
This will automatically download the JunOS archive, extract it to ts-junos, then begin the device configuration.
ThreatSTOP IP Firewall Configuration
The example to the right demonstrates device setup. And includes settings that you will need to copy and paste into your own setup.
Specifically the following data will need to be answered:
- Block policy domain: <block list name>.<ThreatSTOP account ID>.threatstop.local.threatstop.local
This is the name of the policy selected in the ThreatSTOP web interface, the block designator, and the account ID for your ThreatSTOP account.
- Allow policy domain: <allow list name>.<ThreatSTOP account ID>.threatstop.local.threatstop.local
This is the name of the policy selected in the ThreatSTOP web interface, the allow designator, and the account ID for your ThreatSTOP account.
Enter the Maximum policy size: This should be set to the largest policy size supported your device. For most devices Juniper suggests that this size is 80,000 entries for SRX and MX devices. EX devices may need smaller policy sizes due to the available disk space on the device and the script defaults to this smaller size to avoid the issue in rapid setups.
Devices that do have smaller policy sizes will still download the full Threat Intelligence list, and then parse out the first IPs up to the Max Policy Size limit. Both files can be located in /ts-junos/lists
Enter the IP Address with which logs should be associated: This is the external IP address for your device as established by https://www.threatstop.com/cgi-bin/validip.pl and incorporated into the script. This is the address we recommend be applied to the device, however it may be changed if the external address is known to be different from the one supplied.
To run through a full setup of ts-setup:
- Login to the Juniper device.
- Enter cli to switch to CLI mode.
Download and run the installation script:
This will download, extract, and start the ts-setup script.
- Tap ENTER to continue the process after reading the preamble.
- At the Block policy domain (hit return for basic.threatstop.local) prompt enter:
<block list name>.<ThreatSTOP account ID>.threatstop.local.threatstop.local.
- At the Allow policy domain (hit return for dns.threatstop.local) prompt enter:
<allow list name>.<ThreatSTOP account ID>.threatstop.local.threatstop.local.
- Press ENTER to accept the default policy size, or adjust as needed for your configuration.
Press ENTER to accept the provided IP address, or enter another external IP address.
The IP address provided is the same as the one provided by https://www.threatstop.com/cgi-bin/validip.pl and is the address we recommend be applied to the device.
To finish setup, press ENTER at the Continue with ThreatSTOP group update and cron installation (yes/no)? (hit return for yes): prompt.
Setup will begin.
All ThreatSTOP configurations are setup under the ThreatSTOP Group. This group can be viewed with the following command:
The Firewall mode will always be set to filter.
The setup script also creates a cron entry for updates.
Once setup is complete we can move onto Applying the Filter.
Manually Updating the Threat Intelligence Lists
For diagnostic purposes, it may become necessary to manually update the lists used by your device. The following steps demonstrating this assume that your device has already undergone the setup process.
- Enter /bin/sh ts-update.
- Press the ENTER key when prompted to Load the Latest ThreatSTOP address lists now (yes/no)?
This will load the latest lists into the device.
A guide to troubleshooting some common problems. If you are confused or if these steps do not help, then please contact ThreatSTOP support.
ThreatSTOP rules do not appear to download anything
The most likely reason is that you have not correctly entered the firewall's IP address in the ThreatSTOP device definition page. You can verify whether the address the firewall uses is in our database by visiting the this URL - http://www.threatstop.com/cgi-bin/validip.pl - using the fetch command from the CLI:
Alternatively you can visit it in a browser that is NATed through the firewall.
You should see a simple result stating the device's IP address and whether it is in the database or not. Database updates are not instantaneous but take place every 15 minutes; so, if you have recently added/modified the firewall IP details, you may wish to wait about half an hour before checking this. If there is no response at all then verify by using the ping command that the firewall can reach threatstop.com and, if not, that it can reach other places such as google.com. If you have no connectivity to ThreatSTOP but do have connectivity elsewhere please contact ThreatSTOP support for further information about the status of the ThreatSTOP infrastructure.
If the address is valid but there are still problems you should manually run the blocklist retrieval procedure in debug mode and then examine the output. To download the blocklists do the following at the command prompt (SSH or console):
The output should report what the script is doing. You may find it useful to 'tee' the output to a file so that it can be emailed to ThreatSTOP support.
- Not all traffic is being blocked / everything is being blocked
The most likely reason is that you have not correctly applied the ThreatSTOP filter (see "Applying the Filter" above). If you need help with verifying the filter configuration please contact ThreatSTOP support.
- ThreatSTOP blocks access to places it shouldn't
Although ThreatSTOP tries very hard to ensure that we have zero false positives in our standard lists, we do occasionally miss something. If you are a community user or are using ThreatSTOP in standard mode on your firewall then please report the offending domain and IP address to ThreatSTOP support. Please check in the log file (/var/log/ <Device IP>.log) that the IP address is indeed being blocked by the ThreatSTOP rules before contacting us.
You can also add the IP address to a custom allow list. Once you have created the allow list and added it to this device in the "Edit device" page. If you did not use an allow list when you created the device, then the first time one is added you should run the following command on the SRX command prompt to enable it on the device:
Our Advanced lists are not so well checked for false positives as we believe that it is up to each expert Advanced user to make his or her decision about the suitability of certain feeds and some feeds - e.g. the "Parasites" feed - are known to block ip addresses that are not considered harmful by everyone. Do consider a custom allow list (see above) as a first step and do please contact ThreatSTOP support to verify that the feeds you have chosen are appropriate to your situation.
- Other firewall rules do not appear to work
The most common reason for this is the same as 2) above, namely that the ThreatSTOP filter has been incorrectly set up. If you had additional filters then you may have replaced them with the ThreatSTOP filter if you apply it using the "... filter input ThreatSTOP" command. As noted above, if you already have one of more filter on the interface you should use the 'input-list' alternative and put the ThreatSTOP filter before your other filters.
- No Logs Uploaded
In many cases logging issues are related to issue 1) above. If running the "validip" test described above is successful then you should verify that "log enable" is set appropriately in the current configuration (all ThreatSTOP firewall drop policies should include a log command in them).
You should also confirm that the file /var/log/<Device IP>.log exists. If it does not please contact ThreatSTOP support. Finally check that the syslog handling part of the configuration is set to upload the <Device IP>.log file to
The logs are transferred to ThreatSTOP using FTP.
To allow the device to FTP the logs to us on SRX devices, the FTP Application Layer Gateway (ALG) may or may not need to be enabled. By default, the FTP ALG is enabled. To see the status of the FTP ALG, run:
If it is not listed, then it is disabled. If it is listed, you can disable it by running:
The easiest way to test if a log can successfully reach us is to attempt to access ftp.threatstop.com from the device while it is in an active setup. If the FTP request succeeds then the FTP ALG setting is fine, otherwise place in its opposite state and try again.
Removing ThreatSTOP can take a few pathways depending on your needs:
Non-destructively removing ThreatSTOP
ThreatSTOP can be removed in a non-destructive manner by simply removing the ThreatSTOP Group, and uninstalling the files. To do this:
- SSH into the device.
- Enter CLI mode by entering cli.
- Enter Configuration mode by entering configure.
- Delete the ThreatSTOP filter from the interface.
delete interfaces ge-0/0/2 unit 0 family inet filter input ThreatSTOP
- Delete the ThreatSTOP syslog entry.
delete system syslog apply-groups ThreatSTOP
- Delete the association between the policy and the ThreatSTOP group.
delete policy-options apply-groups ThreatSTOP
- Delete the firewall configuration's reference to the ThreatSTOP group.
delete firewall apply-groups ThreatSTOP
- commit the changes.
This will remove ThreatSTOP from the network device. You may then run /bin/sh ts-uninstall from the CLI mode. This will remove the ThreatSTOP group and everything underneath.
Destructively Removing ThreatSTOP:
In addition to the steps taken in the Non-destructive removal process, you can also manually delete the directory structure after ts-uninstall is complete.
Rolling Back a ThreatSTOP Installation
If you have run our install script, applied the policy changes and wish to return to the pre-ThreatSTOP configuration then you should perform the following actions.
To restore the original configuration you should enter the commands to the right in the console.
This will also undo any other changes made to the configuration since ThreatSTOP was installed.
To uninstall the ThreatSTOP scripts enter:
Command Line Switches
The following command line switches are available to help speed up the setup process:
-a <Allow list> the allow list name including the Account ID
-b <Block list> the block list name including the Account ID
-l <Log association IP> this is the external IP associated with the device. This will usually match the one provided by https://www.threatstop.com/cgi-bin/validip.pl
-f filter This will always need to be set to filter
-m <Max policy size> This should be set to match the Maximum Policy Size supported by your device
-h provides definitions of this list in the terminal
ThreatSTOP IP Firewall is distributed via FTP as a pre-packaged tar.gz file. The files can be downloaded from here (ftp://ftp.threatstop.com/pub/ts-juniper.tar.gz), or you can use the command in Installation to automate the download and install process. After extraction the files will be located in a subfolder of the current working folder ~/ts-junos from a fresh login), the following files and directories will be installed:
Two additional files will be created after setup has been completed successfully:
Additionally, the two sub-directories (audit, and lists) contain information that can be used for Troubleshooting and will not normally need to be accessed.
- /audit contains log files for support. The logs files contained are both the current log file, as well as the immediately previous log file.
- /lists By default, contains the full allow and prefix_lists created by the policy used in the ThreatSTOP web interface. If the Max Policy Size is smaller than the size of the full list, an additional file will be generated that contains the list uploaded to the device.
There is no content with the specified labels