SonicWall NSv (Firewall/Security/VPN/Router) - PAYG

My main use case for SonicWall NSv  is cloud space, specifically for Azure , AWS , and GCP deployments.

I use SonicWall NSv  to secure cloud infrastructure instead of relying on Azure  barebone security or AWS  security. This allows me to get more granular control with my security settings.

I also use it to protect our private data center. We have customers that utilize it in a similar manner to Azure infrastructure, but within our own environment.

SonicWall NSv offers the option for Classic or Policy Mode, which allows me to choose between the two. If I need more granular control, I would prefer to use Policy Mode. If it is a simple configuration with one network that does not require much complexity, then Classic Mode is perfect.

When I use Policy Mode for more granular configurations, I can address situations where that flexibility makes a difference, such as wanting to have one network or one zone over another. I am not limited to the global security service configuration and can have multiple different security policies.

SonicWall NSv has positively impacted my organization. One specific outcome I have noticed is the low cost of licensing and that it is a trusted security appliance.

The low cost and trusted security have led to measurable benefits such as cost savings, which allow us to invest in other technologies.

SonicWall NSv can be improved, particularly in the SAML implementation, which was introduced in 7.2 firmware. I have 7.3, and I am waiting on that first jumbo hotfix from SonicWall. There is a need to continue improving the SAML implementation.

I have been using SonicWall NSv for about seven years.

SonicWall NSv is stable.

With NSM, the Network Security Manager, SonicWall NSv is quite scalable. You can operate multiple different NSvs under one management plane.

Customer support from SonicWall could see some improvement. With the number of items that SonicWall has going on at the moment, the wait line can be quite intrusive.

Neutral

Before choosing SonicWall NSv, I evaluated other options such as FortiGate virtual servers. For our customers, it always comes down to cost, where their budget is, and whether they need to go with FortiGate or SonicWall. Along with the cost, it also factors in how granular they need to utilize it. If they know they need to have BGP, then I might forgo SonicWall.

I have seen a return on investment. The relevant metric includes the time saved in deployment, especially if you go with Classic Mode over Policy Mode. Not much has changed since the release of Gen  7.

My experience with pricing, setup cost, and licensing is that licensing is fairly simple. I work with account managers at SonicWall, submit quotes with my distribution group, and the process is seamless.

I did not purchase SonicWall NSv through the AWS Marketplace . I bring my own license.

Integration is something worth discussing.

SonicWall NSv integrates well with my existing systems. I have a built-in syslog system called ForVideo, and I can ingest all logs from SonicWall NSv appliance that I may not be able to get from a FortiGate.

My advice to others looking into using SonicWall NSv is that if deploying SonicWall NSv, I would really consider using Policy Mode over Classic Mode. I know it is quite a change going to that mode, but if you have to change to Policy Mode in the future, then you are looking at redeploying SonicWall NSv. If you deploy it from the start, you have that scalability to continue to grow.

I would rate this product a seven out of ten.