SteelHeadā„¢ Deployment Guide - Protocols : Signed SMB and Encrypted MAPI Optimization : Windows Security Concepts
Windows Security Concepts
The Windows security framework is based on a formal structure known as a domain. Inside the domain is a logical group of host resources (primarily clients and servers, but also printers and other peripherals, and so on) that share a central directory database. The database resides on one or more servers known as domain controllers and contains user accounts and security information for all the resources in the domain. Other domains can coexist alongside and are joined together through a Trust Relationship to allow resources to securely communicate between each other even though they are in different domains with their own domain controllers.
When users and clients are accessing server resources (like file servers and Exchange servers), their credentials are validated against the database on the domain controller. This ensures that the client and the user have the correct security privileges to be able to access resources that provide signed SMB traffic or encrypted MAPI traffic.
There are several techniques and protocols used to validate the credentials of the user and client. These vary according to the Windows operating system version and application configuration (for example, Microsoft Outlook and Microsoft Exchange) on both the client and server. Example protocols include Kerberos, NTLMv1, and NTLMv2. The earliest RiOS version required to perform optimization in a Windows security environment is based on the protocol used, because RiOS has added more capabilities in newer versions.