How are MSP clients kept separate in a multi-tenant security tool?
In a well-built tool, separation is enforced by the system itself, not only by the user interface, so a mistake or a bug in one screen cannot show one client's data to another. Ask vendors how: is every record tagged with a tenant, does the database refuse cross-tenant queries, and are staff accounts limited to the tenants they serve? In NetSenX each customer is its own tenant, kept apart in the database by row-level security, so queries only return rows of the tenant they belong to. On your side, give technicians separate accounts with multi-factor authentication, grant access per client, and remove it when someone leaves or a client ends the contract.