SP13-00-000165 - The SharePoint farm service account (database access account) must be configured with minimum privileges on the SQL server.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

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.

This requirement is intended to limit exposure due to user accounts being used to operate from within a privileged account or role. Limiting the access and permissions of privileged accounts to the minimum required, reduces exposure if the account is compromised and provides forensic history of activity when operating from these accounts.
This policy limits the Farm Account privileges in AD. However, default permissions for this account are configured by the SharePoint Products Configuration Wizard during product installation. This account is referred to during the installation as the 'Database Access' account. By default, the account is used as the service account for the SharePoint Timer Service and the SharePoint Central Administration Web Site Application Pool. These settings should not be changed. Furthermore, this account should not be used as the service account for non-privileged services, applications, or application pools.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

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.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_MS_SharePoint_2013_V2R2_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000366, Rule-ID|SV-223268r612235_rule, STIG-ID|SP13-00-000165, STIG-Legacy|SV-74429, STIG-Legacy|V-59999, Vuln-ID|V-223268

Plugin: Windows

Control ID: a23d81de80c1e9186a33d528fac5151f8a95f79d26dc8f39b41106757015342d