Excel Services Best Practices
Last modified: July 20, 2011
Applies to: SharePoint Server 2013
This topic contains a list of best-practice recommendations for working with Excel Services.
Anonymous Access and Information Disclosure
The following settings combination gives anonymous users access to any files in the share to which the process account has access. Therefore, the following combination of settings is not recommended, because of the possibility of information disclosure:
Anonymous access to Microsoft SharePoint Foundation is turned on.
You have a UNC trusted location and the Process account is turned on.
The Process account is a global Excel Services setting that affects all trusted locations.
To view the Process account option
On the Start menu, click All Programs.
Point to Microsoft SharePoint 2010 Products, and then click SharePoint Central Administration.
Under Application Management, click Manage service applications.
On the Manage Service Applications page, click Excel Services Application.
On the Excel Services Application page, click Global Settings.
In the Security section, look under File Access Method for the Process account option.
Denial of Service Attack
In a denial of service attack against a Web service, an attacker generates very large, individual requests against the Web service. The purpose is to attempt to exploit the limits of one or more Web service input values.
We recommend that you use the Microsoft Internet Information Services (IIS) setting to set the maximum request size for the Web service.
Use the maxRequestLength attribute in the httpRuntime element in the system.web element to prevent denial of service attacks that are caused by users posting large files to the server. The default size is 4096 KB (4 MB).
Sniffing Between the Calling Application and the Web Service Computer
If the calling application and Excel Web Services are deployed to different computers, an attacker can listen to the network traffic for data transfer between the calling application and the Web service. This threat is also called "sniffing" or "eavesdropping."
To help mitigate this threat, we recommend that you:
Use Secure Sockets Layer (SSL) to set up a secure channel to protect data transfer between the client and the server. The SSL protocol helps to protect data against packet sniffing by anyone with physical access to the network.
Physically protect the relevant network if a custom application using Excel Web Services is running in a confined network—for example, if Excel Web Services is deployed on a Web front-end computer within the enterprise.
For information about Excel Services topology, scalability, performance, and security, see the Microsoft SharePoint Server 2010 TechCenter.
We recommend that you use SSL to help mitigate the threats of hijacked Web service Internet Protocol (IP) addresses and ports, and to help prevent attackers from receiving requests and replying on behalf of the Web service.
The SSL certificate is matched against a few properties, one of which is the IP address from which the message is coming. The attacker cannot spoof the IP address if it does not have the Web service SSL certificate.
For more information, see Securing Your Network.
Strong Name Dependencies
In some cases, a user-defined function (UDF) assembly depends on other assemblies that are deployed with it. These dependent DLLs load successfully if they are in the global assembly cache, or if they are located in the same folder as the UDF assembly.
In the latter case, however, it is possible for the load to fail if Excel Calculation Services has already loaded another assembly with the same name. (It fails either because the assembly is not strongly named, or because another version with the same name has been deployed and loaded.)
Consider the following scenario, with the following directory structure:
The Udf01 folder contains:
dependent.dll (not strongly named)
The Udf01.dll file has a dependency on the dependent.dll file.
The Udf02 folder contains:
Udf02.dll (which depends on Interop.dll)
dependent.dll (which is not strongly named)
The Udf02.dll file has a dependency on the dependent.dll file. Udf01.dll's dependency and Udf02.dll's dependency share the same name. But Udf02.dll's dependent.dll file is not the same as Udf01.dll's dependent.dll file.
Assume the following flow:
Udf01.dll is the first DLL to be loaded. Excel Calculation Services looks for dependent.dll and loads Udf01.dll's dependency, which in this case is dependent.dll.
Udf02.dll is loaded after Udf01.dll. Excel Calculation Services sees that Udf02.dll depends on dependent.dll. However, a DLL with the name "dependent.dll" is already loaded. Therefore, Udf02.dll's dependent.dll file is not loaded, and the currently loaded dependent.dll file is used as the dependency.
As a result, the object—in this case, the dependent.dll file that Udf02.dll needs—is not loaded into memory.
To avoid name collision, we recommend that you strongly name your dependencies, and name them uniquely.
Naming Managed-Code DLLs
To ensure that your assembly names are unique, use the fully qualified class name, following the Namespace Naming Guidelines.
For example, use CompanyName.Hierarchichal.Namespace.ClassName instead of Namespace.ClassName.