System accounts deactivated from Vulnerability scan

[chmc]

Security Manager ran a new vulnerabilty scan. I have several system accounts that are now deactivated. We are on a trusted system. If I choose to reactivate the account it will assign a password becasue these accounts did not previously have one (that's the message I get) If they did not have one before I am not sure if adding one will cause a problem. System is running fine though without these activated. Some could even be old accounts that are no longer in use. Do any of these stand out as needed accounts and if I reactivate and it adds a password will there be a problem?

adm
bin
daemon
lp
sys

thank you.

[Jeff_Traigle]

They are needed, but they don't need to be enabled. In an unTrusted environment, they are typically locked.

[Bill Hassell · Accepted solution]

If by "system accounts" you mean something like the mail or lp user, that's fine to leave them deactivated. No one logs in using these accounts, then it's fine to leave them deactivated. This does not mean the user ID is invalid, it just means that no one can login using these accounts. mail and lp will still work because no has to login to use these features.

[chmc]

thanks for the quick replies and explanation of why it was ok for the accounts to be deactivated.