Get access to immediate incident response assistance.
Eliminate active threats with 24/7 threat detection, investigation, and response.
Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.
Advance your cybersecurity program and get expert guidance where you need it most.
Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.
Prevent unauthorized access and exceed compliance requirements.
Stop email threats others miss and secure your organization against the #1 ransomware attack vector.
Prepare for the inevitable with 24/7 global breach response in-region and available on-site.
Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.
Does the filter block IM/P2P traffic if a user connects on a non-standard port?
The filter blocks IM and P2P traffic through pattern blocking mechanisms where it decides whether to block or pass based on the 8e6 proprietary pattern definition file regardless of the port that is being used to connect. Therefore, if a pattern definition exists for a certain IM or P2P client, the filter pattern detection module would still be able to detect and block regardless of the port that is being used to communicate. However, for this to work effectively, it is essential to block relative categories in the profile rule such as Instant Messaging and Peer-2-Peer/File Sharing respectively in addition to turning on service blocking under System tab in the filter GUI.
To contact Trustwave about this article or to request support: