Planifier la sécurité pour un environnement de collaboration sécurisé externe (Office SharePoint Server)

Mise à jour : 2009-04-23

In this article:

• Protect back-end servers

• Secure client-server communication

• Secure the Central Administration site

• Secure Shared Services Provider administration sites

• Secure design checklist

• Plan security hardening for server roles

• Plan secure configurations for Office SharePoint Server features

Security guidance for an external secure environment is targeted to hosting content in an extranet for the purpose of collaborating on content with contributors who do not have general access to your corporate network. This environment allows external partners to participate in a workflow or to collaborate on content together with employees of your organization.

There are several unique recommendations for an external secure collaboration environment. Some of these recommendations might not be practical for all solutions.

Protect back-end servers

External secure collaboration requires Internet-facing servers. You can limit the exposure to traffic from the Internet by protecting back-end servers:

• Protecting database servers   At a minimum, place a firewall between front-end Web servers and servers that host databases. Some environments dictate that database servers be hosted in an internal network instead of directly in an extranet environment.

• Protect application servers   At a minimum, protect application servers by requiring Internet Protocol security (IPsec) to secure communication between server farm computers. You can additionally place application servers behind the firewall used to protect database servers. Or, you can introduce an additional firewall between front-end Web servers and application servers.

• Protect the index role   The index component communicates through a front-end Web server to crawl content in sites. To protect this communication channel, consider configuring a dedicated front-end Web server for use by one or more index servers. This isolates crawling communication to a front-end Web server that is not accessible to users. Additionally, configure Internet Information Services (IIS) to restrict SiteData.asmx (the crawler SOAP service) to allow only the index server (or other crawlers) to access it. Providing a front-end Web server dedicated to content crawling also improves performance by reducing the load on the main front-end Web servers, thereby improving the user experience.

Secure client-server communication

Secure collaboration in an extranet environment relies on secure communication between client computers and the server farm environment. Where appropriate, use Secure Sockets Layer (SSL) to secure communication between client computers and servers. To increase security, consider the following:

• Require certificates on client computers. SSL can be implemented without requiring client certificates. You can increase the security of external collaboration by requiring certificates on all client computers.

• Use IPsec. If client computers support IPsec, you can configure IPsec rules to achieve a greater level or granularity of security compared with SSL.

Secure the Central Administration site

Because external users have access to the network zone, it is important to secure the Central Administration site to block external access and secure internal access:

• Ensure that the Central Administration site is not hosted on a front-end Web server.

• Block external access to the Central Administration site. This can be achieved by placing a firewall between front-end Web servers and the server that hosts the Central Administration site.

• Configure the Central Administration site by using SSL. This ensures that communication from the internal network to the Central Administration site is secured.

Secure Shared Services Provider administration sites

Shared Services Provider (SSP) administration sites (one site per SSP) are installed on front-end Web servers. Each SSP administration site is created in a dedicated Web application. The recommendations for securing these sites include:

• Configure all SSP administration sites by using SSL. This ensures that communication from the internal network to these sites is secured.

• Configure a policy for the Web application to deny access to all external users.

Secure design checklist

Use this design checklist together with the checklists in Présentation : planifier la sécurité des batteries de serveurs (Office SharePoint Server).

Topology

Logical architecture

Plan security hardening for server roles

The following table describes additional hardening recommendations for an external secure collaboration environment.

Plan secure configurations for Office SharePoint Server features

The following table describes additional recommendations for securing Microsoft Office SharePoint Server 2007 features. These recommendations are appropriate for an external secure collaboration environment.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

• Planning and architecture for Office SharePoint Server 2007, part 2

• Planning an Extranet Environment for Office SharePoint Server

See the full list of available books at Downloadable content for Office SharePoint Server 2007