Security and protection for SharePoint Foundation 2010
Applies to: SharePoint Foundation 2010
This section provides information and best practices about how to make the Microsoft SharePoint Foundation 2010 system more secure and how to help protect data.
In this section:
|SharePoint Foundation 2010 uses several Windows encryption algorithms for computing hash values that do not comply with Federal Information Processing Standard (FIPS) 140-2, Security Requirements for Cryptographic Modules. These algorithms are not used for security purposes; they are used for internal processing. For example, SharePoint Foundation 2010 uses MD5 to create hash values that are used as unique identifiers.
Because SharePoint Foundation 2010 uses these algorithms, it does not support the Windows security policy setting that requires FIPS compliant algorithms for encryption and hashing. This Windows security policy is managed through the FIPSAlgorithmPolicy registry key in Windows, which is described in the "Configure FIPS policy for a mixed environment" section of the following topic:
The goal of FIPS is to provide a standardized way to ensure the security and privacy of sensitive information in computer systems of the United States and Canadian governments. Using a FIPS compliant algorithm for encryption of data over an open network is a key requirement for FISMA certification. The Windows FIPSAlgorithmPolicy registry key is neither necessary nor sufficient for FISMA certification, it is a useful enforcement tool for many solutions, but not SharePoint Foundation 2010.
The FIPS contribution to FISMA certification is the strength of encryption used for security purposes. Security-related encryption within SharePoint Foundation 2010 is performed by using FIPS-compliant cipher suites.
For additional information about FISMA, FISMA certification, and reverse proxy see the following articles:
- Federal Information Security Management Act (FISMA) Implementation Project (http://go.microsoft.com/fwlink/?LinkId=242329)