SonicWall has a rich set of application signatures for various applications that can also be categorized into multiple categories, such as P2P, social networking and risk levels. These signatures can restrict application use to only those applications that are approved by the organization.
SonicWall has an implicit deny rule which blocks all traffic. To allow a specific application like Teamviewer we would need to add a security rule to specifically allow it. Security rules consists of three sections, match criterion, action and action profile. This KB gives you the configuration steps for security rules
NOTE: When creating positive app match rule, make sure to allow all related application signatures so that application works without issues. It is recommended to create ANY ANY ANY allow rule from LAN to WAN zone and find out the required application signatures that are needed to run.
We would need to create and add the following to security policies to allow certain applications.
Before a connection can be made, the end machine would need to perform DNS resolution of the URLs that it needs to connect to for this application to work. Since we have an implicit deny rule, DNS traffic needs to be allowed as well.
To create the DNS-related Security Policy:



NOTE: This policy can also be created using the DNS protocol application signature, but service is used in this example.To create the Allow Application related Security Policy:
TIP: Some of the application signatures need DPI SSL. You can refer to the KB article: How to create a Decryption Policy on SonicOSX 7.0? for more details on the decryption rule configuration. Navigate to Objects | Match Objects | Applications and verify the signatures to confirm. The signatures have [Reqs DPI SSL CI] next to it that are dependent on DPI SSL Client inspection.

EXAMPLE: Let's walk through the steps to allow the Remote Access application Teamviewer.









TIP: For applications that also have websites like youtube.com, facebook.com etc might not load completely or intermittently as they could have several intermediate cdn servers, or image signatures loaded from various sites that are not part of the mentioned signatures.In those scenarios, it would be best to create an Any, Any, Any allow rule at the bottom of your security policies list and find out those missing signatures. You can use the packet monitor tool and check for the signatures that are needed along with the ones already allowed. You can refer to the KB article: How Can I Setup And Utilize The Packet Monitor Feature For Troubleshooting? for more details on Packet monitor tool.