From MS SharePoint 2013 Security Technical Implementation Guide
Part of SRG-APP-000062
Associated with: CCI-000366
Separation of duties is a prevalent Information Technology control implemented at different layers of the information system including the operating system and in applications. It serves to eliminate or reduce the possibility that a single user may carry out a prohibited action. Separation of duties requires the person accountable for approving an action not be the same person who is tasked with implementing the action.
Review the SharePoint server configuration to ensure the farm service account (database access account) is configured with minimum privileges on the SQL server. - Launch the SQL Server Management Console and navigate to Security >> Logins. - Select the SharePoint farm service account. - Click on "Server Roles" and verify only public, dbcreator, and securityadmin are checked. - Click on "User Mapping" and verify that the farm account is a member of the public and db_owner role on each SharePoint database. Otherwise, this is a finding.
Configure the SharePoint farm service account (database access account) with minimum privileges on the SQL server. Configure the account on each SQL server in the farm. - Launch the SQL Server Management Console and navigate to Security >> Logins. - Select the SharePoint farm service account. - Click on Server Roles. - Ensure only public, dbcreator, and securityadmin roles are checked. - Remove checks from all other roles.
Lavender hyperlinks in small type off to the right (of CSS
class id
, if you view the page source) point to
globally unique URIs for each document and item. Copy the
link location and paste anywhere you need to talk
unambiguously about these things.
You can obtain data about documents and items in other
formats. Simply provide an HTTP header Accept:
text/turtle
or
Accept: application/rdf+xml
.
Powered by sagemincer