Skip to content
Nubent

/Glossary · Security

What is Zero Trust?

Zero Trust is a security model that grants no implicit trust to any user, device, or network, even inside the perimeter. Every access request is explicitly verified based on identity, context, and least privilege.

How Zero Trust works

Instead of trusting everything inside the corporate network or behind a VPN, Zero Trust evaluates each request: who the user is, what device they are on, which resource they want, and whether that access makes sense right now. Identity becomes the primary perimeter, and the network becomes one more layer of defense.

On AWS, the building blocks are IAM with least privilege and temporary credentials, IAM Identity Center with multi-factor authentication, AWS Verified Access to reach internal applications without a VPN, VPC Lattice to authorize service-to-service calls, and encryption with KMS. CloudTrail and GuardDuty provide continuous verification.

When to adopt Zero Trust

It makes sense when your team works remotely, when outside vendors access internal systems, or when a VPN grants broad access to the whole network. It also applies when compliance requirements ask you to prove who accesses what and why.

Zero Trust is not something you buy or switch on overnight. You adopt it in stages: first centralized identity with MFA, then removing long-lived credentials, then application access without a VPN, and finally segmentation between services. You can verify each stage with CloudTrail and IAM Access Analyzer before moving to the next.

Best practices and common mistakes on AWS

Remove IAM users with long-lived access keys, use roles with temporary credentials for both people and workloads, and review unused permissions with IAM Access Analyzer. Apply service control policies and resource control policies to set limits at the organization level, and log every access in CloudTrail.

Common mistakes: calling a VPN with MFA Zero Trust, handing out admin permissions for convenience, trusting any traffic inside the VPC, and not revoking access for vendors whose work is done. Another is making controls so rigid that teams look for insecure workarounds.

/FAQ

Questions about Zero Trust

Another question? Write to hello@nubent.com and an engineer will answer.

Does Zero Trust replace the VPN?

It can replace it for application access. With services like AWS Verified Access, each request is authorized based on identity and device posture, without exposing the whole network. A VPN can still be useful for specific cases, such as connecting networks to each other.

What are the principles of Zero Trust?

Verify every access explicitly, grant the least privilege needed, and assume the environment may already be compromised. In practice, that means strong identity, permissions scoped in time and reach, segmentation, encryption, and continuous monitoring of activity.

How do you get started with Zero Trust on AWS?

Centralize human access with IAM Identity Center and MFA, remove long-lived access keys, review permissions with IAM Access Analyzer, and split workloads into separate accounts. Then move on to application access without a VPN and service-to-service authorization.

Next step

What should we build next on AWS?

30 minutes with an engineer. Concrete next steps, whether or not you work with us.