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 » Users and Authentication » FAQ: Using authentication retention in terminal server...

FAQ: Using authentication retention in terminal server environments

Expand / Collapse
Show/Hide Article Tools


  • Question
    Can authentication retention be used in an environment with terminal servers?

  • Answer

    Definitions

    Authentication Rentention mechanisms allow a Vital Security Appliance to temporarily cache a user's name. This means that the user does not need to reauthenticate with each transaction, thereby improving performance.

    Terminal servers are powerful computers that host multiple interactive sessions from different users simultaneously. Many organizations use Windows-based terminal server solutions, such as Microsoft's Terminal Services and similar offerings from Citrix. With these solutions, several users can simultaneously run individual Windows sessions on the same server. The applications within these sessions run on the server itself, rather than on the user's own client PC.

    Answer Explanation

    It is possible to use the Cookie authentication retention mechanism in terminal server environments. This method sends a temporary identification cookie to the browser, which works well on a multi-session system because cookies are not shared between sessions from different users.

    The IP Caching authentication retention mechanism should not be used in terminal server environments. This method temporarily associates usernames with client IP addresses. In a terminal server environment, all transactions that originate from the terminal server will have the same client IP address. Since the terminal server can simultaneously host sessions from different users, a request from the IP address of the terminal server could have been made by any of the users on that server. Therfore, it is not possible to associate a specific transaction with a specific user by simply recognizing that the request came from the terminal server's IP.

  • Software Version
    8.4.3
    8.5.0
    9.0

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

    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