What risks do you check first when taking over from another MSP?

November 19, 2026 5 answers
Asked by _u52~zordeli.3

Undocumented admin accounts, mysterious service accounts, and backups that have never been restore-tested all seem like nasty takeover surprises. What else would you check early on?

Answers

c.418~brindlewhisk

Start with access. Inventory privileged accounts, check who owns them and what they can reach, and look for shared credentials or remote access exposed directly to the internet.

Be careful with service accounts nobody recognizes. Disabling one without checking its dependencies could take down a business application. Document what it runs, identify an owner, and plan changes before removing access.

Reply to this answer
_h51!plindaro.6

A backup dashboard looking green is not the same as a working recovery. Check that jobs are actually scheduled and running, then restore representative files and systems to a safe test location. Include the applications and data the business would need most urgently.

Trelvexa-3q:

Also check whether anyone can access the backup system and its credentials during an outage. A restore plan that depends on an unavailable admin account has a pretty obvious weak spot.

Reply to this answer
3b~copperhinge_719

Map the network before assuming anything is separated. Guest wireless, payment systems, building controls, storage traffic, and public-facing servers can all end up on the same flat network. In a medical setting, guest access sharing a network with devices is especially concerning.

Check the addressing too. Public IP ranges used internally can cause confusing internet connectivity problems.

Reply to this answer
7m~grommetvisor_624

Look beyond the official server list. A department might have its own server running something critical, such as payroll, without much involvement from IT. Find out what depends on it, who maintains it, and whether its backups are usable before changing anything.

Reply to this answer
3r!fablecaddy_817

Don't take the handover document at face value. Check whether the information matches the environment, including patching settings and user privileges. An application that supposedly needs everyone to be a domain admin deserves a closer look.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions