Service Accounts: The Logins No Person Owns and Nobody Reviews

When the business office scanner stops emailing documents, someone eventually discovers it was set up three years ago with a login called something like "scan" and a password that has not changed since. The person who created it left long ago. Nobody knows what else that login can reach.

That login is a service account: a sign-in used by a device or a piece of software rather than a human being. Every care facility has them, and they are among the least reviewed credentials in the building.

What service accounts do

When a machine or program needs to talk to another system, it often needs to log in the way a person would. Common examples include:

A copier or scanner that sends scans to email or to a shared folder.

Backup software that reads files and databases overnight.

Your EHR or billing system connecting to another system to move data.

A monitoring tool, a phone system or a door access system that reads from a directory.

A script an earlier IT person wrote to automate a task.

Nobody sits at a keyboard typing these passwords, so they tend to be set once and never touched again. Often they are given generous permissions "to make it work," and passwords are frequently set so they never expire.

Why they become a problem

A service account has no human to notice something odd. It does not get a sign-in alert on a phone. It cannot be asked to use a second verification step in the usual way. If its password is stolen, whoever has it can use it quietly, often at hours nobody is watching.

There is also the simple matter of ownership. When a vendor is replaced, the old integration may be turned off, but its account is left behind with full access. When an employee who created an account leaves, no one is responsible for it anymore. An orphaned login with broad permissions is exactly what you do not want to find during a security review or an insurance questionnaire.

Give every service account an owner

An owner is a named person, usually a department head or your IT provider's contact, who answers three questions for that account: what is it for, who may change it, and is it still needed.

Start with an inventory. For each account, record:

Its name and where it is used (which scanner, which backup, which system).

What it can access, and whether that is more than the job requires.

The business owner and the technical owner.

When the password was last changed and where the password is stored.

What would break if the account were disabled.

A simple spreadsheet in a restricted location is a fine start. The goal is that no one has to guess later.

Tighten what each account can do

Once you know what each one is for, reduce its reach.

Give it only the folders, mailboxes or systems it needs. A scanner account needs to write to one folder, not to read the whole file server.

Use a long, unique password for each account, kept in a company password manager rather than in a note on the copier or in someone's email.

Where the system supports it, restrict the account to sign in only from the device or address it should use.

Avoid using a person's own login for a device. When that person leaves, the device quietly stops working, and their access lingers in odd places.

Review them on a schedule

Put a review on the calendar, perhaps twice a year. Ask whether each account is still in use, whether the owner is still here, and whether the password has been rotated. Disable accounts for equipment you no longer have, and watch what breaks before deleting. A day or two of disabled status is a gentler test than guessing.

Also make account creation part of purchasing. When a new scanner, camera system or software package is installed, the vendor or IT provider should record the service account and its owner on day one.

What to do when the owner leaves

Treat the departure of an account owner like any other offboarding step. Before the last day, reassign each service account they own to someone else and change the password if they knew it. This takes minutes and prevents the "nobody knows who made this" problem.

How we can help

UnityCare IT finds and documents the service accounts in your environment, helps assign owners, narrows their permissions and keeps their passwords in a managed vault. We can fold a periodic review into your regular managed IT service, so these logins stop being the ones nobody remembers.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support