# 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.

FAQ: [MSPs and MSSPs](https://netsenx.com/en/faq/msp) · https://netsenx.com/en/faq/how-are-msp-clients-kept-separate-in-a-multi-tenant-security-tool

## Read next

- https://netsenx.com/en/problems-we-solve
- https://netsenx.com/en/partners

## Related questions

- [Does NetSenX have a partner programme for MSPs and resellers?](https://netsenx.com/en/faq/does-netsenx-have-a-partner-programme-for-msps)
- [Can an MSP white-label detection reports?](https://netsenx.com/en/faq/can-an-msp-white-label-detection-reports)
- [Can an MSP generate PDF security reports for each client?](https://netsenx.com/en/faq/can-an-msp-generate-pdf-security-reports-for-each-client)
- [Per-device or per-site pricing: which works better for an MSP with small clients?](https://netsenx.com/en/faq/per-device-or-per-site-pricing-for-an-msp)
- [How can an MSP monitor very small clients profitably?](https://netsenx.com/en/faq/how-can-an-msp-monitor-very-small-clients-profitably)