Hardening and Protecting Servers and Applications for Lync Server 2010
Topic Last Modified: 2012-10-15
You should harden and protect your operating system and applications according to best practices for that specific component. This section describes how to harden application servers and use Group Policy to implement security lockdowns.
|You can also harden and protect the databases used for you Microsoft Lync Server 2010 deployment. For details, see Hardening and Protecting the Databases of Lync Server 2010.|
For applications servers, the operating system and the application should be hardened. For example, a Windows Server 2008 computer dedicated to running Microsoft Internet Security and Acceleration (ISA) Server 2006 should be hardened from the operating system and from the application perspective. Minimizing the number of services running and provided by the server should be a primary goal.
Virtual server snapshots contain copies of the server’s data disks and also contain dumps of in-memory data, both of which can contain sensitive cryptographic data that might lead to attacks. For production servers implemented using virtualization, you should disable all server snapshots or manage them in a very controlled manner. For details about securing Hyper-V virtual servers, see the Hyper-V Security Guide at: http://go.microsoft.com/fwlink/p/?LinkId=214176.
In Windows Server 2008 and Windows Server 2008 R2, Group Policy provides directory-based desktop configuration management. You can use Group Policy to implement security lockdowns by defining Computer and User settings within a Group Policy object (GPO) for the following:
Remote installation services
To provide a user interface for the administrator to configure these settings, administrative templates are shipped with operating system releases, service pack releases, and some applications, including Lync Server 2010.
The Communicator.adm file is an administrative template that ships with Lync Server 2010, is installed to the %windir%\inf\ directory, and provides an interface to the Group Policy settings. Each setting in Communicator.adm corresponds to a setting in the registry that affects application behavior.
The settings can be accessed from GPedit.dll, which is available from the Active Directory Users and Computers console and the Group Policy Management Console (GPMC).
Group Policy contains security settings for a GPO under Computer Configuration/Windows Settings/Security Settings when accessed from GPedit.dll. You can import security templates to configure security settings for the GPO. The Windows Server 2008 Security Guide at http://go.microsoft.com/fwlink/p/?LinkId=145186 and the Windows Server 2008 R2 Security Compliance Management Toolkit at http://go.microsoft.com/fwlink/p/?LinkId=211882 contain a number of sample templates that you can modify to meet your needs.
Harden all server operating systems and applications.
Protect server snapshots and enhance the security of all virtual servers.
Use Group Policy to implement security lockdowns.