Example: detecting the use of forbidden software
Engine-specific examples of using custom Situations to detect traffic patterns associated with specific software.
Engine
Company A has a Engine that inspects all outgoing web traffic against the Inspection Policy. The use of instant messaging clients across the Internet is forbidden in the company. The Inspection Policy is set to detect and log Situations with the Instant Messaging Tag.
The company’s administrators have found out that some internal users have started chatting using a new little-known instant messaging client that does not have a default Situation yet. The communications seem to be standard HTTP directly from client to client. The administrators find one distinctive characteristic in the software: when started, the software in question always connects to a particular address to check for updates using HTTP.
- Create a custom Situation element with the name “Software X”.
- Add the HTTP Request URI Context to the Situation and type in a regular expression that contains the address they want the Situation to find using the SMCaaS Application regular expression syntax.
- Add the default system Tag Instant Messaging to the Situation.
- Refresh the Engine’s policy.
- Open the Logs view and filter the view using the “Software X” Situation as the filtering criteria.
- See which computers use the forbidden software and remove the software from the computers shown in the logs.