What is zero trust security?

Zero trust security is a security model that grants no implicit trust to any user, device or application based on its network location. Every access request is verified explicitly, using identity, device state and context, and each approved request gets only the access its task needs. The aim is to limit what any single compromised account can reach.

What are the core principles?

  • Explicit verification: each request is checked for who is asking, whether the device is in a known state and the context, such as location, time and the resource requested. Multi-factor sign-in is usually the first check. Being inside the network counts for nothing.
  • Least privilege: an approved request receives access to the specific resources the task needs, for as long as the task needs them, and nothing wider.
  • Assumed breach: the design expects that some account or device is already compromised, so access is segmented to limit what that compromise can reach.

NIST describes the model in SP 800-207, and its SP 1800-35 guide documents example builds from multiple vendors.

How does zero trust limit blast radius?

Administrative blast radius is everything one account can reach or change. In a flat design, one domain administrator login may reach production servers, the hypervisor and the backups. Zero trust splits those into separately verified scopes, so a compromised account in one scope gains nothing in another.

How does it apply to backup systems?

The backup server, the management console and the backup storage each require their own authentication, with identities that are not shared with the production directory. Storage access keys are scoped to specific buckets. Administrative roles are split, so the role that schedules jobs cannot change storage retention settings. A credential stolen from any one of these components reaches nothing in the others.

Where does zero trust stop working?

It cannot tell a legitimate administrator from an attacker holding a phished password and second factor that pass every check. A valid session is allowed in. Zero trust narrows what that session can touch, but it does not flag the session as hostile, which is why credential theft remains a problem under any architecture. The same narrowing limits insider threat cases, where access was legitimately granted.

Every additional account, key and role also has to be created, rotated and reviewed. Designs that are not maintained drift back toward shared accounts and broad permissions.

What protects backups when a verified session is hostile?

Storage that refuses deletion. Access policies at the storage layer limit what a session can do, and S3 Object Lock in compliance mode keeps locked backups in place even if a session is compromised. The two controls answer different questions: zero trust decides who may act, and the lock decides what happens when the wrong party acts anyway, which is what blocks backup tampering.

Frequently asked questions

Is zero trust a product?

No. It is a security model that combines identity, device and network controls. Products implement parts of it.

Does zero trust replace a firewall?

It removes the assumption that traffic behind the firewall is safe. Network controls still exist, but they are not treated as proof of trust.

Does zero trust apply to backup software?

Yes. Backup consoles and repositories hold broad access to data, so separating their identities and scoping their keys follows the same logic as for any sensitive system.