Server DPI-SSL inspects incoming encrypted traffic before it reaches hosted apps. Moreover, this is a pretty important part of your SonicWall training. From public-facing websites to APIs, and more, many angles of your network are bound to face probing threats.
There’s more to know here than just flipping a switch and reaping the benefits. For this article, you’re gaining a better understanding of how to set up server DPI-SSL inspection with your SonicWall hardware.
Key Takeaways:
- Server DPI-SSL inspects inbound encrypted traffic targeting hosted apps
- Import the server’s SSL certificate and private key before configuring inspection
- Use a server address object to identify the device protected by the inspection policy
- Apply inclusion and exclusion rules to manage inspection exceptions for users and network segments
- Verify inspection activity through firewall logs and diagnostics after enabling the policy
What’s the Difference Between Server SSL vs Client SSL?
For starters, it helps to understand that client DPI-SSL inspects connections initiated by internal users. With server DPI-SSL, this examines connections initiated by external clients. Overall, the two inspection methods address different traffic directions. In addition to that, they also require distinct security policies.
The short version is that server DPI-SSL is great for companies hosting public-facing apps and services. Whereas on the client side, it generally uses a trusted certificate to re-sign intercepted connections. Nevertheless, you can improve your SonicWall firewall training by knowing how to set up server DPI-SSL, and it only takes a few steps.
Step 1: Download Your SSL Certificate From Your DNS Provider
If you’re new to this process, it can seem like a lot, but I promise it’s a whole lot easier than you think. First, you want to focus on obtaining the SSL certificate and corresponding private key from your DNS provider.
Here are the other important technical steps that follow:
- Install the certificate on the local machine before importing it into SonicWall
- During installation, select the Trusted Root certificate store
- Prepare the certificate in P12 format
On another note, these steps are relevant whether you’re working with the SonicWall NGFW TZ-Series or even the NSa’s. To help you avoid any confusion, step two will focus on the play-by-play of importing the certificate into SonicWall.
Step 2: Import the Certificate Into SonicWall
By this point, you should have the SonicWall management interface open. You’ll start at Device, then move to Certificates, and then hit Import. I always have to stress the importance of creating a recognizable certificate name here.
You want this to be easily identifiable when it comes to configuration. Moving on, select P12 as the certificate format, and enter the password associated with the certificate once you’re prompted. Moreover, don’t forget to confirm the certificate is actually available in SonicWall before moving on to the next step.
Step 3: Create a Server Address Object
For those who are still on track with me, the next step is to navigate to Object and then move to Addresses. Once again, this is all found in SonicWall’s management interface. What you’re doing here is defining the server that will be protected by DPI-SSL.
First, you’ll want to select the option to create a new address, and then assign it to the appropriate network zone. After you enter the server’s IP address in the configuration, make sure to save it before moving on.
These types of solutions may not be uncommon in today’s cybersecurity landscape, but there’s a sense of efficiency behind everything in SonicWall Gen 8 hardware. On paper, this might seem like a lot to go through, but you’ll realize that hands-on, it’s a breeze. Now that you have created a server address object, it’s time to move on to configuring the SSL server entry.
Step 4: Configure the SSL Server Entry
This step comes with three parts right from the jump, as you’ll need to navigate from Policy to DPI-SSL, and then Server SSL. Here, you’ll find the firewall’s server-side SSL settings.
Now work from the bottom of the page upward, and locate the SSL Servers section and select Add to create a new server entry. Then, you will choose the address object you created in step 3 to identify the specific server.
On top of that, you’ll want to select the SSL certificate that was imported back in step 2. This allows SonicWall to associate the certificate with the designated server. Lastly, don’t forget to add the completed entry and verify that the server address object and certificate are associated correctly.
Step 5: Set Inclusion and Exclusion Rules
I promise you’re getting to the end of it here, as step 5 focuses on the inclusion and exclusion settings. This can be found on the Server SSL configuration page. You’ll be using address objects to establish exceptions for specific network segments.
Moreover, configuring user-based exceptions is part of this too, especially when certain accounts require different treatment under the inspection policy. I’d also tell any business owner to consider excluding the entire LAN subnet if your network requirements call for internal traffic to bypass inspection.
It’s a small detail that can make a big impact, and it also doesn’t hurt to exclude SonicWall admins when it makes sense. This can help prevent inspection from interfering with certificate maintenance or admin access to the server.
“So that way whenever they're doing certificate maintenance on the server itself, they don't accidentally lock themselves out.”
~ William Beeman, Network Engineer
Step 6: Enable Inspection and Verify
Now we’re on the final step to this, which handles actually enabling inspection. Again, these steps come with the technical jargon, but the list below highlights just how simple it is to get it done.
Follow these points to enable inspection successfully:
- Save the server DPI-SSL configuratio to apply the settings and activate the inspection policy
- Access the hosted app to confirm that the service is still available after the configuration change
- Review packet inspection firewall status, logs, or diagnostic information to verify that the intended traffic is being decrypted and inspected
- Confirm that the correct server address object and SSL certificate are associated with the SSL server entry
Another consideration I like to slide into this conversation is pairing server DPI-SSL with client DPI-SSL. This can be a great combo for addressing encrypted traffic in both directions, each having their appropriate configuration.
Even though all of these steps are simple on a technical level, it’s understandable if it feels a bit overwhelming. Regardless of whether you’re brand new to the topic or a cybersecurity veteran, the table below can help you streamline the steps laid out in this article. Consider this information as the bulk of your navigation throughout this process.
| Step | SonicWall Interface Navigation |
|---|---|
| Import Certificate | Device → Certificates → Import |
| Create Address Object | Object → Addresses → New |
| Add SSL Server Entry | Policy → DPI-SSL → Server SSL |
| Set Exclusion Rules | Policy → DPI-SSL → Inclusion/Exclusion |
I highly suggest using it as a callback for when you’re ready to dig through this side of your SonicWall training. We also have a great video on this topic that you can find above.
The Final Word
Server DPI-SSL is only one important angle to SonicWall training, but it’s crucial to improving network security through inspection. Of course, how well it works definitely has a lot to do with the setup process.
Remember to correctly associate the server, SSL certificate, and inspection policy. I can’t stress enough that verifying and reviewing should be a priority as well. On the other hand, our team at Firewalls.com is always here if you’d rather we take the reins. All it takes is a single conversation with us to make sure you aren’t left with any questions.
Frequently Asked Questions
What is Server DPI-SSL on a SonicWall?
Server DPI-SSL decrypts and inspects incoming encrypted traffic to identify potential threats before they reach a hosted server.
How is Server SSL Different From Client SSL Inspection?
Server SSL inspects inbound connections using the hosted server’s certificate, while client SSL inspects outbound connections and typically uses a trusted CA certificate to re-sign intercepted traffic.
Do I Need a Certificate From My DNS Provider to Set This Up?
A valid certificate and private key are recommended for production, while a locally signed certificate can be used for lab testing.
Can I Exclude Certain Users From Server SSL Inspection?
Yes, inclusion and exclusion rules let you exempt specific users or addresses, including admins performing specific maintenance.
Which SonicWall Models Support Server DPI-SSL?
Server DPI-SSL availability depends on the model and firmware, so I’d advise you to check SonicWall documentation for compatibility with their Gen 8 hardware.


