Share via

Plan for least-privileged administration in SharePoint Server

  • Article

APPLIES TO: yes-img-132013 yes-img-162016 yes-img-192019 yes-img-seSubscription Edition no-img-sopSharePoint in Microsoft 365

The concept of least-privileged administration is to assign users the minimum permissions that are required for users to complete authorized tasks. The goal of least-privileged administration is to configure and help maintain secure control of an environment. The result is that each account under which a service runs is granted access to only the resources that are necessary.

Microsoft recommends deploying SharePoint Server with least-privileged administration. Implementing least-privileged administration can result in increased operational costs as other resources might be required to maintain this level of administration. Moreover, the ability to troubleshoot security problems become more complex.

Introduction

Organizations implement least-privileged administration to achieve better security than would be typically recommended. Only a small percentage of organizations requires this heightened level of security because of the resource costs of maintaining least-privileged administration. Some deployments that might require this heightened level of security include governmental agencies, security organizations, and organizations in the financial services industry. The implementation of a least-privileged environment shouldn't be confused with best practices. In a least-privileged environment, administrators implement best practices together with other heightened levels of security.

Least-privileged environment for accounts and services

To plan for least-privileged administration, you must consider several accounts, roles, and services. Some apply to SQL Server and some apply to SharePoint Server. As administrators lock down other accounts and services, daily operational costs are likely to increase.

SQL Server roles

In a SharePoint Server environment, several accounts may be granted the following two SQL Server server-level roles. In a least-privileged SharePoint Server environment, we recommend that you only grant these privileges to the account under which the Microsoft SharePoint Foundation Workflow Timer Service runs. Typically, the timer service runs under the server farm account. For day-to-day operations, we recommend that you remove the following two SQL Server server-level roles from all other accounts that are used for SharePoint administration:

  • Dbcreator - Members of the dbcreator fixed server role can create, alter, drop, and restore any database.

  • Securityadmin - Members of the securityadmin fixed server role manage logins and their properties. They can GRANT, DENY, and REVOKE server-level permissions. They can also GRANT, DENY, and REVOKE database-level permissions if they have access to a database. Additionally, they can reset passwords for SQL Server logins.

Note

The ability to grant access to the database engine and to configure user permissions allows the securityadmin to assign most server permissions. You should treat the securityadmin role as equal to the sysadmin role.

For more information about SQL Server server-level roles, see Server Level Roles.

If you remove one or more of these SQL Server roles, you might receive "Unexpected" error messages in the Central Administration web site. In addition, you may receive the following message in the Unified Logging Service (ULS) log file:

System.Data.SqlClient.SqlException... <operation type> permission denied in database <database>. Table <table>

Along with an error message that may be displayed, you may be unable to perform any of the following tasks:

  • Restore a backup of a farm because you can't write to a database

  • Provision a service instance or web application

  • Configure managed accounts

  • Change managed accounts for web applications

  • Perform any action on any database, managed account, or service that requires the Central Administration web site

In certain situations, database administrators (DBAs) may want to operate independently from SharePoint Server administrators and create and manage all the databases. This is typical in IT environments where security requirements and company policies require a separation of administrator roles. The farm administrator provides SharePoint Server database requirements to the DBA, who then creates the necessary databases and sets up the logins that are required for the farm.

By default, the DBA has complete access to the SQL Server instance but requires additional permissions to access SharePoint Server. DBAs typically use Windows PowerShell 3.0 when they add, create, move, or rename SharePoint databases, so they must be a member of the following accounts:

  • Securityadmin fixed server role on the SQL Server instance.

  • Db_owner fixed database role on all databases in the SharePoint farm.

  • Administrators group on the computer on which they run the PowerShell cmdlets.

Additionally, the DBA may have to be a member of the SharePoint_Shell_Access role to access the SharePoint content database. In some conditions, the DBA may want to add the Setup user account to the db_owner role.

SharePoint Server roles and services

In general, you should remove the ability to create new databases from SharePoint Server service accounts. No SharePoint Server service account should have the sysadmin role on the SQL Server instance and no SharePoint Server service account should be a local Administrator on the server that runs SQL Server.

For more information about SharePoint Server accounts, see Account permissions and security settings in SharePoint Server 2016.

For account information in SharePoint Server 2013, see Account permissions and security settings in SharePoint 2013.

