A security baseline for a service company that does not live in an office
Passwords, phones, and customer history for crews and dispatchers. A short baseline, not a security product.
The lobby model does not fit a truck
Most security advice assumes a building. Badges, a server room, people at desks. A service company has a dispatcher, a handful of shared trucks, phones that are also personal, and a customer list that is the business. The baseline has to fit that, or it will be ignored by Thursday.
Do these before you buy a platform
- One login per person, including the owner. Shared “office” and “tech” accounts make a departure messy and a theft invisible.
- A written list of admin accounts. Email, the scheduling tool, the accounting file, the domain name, the phone vendor. If only one person can reset them, that person is a risk even if you trust them.
- Customer history in a system, not a thread. Text messages are useful. They are not a file you can hand to the next technician.
- Phones that can be wiped if a truck is broken into. You do not need a fancy suite to decide this. You need to know whether you can.
- Mail that is not a personal account. Invoices sent from a private Gmail walk away with the employee.
- A backup of the one machine that holds accounting or dispatch, and a date when someone opened that backup and saw real jobs in it.
What this is not
It is not a penetration test and it is not a claim that you are “secure.” It is the shortest list that keeps a twenty-person service company from losing the week because one phone disappeared. The service-company brief starts from whatever is true on that list today.