98-365 · Question #34
You need to limit what a service can access. You should change the service's:
The correct answer is D. Logon options. To limit what a service can access, you should change its logon options, which define the security context (user account) under which the service runs and thus its permissions.
Question
You need to limit what a service can access. You should change the service's:
Options
- ADependencies
- BStatus
- CStartup type
- DLogon options
How the community answered
(26 responses)- A8% (2)
- B4% (1)
- C4% (1)
- D85% (22)
Why each option
To limit what a service can access, you should change its logon options, which define the security context (user account) under which the service runs and thus its permissions.
Dependencies define which other services must be running before a particular service can start, but they do not directly control the access rights of the service itself.
A service's status indicates whether it is running, stopped, or paused, which does not define its access permissions.
The startup type determines how and when a service starts (e.g., Automatic, Manual, Disabled), but it does not control the service's access permissions.
A service's logon options determine the user account under which the service runs, directly impacting the permissions and access rights it inherits. By assigning a service to a less privileged account (e.g., Network Service, Local Service, or a custom low-privilege account), you can significantly limit its access to system resources and files, thereby enhancing security.
Concept tested: Service account privileges and security context
Source: https://learn.microsoft.com/en-us/windows/win32/services/service-user-accounts
Topics
Community Discussion
No community discussion yet for this question.