You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/service-accounts-govern-on-premises.md
+74-76Lines changed: 74 additions & 76 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,115 +42,113 @@ When you create service accounts, consider the information in the following tabl
42
42
| Principle| Consideration |
43
43
| - |- |
44
44
| Service account mapping| Connect the service account to a service, application, or script |
45
-
| Ownership| Ensure there's an owner who requests and assumes account responsibility |
45
+
| Ownership| Ensure there's an account owner who requests and assumes responsibility |
46
46
| Scope| Define the scope, and anticipate usage duration|
47
47
| Purpose| Create service accounts for one purpose |
48
48
| Permissions | Apply the principle of least permission. To do so:<li>Don't assign permissions to built-in groups, such as administrators<li>Remove local machine permissions, where feasible<li>Tailor access, and use AD delegation for directory access<li>Use granular access permissions<li>Set account expiration and location restrictions on user-based service accounts |
49
49
| Monitor and audit use| Monitor sign-in data, and ensure it matches the intended usage. Set alerts for anomalous usage. |
50
50
51
51
### User account restrictions
52
52
53
-
For user accounts that are used as service accounts, apply the following settings:
53
+
For user accounts used as service accounts, apply the following settings:
54
54
55
-
*[**Account expiration**](/powershell/module/activedirectory/set-adaccountexpiration?view=winserver2012-ps&preserve-view=true): Set the service account to automatically expire at a set time after its review period, unless you've determined that the account should continue.
56
-
57
-
***LogonWorkstations**: Restrict permissions where the service account can sign in. If it runs locally on a machine and accesses only resources on that machine, restrict it from signing in anywhere else.
58
-
59
-
*[**Cannot change password**](/powershell/module/activedirectory/set-aduser): Prevent the service account from changing its own password by setting the parameter to true.
55
+
* Account expiration - set the service account to automatically expire, after its review period, unless the account can continue
56
+
* LogonWorkstations - restrict service account sign-in permissions
57
+
* If it runs locally and accesses resources on the machine, restrict it from signing in elsewhere
58
+
* Cannot change password - set the parameter to **true** to prevent the service account from changing its own password
60
59
61
-
## Build a lifecycle management process
62
-
63
-
To help maintain the security of your service accounts, you must manage them from the time you identify the need until they're decommissioned.
60
+
## Lifecycle management process
64
61
65
-
For lifecycle management of service accounts, use the following process:
62
+
To help maintain service account security, manage them from inception to decommission. Use the following process:
66
63
67
-
1. Collect usage information for the account.
68
-
1. Move the service account and app to the configuration management database (CMDB).
69
-
1. Perform risk assessment or a formal review.
70
-
1. Create the service account and apply restrictions.
71
-
1. Schedule and perform recurring reviews. Adjust permissions and scopes as necessary.
72
-
1. Deprovision the account when appropriate.
64
+
1. Collect account usage information.
65
+
2. Move the service account and app to the configuration management database (CMDB).
66
+
3. Perform risk assessment or a formal review.
67
+
4. Create the service account and apply restrictions.
68
+
5. Schedule and perform recurring reviews.
69
+
6. Adjust permissions and scopes as needed.
70
+
7. Deprovision the account.
73
71
74
-
### Collect usage information for the service account
72
+
### Collect service account usage information
75
73
76
-
Collect relevant business information for each service account. The following table lists the minimum amount of information to collect, but you should collect everything that's necessary to make the business case for each account's existence.
74
+
Collect relevant information for each service account. The following table lists the minimum information to collect. Obtain what's needed to validate each account.
77
75
78
76
| Data| Description |
79
77
| - | - |
80
-
| Owner| The user or group that's accountable for the service account |
78
+
| Owner| The user or group accountable for the service account |
81
79
| Purpose| The purpose of the service account |
82
-
| Permissions (scopes)| The expected set of permissions |
83
-
| CMDB links| The cross-link service account with the target script or application and owners |
84
-
| Risk| The risk and business impact scoring, based on the security risk assessment |
85
-
| Lifetime| The anticipated maximum lifetime for enabling the scheduling of account expiration or recertification |
86
-
|||
80
+
| Permissions (scopes)| The expected permissions |
81
+
| CMDB links| The cross-link service account with the target script or application, and owners |
82
+
| Risk| The risk and business impact score, based on a security risk assessment |
83
+
| Lifetime| The anticipated maximum lifetime to schedule account expiration or recertification |
87
84
88
-
Ideally, you want to make the request for an account self-service, and require the relevant information. The owner can be an application or business owner, an IT member, or an infrastructure owner. By using a tool such as Microsoft Forms for this request and associated information, you'll make it easier to port it to your CMDB inventory tool if the account is approved.
85
+
Make the account request self-service, and require the relevant information. The owner is an application or business owner, an IT team member, or an infrastructure owner. You can use Microsoft Forms for requests and associated information. If the account is approved, use Microsoft Forms to port it to a configuration management databases (CMDB) inventory tool.
89
86
90
-
### Onboard service account to CMDB
87
+
### Service accounts and CMDB
91
88
92
-
Store the collected information in a CMDB-type application. In addition to the business information, include all dependencies on other infrastructure, apps, and processes. This central repository makes it easier to:
89
+
Store the collected information in a CMDB application. Include dependencies on infrastructure, apps, and processes. Use this central repository to:
93
90
94
-
* Assess risk.
95
-
* Configure the service account with the required restrictions.
96
-
*Understand any relevant functional and security dependencies.
97
-
* Conduct regular reviews for security and continued need.
98
-
* Contact the owners for reviewing, retiring, and changing the service account.
91
+
* Assess risk
92
+
* Configure the service account with restrictions
93
+
*Ascertain functional and security dependencies
94
+
* Conduct regular reviews for security and continued need
95
+
* Contact the owner to review, retire, and change the service account
99
96
100
-
Consider a service account that's used to run a website and has permissions to connect to one or more Human Resources (HR) SQL databases. The information stored in your CMDB for the service account, including example descriptions, is listed in the following table:
97
+
#### Example HR scenario
98
+
99
+
An example is a service account that runs a website with permissions to connect to Human Resources SQL databases. The information in the service account CMDB, including examples, is in the following table:
101
100
102
-
|Data | Example description|
101
+
|Data | Example|
103
102
| - | - |
104
-
| Owner, Deputy|John Bloom, Anna Mayers|
105
-
| Purpose| Run the HR webpage and connect to HR databases. Can impersonate end users when accessing databases. |
106
-
| Permissions, scopes| HR-WEBServer: sign in locally; run web page<br>HR-SQL1: sign in locally; read permissions on all HR databases<br>HR-SQL2: sign in locally; read permissions on Salary database only |
107
-
| Cost Center| 883944|
108
-
| Risk Assessed| Medium; Business Impact: Medium; private information; Medium |
109
-
| Account Restrictions| Log on to: only aforementioned servers; Cannot change password; MBI-Password Policy; |
103
+
| Owner, Deputy|Name, Name|
104
+
| Purpose| Run the HR webpage and connect to HR databases. Impersonate end users when accessing databases. |
105
+
| Permissions, scopes| HR-WEBServer: sign in locally; run web page<br>HR-SQL1: sign in locally; read permissions on HR databases<br>HR-SQL2: sign in locally; read permissions on Salary database only |
106
+
| Cost center| 123456|
107
+
| Risk assessed| Medium; Business Impact: Medium; private information; Medium |
108
+
| Account restrictions| Log on to: only aforementioned servers; Cannot change password; MBI-Password Policy; |
110
109
| Lifetime| Unrestricted |
111
-
| Review Cycle| Biannually (by owner, by security team, by privacy) |
112
-
|||
113
-
114
-
### Perform a risk assessment or formal review of service account usage
110
+
| Review cycle| Biannually: By owner, security team, or privacy team |
115
111
116
-
Suppose your account is compromised by an unauthorized source. Assess the risks the account might pose to its associated application or service and to your infrastructure. Consider both direct and indirect risks.
112
+
### Service account risk assessments or formal reviews
117
113
118
-
* What would an unauthorized user gain direct access to?
119
-
* What other information or systems can the service account access?
120
-
* Can the account be used to grant additional permissions?
121
-
* How will you know when the permissions change?
114
+
If your account is compromised by an unauthorized source, assess the risks to associated applications, services, and infrastructure. Consider direct and indirect risks:
122
115
123
-
After you've conducted and documented the risk assessment, you might find that the risks have an impact on:
116
+
* Resources an unauthorized user gains access to
117
+
* Other information or systems the service account can access
118
+
* Permissions the the account can grant
119
+
* Indications or signals when permissions change
124
120
125
-
* Account restrictions.
126
-
* Account lifetime.
127
-
* Account review requirements (cadence and reviewers).
121
+
After the risk assessment, documentation likely shows that risks affect account:
122
+
123
+
* Restrictions
124
+
* Lifetime
125
+
* Review requirements
126
+
* Cadence and reviewers
128
127
129
128
### Create a service account and apply account restrictions
130
129
131
-
Create a service account only after you've completed the risk assessment and documented the relevant information in your CMDB. Align the account restrictions with the risk assessment. Consider the following restrictions when they're relevant to your assessment:
132
-
133
-
* For all user accounts that you use as service accounts, define a realistic, definite end date. Set the date by using the **Account Expires** flag. For more information, see [Set-ADAccountExpiration](/powershell/module/activedirectory/set-adaccountexpiration).
134
-
135
-
* Login to the [LogonWorkstation](/powershell/module/activedirectory/set-aduser).
* Account creation in an [organizational unit location](/windows-server/identity/ad-ds/plan/delegating-administration-of-account-ous-and-resource-ous) that ensures management only for allowed users.
140
-
141
-
* Setting up and collecting auditing [that detects changes](/windows/security/threat-protection/auditing/audit-directory-service-changes) to the service account, and [service account use](https://www.manageengine.com/products/active-directory-audit/how-to/audit-kerberos-authentication-events.html).
142
-
143
-
When you're ready to put the service account into production, grant access to it more securely.
144
-
145
-
### Schedule regular reviews of service accounts
146
-
147
-
Set up regular reviews of service accounts that are classified as medium and high risk. Reviews should include:
148
-
149
-
* Owner attestation to the continued need for the account, and a justification of permissions and scopes.
150
-
151
-
* Review by privacy and security teams, including an evaluation of upstream and downstream connections.
130
+
> [!NOTE]
131
+
> Create a service account after the risk assessment, and document the findings in a CMDB. Align account restrictions with risk assessment findings.
132
+
133
+
Consider the following restrictions, although some might not be relevant to your assessment.
134
+
135
+
* For user accounts used as service accounts, define a realistic end date
136
+
* Use the **Account Expires** flag to set the date
* Create accounts in an [organizational unit location](/windows-server/identity/ad-ds/plan/delegating-administration-of-account-ous-and-resource-ous) that ensures only some users will manage it
141
+
* Set up and collect auditing that detects [service account changes](/windows/security/threat-protection/auditing/audit-directory-service-changes), and [service account usage](https://www.manageengine.com/products/active-directory-audit/how-to/audit-kerberos-authentication-events.html)
142
+
* Grant account access more securely before it goes into production
143
+
144
+
### Service account reviews
145
+
146
+
Schedule regular service account reviews, especially those classified Medium and High Risk. Reviews can include:
152
147
153
-
* Data from audits, ensuring that it's being used only for its intended purposes.
148
+
* Owner attestation of the need for the account, with justification of permissions and scopes
149
+
* Privacy and security team reviews, that include upstream and downstream dependencies
0 commit comments