The following list provides information about locking down other SharePoint Server roles and services:

  • SharePoint_Shell_Access role

    When you remove this SQL Server role, you remove the ability to write entries to the configuration and content database and the ability to perform any tasks by using Microsoft PowerShell. For more information about this role, see Add-SPShellAdmin.

  • SharePoint Timer service (SPTimerV4)

    We recommend that you don't limit the default permissions granted to the account under which this service runs and that you never disable this account. Instead, use a secure user account, for which the password isn't widely known, and leave the service running. By default, this service is installed when you install SharePoint Server and maintains configuration cache information. If you set the service type to disabled, you may experience the following behavior:

    • Timer jobs won't run

    • Health analyzer rules won't run

    • Maintenance and farm configuration will be out of date

  • SharePoint Administration service (SPAdminV4)

    This service performs automated changes that require local administrator permission on the server. When the service isn't running, you must manually process server-level administrative changes. We recommend that you don't limit the default permissions granted to the account under which this service runs and that you never disable this account. Instead, use a secure user account, for which the password isn't widely known, and leave the service running. If you set the service type to disabled, you may experience the following behavior:

    • Administrative timer jobs won't run

    • Web configuration files won't be updated

    • Security and local groups won't be updated

    • Registry values and keys won't be written

    • Services may be unable to be started or restarted

    • Provisioning of services may be unable to be completed

  • SPUserCodeV4 Service

    This service lets a site collection administrator upload sandboxed solution to the Solutions gallery. If you are not using sandboxed solutions, you can disable this service.

  • Claims To Windows Token service (C2WTS)

    By default, this service is disabled. The C2WTS service may be required for a deployment with Excel Services, PerformancePoint Services, or SharePoint shared services that must translate between SharePoint security tokens and Windows-based identities. For example, you use this service when you configure Kerberos-constrained delegation for accessing external data sources. For more information about C2WTS, see Plan for Kerberos authentication in SharePoint Server.

The following features may experience additional symptoms under certain circumstances:

  • Backup and restore

    The ability to perform a restore from a backup may fail if you have removed database permissions.

  • Upgrade

    The upgrade process starts correctly, but then fails if you don't have suitable permissions to databases. If your organization is already in a least-privileged environment, the workaround is to move to a best practices environment to complete the upgrade, and then move back to a least-privileged environment.

  • Update

    The ability to apply a software update to a farm succeeds for the schema of the configuration database, but fail on the content database and services.

Additional things to consider for a least-privileged environment

In addition to the previous considerations, you might have to consider more operations. The following list is incomplete. Selectively use the items at your own discretion:

  • Setup user account - This account is used to set up each server in a farm. The account must be a member of the Administrators group on each server in the SharePoint Server farm. For additional information about this account, see Initial deployment administrative and service accounts in SharePoint Server.

    When you build a new SharePoint farm and the based build has October 2022 CU or a new slipstreamed into the build process, you're using the least privileged security model. After completing the psconfig on the first server in the farm, prior to running the Farm configuration wizard or provisioning other components, the following commands must be executed to ensure access to the SharePoint Databases:

    Get-SPDatabase | %{$_.GrantOwnerAccessToDatabaseAccount()}

  • Synchronization account - For SharePoint Server, this account is used to connect to the directory service. We recommend that you don't limit the default permissions granted to the account under which this service runs and that you never disable this account. Instead, use a secure user account, for which the password isn't widely known, and leave the service running. This account also requires Replicate Directory Changes permission on AD DS, which enables the account to read AD DS objects and to discover AD DS objects that were changed in the domain. The Grant Replicate Directory Changes permission doesn't enable an account to create, change or delete AD DS objects.

  • My Site host application pool account - This is the account under which the My Site application pool runs. To configure this account, you must be a member of the Farm Administrators group. You can limit privileges to this account.

  • Built-in user group - Removing the built-in user security group or changing the permissions may have unanticipated consequences. We recommend that you don't limit privileges to any built-in accounts or groups.

  • Group permissions - By default the WSS_ADMIN_WPG SharePoint group has read and write access to local resources. The following WSS_ADMIN_WPG file system locations, %WINDIR%\System32\drivers\etc\Hosts and %WINDIR%\Tasks are needed for SharePoint Server to work correctly. If other services or applications are running on a server, you might consider how they access the Tasks or Hosts folder locations. For additional information about account settings for SharePoint Server, see Account permissions and security settings in SharePoint Server 2016.

    For account information in SharePoint Server 2013, see Account permissions and security settings in SharePoint 2013.

  • Change permission of a service - A change of a permission of a service may have unanticipated consequences. For example, if the following registry key, HKLM\System\CurrentControlSet\Services\PerfProc\Performance\Disable Performance Counters, has the value of 0, the User Code Host service would be disabled which would cause sandboxed solutions to stop working.

See also

Other Resources

Least Privilege Configuration for Workflow Manager with SharePoint 2013