LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  Learn More

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
View All Services
Solutions
BY INDUSTRY
BY REGULATION
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft Security
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
We reduce cyber risk and fortify organizations
Awards and Accolades
Recognition by analysts and media outlets
LevelBlue SpiderLabs
Global researchers, ethical hackers, and responders
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Access to cybersecurity threat protection resources
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Register
Login
Resources
BLOGS
UPCOMING
MEDIA & ASSETS
NOTICES
HELP
Loading...
Loading...

LevelBlue Knowledge Base

Home » Knowledgebase » Legacy Products » Web Filter (R3000) » INFO: Why is Pattern showing up in the probes and reports?

INFO: Why is Pattern showing up in the probes and reports?

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • R3000/WF/WFR

Question:

Why is Pattern showing up in the probes and reports?

Reply

Why is Pattern showing up in the probes and reports?
By design, the pattern-based filtering is identifying traffic on the signature of the request rather than identifying a known-destination. Because this is extremely processing intensive, we simply identify the traffic when it matches a particular signature and log the destination IP address of that traffic.

What you may see in probes
PROXY,1,7,,pattern://72.165.141.81/, pattern://72.165.141.81/   where 1= blocked and 7=block method, pattern in this case
or
PATTERN//157.233.101.99/  These pattern ip typically do not go to a website, since it is a signature pattern not a domain.  
The filter Software version 4.x or higher has this new pattern filtering Whitelist: the new Pattern Detection Whitelist window (Library > Pattern Detection Whitelist) lets you create a list of IP addresses that will always bypass pattern detection filtering. If the above ip is a server, it must be excluded from the range to detect section.
Another option is to exclude a source ip address in the Global Group > Range To Detect section. If you have multiple range to detect settings, select the source ip that needs access to this site then add the excluded ip address in step 4 of the wizard.

Using an internal Proxy
When looking at traffic that is going through a proxy server, the destination IP address is in fact the proxy server, so by design, the filter will log that instead of the real site outside the network. We do not maintain a state table of which connection (from client to proxy server) is going to which destination (from proxy server to internet destination), due to the processing overhead associated with the signature matching as it is.


This article was previously published as:
8e6 KB 300017

To contact LevelBlue about this article or to request support:

Rate this Article:
     

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster.


Execution: 0.031. 8 queries. Compression Disabled.
Powered by InstantKB.NET