Table of Contents
Click an item to jump directly to that question.
- What's The Difference Between Application Control Lite And Application Control?
- Is There A List Of All Applications That Can Be Scanned For?
- Can Sessions Ever Reach The Fully Classified State With Confidence Less Than 100%?
- Should I Use Block Or Tarpit?
- I'm Already Using The Firewall - Isn't Application Control Redundant?
- How Does Application Control Work?
Application Control Lite runs simple regular expression signatures against the datastream. If a signature/regex matches the action is taken for that particular signature (log or block). Please do not go through the list of signatures and block what you "don't need"; these signatures are not exact matches and can have false positives.
Application Control classifies the attributes and metadata of packets to determine their type and operates on them once classified. False positives are very rare.
An exhaustive list of applications and their description is available here.
Short lived sessions often die before they become fully classified, so it is not uncommon to see session in the event log with confidence less than 100%. Rarely, the classification engine might have no idea what a session is and considered it fully classified as nothing more will be learned. In this case it will consider the session fully classified but confidence will be less than 100%.
The block action resets the connection immediately - this is quick, straight-forward and the application will immediately know it has been disconnected. Unfortunately, many applications are written to be very tolerant towards disconnects and even try alternate connection methods if it detects it's getting blocked. In these cases tarpit can be a better option as it will leave the connection open but silently discard the data, making it much harder for the application to know it has been disconnected. The downside of this method is that it may make any false positives harder to troubleshoot.
The Firewall application works to block traffic by IP addresses and/or ports. For well-behaved applications (such as legitimate web and email servers) the port can be used to identify the protocol. Less than legitimate applications may use different ports, or malicious users may deliberately use unwanted services on obscure ports. Application Control scans all traffic, looking for a match even if traffic was not transported across the expected port for that protocol.
Application Control feeds each chunk of data to a classification engine as it passes through NG Firewall. The classification engine continues to analyze the traffic flow and keeps properties of the session, such as the Application property. Each time the classification of the Application property is updated, the Applications settings are checked to see if that application is allowed. If the application is set is blocked the session is reset, blocked or tarpit depending on your settings. If not, the process continues until the session reaches a fully classified state where the classification engine believes no more classification of the session is possible. At this point the Rules are evaluated and the session is ultimately blocked or passed based on the rules you've configured.