In the Windows operating system applications sometimes require administrative access to local land network
resources.
In the past it was common to give this application administrative account permissions to the resources.
For example Microsoft sequel server needs to manage its databases and it might need local administrative
access to do this in a distributed sequel solar environment with multiple sequel servers each hosting
numerous databases.
It might need administrative access to all of them for that reason.
An administrator needs to create an account for a sequel server that belongs to the domain admins group
or at least the computers local administrators group with a password that is configured to not ever
expire.
Administrators need to remember to periodically change the password manually on every server service
under which it runs.
This type of account introduces possible security issues and if compromised can endanger an entire domain.
Therefore because of the possible security issues you could consider running the program a service by
using a built in local account Windows operating systems have three built in local accounts to allow
program and servers access of resources.
These three accounts are tied to the individual computer rather than a user account.
It is connected to a local computer as follows local system.
It has extensive privileges on the local system and acts as the computer on the network.
It is a very high privilege built underground.
The name of their counties and anti authority backslash system and local service.
This has the same level of access to resources and objects as members of the local user group.
This limited access helps protect the system.
If individual services or processes are compromised services run and other local service account will
access network resources as new session without any credentials.
The name of the county's anti authority backslash local service and the sole type of such accounts are
network service.
It has more access to resources and objects than members of the user group have such as the local service
account services that run as a network service account access network resources.
By using the credentials of the computer account the name of the account is empty authority backslash
network servers.
Now you should be aware that using the local system account still might compromise security.
Considering their higher level privileges under which it operates.
Therefore you should take extra care when using this account for program Access.
Alternatively the local service account might not have enough privileges to access all the resources
required by the program.
If the program needs resources on other computers you could use the network service account.
However you must add the machine account group in the domain or individually.
On the other computers in all cases you should make a thorough security analysis to ensure you consider
all aspects of using the service account.
Next up will be talking about challenges of using the service accounts.