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 » Secure Web Gateway » Security Policies » FAQ: Why are websites blocked without block page or logs by Vital...

FAQ: Why are websites blocked without block page or logs by Vital Security NG?

Expand / Collapse
Show/Hide Article Tools


  • Question
    Why are web sites or web servers that do not respond from the requested TCP port (e.g. port 80 - HTTP) blocked and not logged by the Finjan Vital Security NG proxy?

  • Answer
    By default, the Vital Security NG appliance blocks connections to most "privileged" or "well known" ports (ports lower than 1024). Of the privileged ports, Vital Security only allows connections to 21 (FTP), 80 (HTTP), and 443 (HTTPS) by default.

    Vital Security does not log anything when transactions are blocked due to the fact that they occurred on a restricted port. Simple URL whitelisting works on a URL basis (Layer 7) and can not resolve the problem in principle.

    To allow additional privileged ports, administrators can edit the allowed ranges:
    1. From the management console, navigate to Settings > Devices > Scanning Server >HTTP: Allowed Server Ports in URI.



    2. Change the set of allowed port ranges according to your needs, and then Apply and Commit Changes. You can check which port is responding by performing a packet trace on the proxy.
  • VSOS
       8.4.0
       8.4.3
       8.5.0

    • This article applies to:
    NG 1000
    NG 5000
    NG 8000
    This article was previously published as:
    Finjan KB 1152

    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.078. 8 queries. Compression Disabled.
    Powered by InstantKB.NET