LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. 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
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 build resilience
Awards and Accolades
The most recognized cybersecurity leader
LevelBlue SpiderLabs
Elite global threat experts and intelligence
PGA of America Partnership
Cybersecurity at the championship level
Secure What's Next
Future-proof your organization
LevelBlue Security Operations Platforms
Unprecedented security visibility and control
Security Colony
Cybersecurity threat protection resources
Partners
Microsoft
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: Adding wildcard URLs to a Category and differences

INFO: Adding wildcard URLs to a Category and differences

Expand / Collapse
Show/Hide Article Tools


This article applies to:

  • R3000

Question:

Adding wildcard URLs to a Category and differences

Reply

If I add a wildcard URL (*.go.com for example) to a custom category, and then set the category to 'Allow', would I still be able to visit a website like www.disney.go.com?

 

It depends on the URL that is being visited.  Simply having a wildcard added in the ‘Allow’ library category does not guarantee an automatic exclusion of all URLs or sub-domains under the wildcard.  If a URL in question is “specifically” categorized in a different category, which is marked as ‘Block’ in the given profile, then wild card exclusion will not work for the particular URL.

As an example, assume following URLs are listed in the R3000 library as shown below:

*.go.com -- Custom_Category
www.disney.go.com -- Entertainment
www.xyz.go.com -- Not Specifically Categorized.

Your filtering rule states that the Custom_Category is marked as 'Allow' while 'Entertainment' is marked as ‘Block’. Block/Allow results of visiting each of the above URL will be as in the following:

www.go.com -- Allowed due to custom category being marked as 'Allow'.
www.disney.go.com -- Blocked due to the URL being "specifically” categorized in the Entertainment category.
www.xyz.go.com -- Allowed due to the URL not being specifically categorized in any category; hence, the only possible match found in the library is *.go.com, which is in the Custom_Category that is marked as 'Allow'.

So, based on the R3000 filtering logic, any URL that is specifically categorized in a certain category will have precedence over a [rather] less specific URL [wildcard].  In other words, *.disney.go.com is more “specific” than *.go.com; therefore, the specifically a URL is listed in the library, the higher the precedence is when it comes to actually blocking or allowing.
This article was previously published as:
8e6 KB 289097

To contact LevelBlue about this article or to request support:

Rate this Article:
     
Tags:

Add Your Comments


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


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