Glossary / Zero Trust (security model)
Zero Trust (security model)
A security model built on "never trust, always verify" — no user, device, or network segment is trusted by default, and every access request is authenticated and authorized explicitly, inside the network or out.
Zero Trust replaces the older "castle and moat" assumption — that anything inside the corporate network perimeter is safe — with a default-deny posture: every request for a resource gets verified on its own merits, regardless of whether it originates from an office desktop or a laptop on public Wi-Fi. The shift happened largely because the perimeter itself stopped meaning much once remote work, cloud apps, and BYOD became normal — there was no longer a clean "inside" to trust.
In practice, Zero Trust is a bundle of controls rather than one product: strong identity verification (MFA on every login, not just the first one), device posture checks (is this specific device patched and encrypted before it gets access), least-privilege authorization (a user or service account gets exactly the permissions the task requires, not broad network access by default), and segmentation (a breach in one area doesn't grant a free path to everything else).
For an MSP, the principle applies with extra weight to the MSP's own access into client environments — the RMM agent, remote-control sessions, and any credential used to manage a client system are high-value targets in their own right, so verifying every command cryptographically rather than trusting anything that arrives over the right network connection is Zero Trust applied to the very tool doing the managing.
How Nexus handles this
Nexus applies Zero Trust to its own management channel: the agent is outbound-only, so there's no open inbound port to implicitly trust, and every remote job is Ed25519-signed and verified on the endpoint rather than trusted because it arrived over the right connection.
More terms
MSP (Managed Service Provider)
A company that remotely manages a client's IT infrastructure and end-user systems on an ongoing, proactive basis — usually a flat-fee contract, not break-fix billing.
RMM (Remote Monitoring and Management)
Software that lets an MSP monitor device health and perform remote management tasks — patching, scripting, remote control — across every client site from one console.
PSA (Professional Services Automation)
Software that runs the business side of MSP operations — ticketing, SLAs, billing, contracts, and client records — the system of record most MSP work flows through.
Ready to see it in the platform?
Join the design-partner cohort and we'll show you exactly where this lives.