An IT handover flagged unmanaged devices, Windows Home endpoints and users with local admin rights. There are hundreds of remote staff and limited IT capacity. Management is hesitant about licensing costs. How would you prioritize this and make the case for help?
Where do I start with security gaps at a small organization?
Answers
First, pin down what the organization actually has to comply with. An insurance policy, customer contract and security regulation can have different requirements. The handover is a useful starting point, but it doesn't establish that every Windows Home machine would fail an audit.
Make an inventory of devices, who uses them, what data they access and which controls are already in place. Then map the gaps to the applicable requirements. That gives you something more concrete than a general warning about compliance.
Reply to this answer
For the licensing discussion, talk about capabilities rather than just the edition name. Windows Pro can support domain or Entra ID join and BitLocker management, depending on the setup. Check what the existing devices support and what management tools and licenses you'd need before pricing a rollout.
Don't assume an upgrade alone fixes unmanaged endpoints. You still need a way to enroll them, apply policies and support remote users.
Reply to this answer
Local admin rights are worth tackling, but don't flip the switch for everyone at once. Find out which applications need elevated access, test standard-user accounts with a small group, and have a process for approved installs and exceptions. Otherwise you could leave remote staff unable to work.
In parallel, check whether work files are stored somewhere the organization can back up and restore. A central location helps only if the backups and access controls are actually set up.
Reply to this answer
Put a short proposal in front of the manager. List the main risks, a rough cost for licensing and endpoint management, and the staff time needed to roll it out. Include an option for outside support or another IT hire, because hundreds of remote users are a lot for one person to coordinate.
Ask for a decision on priorities and budget, then record the response and any accepted risks in writing. You can recommend the work, but management needs to decide what resources to commit.
r.346~velqumi:
Breaking the proposal into phases may help too. A pilot can show the cost and workload before asking for the full rollout.
Reply to this answer
I wouldn't make a career decision after a couple of days of budget discussions. Give management a clear plan and see how they respond. If they expect one person to fix everything without time, money or support, that's useful information when deciding whether to stay.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_z.91+quimelo:
That makes sense. I'll ask management which contracts, policies and audit requirements they expect IT to meet.