Cloud concept · Updated

Trust Boundaries - Trust boundaries are points where data, requests, or identities cross between environments with different security assumptions or levels of control.

In short

A trust boundary marks where a system must reassess whether an interaction is authentic, authorized, and safe rather than inheriting trust from its origin. Identifying these boundaries helps engineers choose network, identity, and application controls that address the threats created by a particular architecture.

Cloud Concepts Hub →

6 key aspects of Trust Boundaries

Effective trust boundaries combine architecture-specific threat modeling, explicit access checks, constrained connectivity, validation, containment, and continuous verification.

01
Architecture-driven threat modeling

Identify boundaries from data flows, execution contexts, administrative ownership, and tenant separation. A public web application, a microservices platform, and an event-driven workflow require different checks even when they use the same network.

02
Explicit authentication and authorization

Authenticate callers and authorize the requested action when crossing a boundary. Private addresses, encrypted connections, and membership in the same account are not substitutes for permission checks.

03
Least-privilege connectivity

Permit only the sources, destinations, protocols, and ports required by the application. Combine network restrictions with workload and resource permissions so that one compromised component has limited reach and authority.

04
Validation across trust contexts

Treat incoming payloads, events, headers, and tenant identifiers as untrusted until validated. A request that passed an edge filter can still contain unauthorized object references or invalid business operations.

05
Containment and administrative isolation

Use appropriately scoped accounts, networks, roles, and resource policies to limit lateral movement and separate ownership. Check that shared connectivity and centralized administration do not unintentionally bypass those controls.

06
Observable and testable enforcement

Record relevant network flows, authentication decisions, and resource access. Test denied paths as well as successful requests, and detect configuration changes that weaken the intended boundary.

Cloud services for Trust Boundaries

Amazon VPC constrains network reachability, while IAM determines which identities may act on resources. AWS Organizations adds account-level governance so teams cannot freely weaken selected controls. AWS Network Firewall inspects routed network traffic, and AWS WAF applies HTTP-layer filtering at supported application entry points. AWS PrivateLink can expose a specific service privately without connecting entire networks. Together, these services enforce different aspects of a trust boundary rather than replacing one another. Engineers must align routing, filtering, identity policies, and application authorization, then use logs and access tests to verify that allowed flows work and prohibited crossings fail.

Amazon VPCAmazon VPC

Amazon VPC provides network isolation and controls such as route tables, security groups, and network ACLs that constrain traffic across boundaries. VPC Flow Logs help investigate accepted and rejected traffic, but network placement alone does not establish application trust.

AWS Network FirewallAWS Network Firewall

AWS Network Firewall inspects traffic routed through its endpoints and applies stateless and stateful rules. It supports network-boundary enforcement, but routing must ensure that the intended traffic traverses inspection and that stateful flows have compatible forward and return paths.

AWS WAFAWS WAF

AWS WAF filters HTTP and HTTPS requests at supported application entry points using rules for request attributes, attack patterns, and request rates. It reduces exposure at an application boundary but does not replace application authentication or object-level authorization.

AWS PrivateLinkAWS PrivateLink

AWS PrivateLink provides private access to supported services without requiring broad network connectivity between consumers and providers. Service access must still be constrained through the applicable endpoint controls, resource policies, and application authentication.

AWS OrganizationsAWS Organizations

AWS Organizations supports account-based administrative separation and organization-wide guardrails. Service control policies limit the available permissions for affected member-account principals, but they do not grant access or filter network traffic.

Trust Boundaries exam questions

Real practice exam questions on Trust Boundaries, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAA-C03

A manufacturer deploys a vendor-managed monitoring appliance on an EC2 instance in a private subnet. An internal maintenance API and a production database run on separate EC2 instances in other private subnets of the same VPC. Currently, security groups allow all traffic between these instances.

The appliance must submit measurements to the maintenance API over HTTPS on port 8443. The same API listener also exposes administrative operations that the appliance must never perform. The appliance must not establish direct connections to the production database, even if the appliance is compromised. Other clients must retain their authorized API access. The vendor supports application credentials, and API code changes are permitted.

Which solution meets these requirements?

Show answerCORRECT ANSWER

Replace the broad security group rules with rules that allow the appliance to reach only the maintenance API on port 8443 and allow database ingress only from approved database clients. Require the API to authenticate an appliance-specific credential and authorize it only for measurement submission.

Scoped security group rules enforce the network boundary and prevent direct appliance-to-database connections. Authentication and operation-level authorization enforce a separate boundary within the API, where measurement submission and administrative operations share the same network listener. Existing authorized clients can retain their required rules and permissions.

SAP-C03

A healthcare data exchange exposes a private Amazon API Gateway REST API to approved analytics partners through interface VPC endpoints. Each partner signs requests with a distinct IAM role. API resource policies restrict access to approved partner roles and VPC endpoints. All connections use TLS.

Partners request exports by submitting a customer ID. A shared backend uses an execution role that can read every customer's Amazon S3 prefix. Each partner is authorized to access a different, overlapping subset of customers. These entitlements change independently of network connectivity. Customer IDs are not secrets.

During a threat-modeling review, the security team considers an attacker who has compromised an approved partner's application and signing credentials. Compliance requires the exchange to prevent this attacker from exporting records for customers outside that partner's current entitlements.

Which architectural change best addresses this risk?

Show answerCORRECT ANSWER

Require the backend to resolve the authenticated IAM caller to a partner identity and check the requested customer against a server-controlled entitlement store before creating an export. Bind the export job to that authorized customer and use an S3 session policy restricted to that customer's prefix when reading the records.

This reassesses authorization as an authenticated external request becomes a privileged data-access operation. Server-controlled entitlements prevent the partner from choosing its own authority, and binding the job to the authorized customer preserves that decision during processing. A customer-scoped session policy further limits the export worker's effective S3 permissions.

ANS-C01

A company provides a proprietary TCP service on port 8443 from EC2 instances in a provider VPC. Several customers must access this service privately from their own VPCs in the same AWS Region. Some customer VPC CIDR blocks overlap with the provider VPC CIDR block. A threat model assumes that a customer workload could be compromised. The design must expose only the designated service, prevent customers from gaining general routed connectivity to the provider network, and let the provider approve each customer's connection. Customers cannot renumber their networks, and the company will not deploy address-translation appliances or application-protocol adapters. Which solution best meets these requirements?

Show answerCORRECT ANSWER

Place the service behind a dedicated internal Network Load Balancer and publish a VPC endpoint service. Allow approved customer principals and require endpoint acceptance. Have customers create interface VPC endpoints, and restrict endpoint and provider-side security groups to the required service traffic.

AWS PrivateLink exposes the designated service without establishing general routed connectivity between the VPCs and supports overlapping CIDR blocks. Endpoint-service permissions and acceptance let the provider approve connections, while security groups restrict traffic to the required service path. Connection approval does not replace application authentication and authorization.

Practice Trust Boundaries in a full exam

Questions on Trust Boundaries in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Trust Boundaries

3 min read

A trust boundary separates components that operate under different security assumptions, administrative control, or exposure to threats. Crossing that boundary requires explicit checks appropriate to the interaction. Boundaries can exist between the internet and an application, between application tiers, between cloud accounts, between tenants, or between a workload and a managed service. They are logical security distinctions, not necessarily physical network edges.

Start by drawing the application's data flows and identifying entry points, sensitive assets, identities, and administrative owners. Mark each place where input or authority moves into a different trust context. For each crossing, ask what an attacker could impersonate, modify, disclose, replay, or disrupt. Then select controls that address those threats: authentication, authorization, input validation, encryption, traffic filtering, rate limiting, and audit logging. A boundary is meaningful only when the required checks are actually enforced.

In a three-tier web application, the public load balancer accepts untrusted client traffic, application servers process requests, and the database holds sensitive records. Restrict application ingress to the intended load-balancer path and database ingress to the required application sources and ports. Database credentials and permissions must still constrain what the application can do. If an attacker compromises an application server, network reachability alone must not provide unrestricted access to every database or administrative interface.

Different application architectures produce different threat models. A monolith often has fewer network crossings, but a process compromise can expose many functions and secrets. Microservices introduce more service-to-service boundaries, requiring workload authentication and authorization rather than reliance on internal IP addresses. Serverless and event-driven systems add boundaries at API handlers, queues, event publishers, and execution roles; events still need schema validation and tenant-aware authorization. In multitenant applications, shared infrastructure makes application-level tenant isolation essential because network segmentation may not distinguish individual tenants.

Cloud network constructs help enforce boundaries but do not establish trust automatically. Separate subnets without restrictive traffic controls do not provide effective isolation, and a private subnet is not proof that its workloads are trustworthy. Peering or transit connectivity can expand reachable attack surfaces unless routes and filtering preserve intended separation. Security groups provide stateful traffic filtering, while network ACLs provide stateless subnet-level filtering that requires explicit consideration of return traffic. Neither substitutes for application authorization.

Hybrid and cross-account architectures require particular care because connectivity crosses administrative domains. Limit partner access to specific services rather than entire networks where possible. Private connectivity reduces public exposure but does not prove caller identity or authorize a request. Dedicated connectivity also does not inherently provide encryption; for example, AWS Direct Connect does not encrypt traffic by default. When TLS terminates at a proxy, assess whether the next connection needs encryption and ensure the application accepts identity headers only from trusted intermediaries.

More boundaries can reduce lateral movement and contain failures, but they also increase policy complexity, latency, certificate-management work, and troubleshooting effort. Centralized inspection can simplify policy enforcement but creates routing and availability dependencies, including symmetric-routing requirements for stateful inspection. For compliance, document allowed flows, administrative ownership, and required evidence. Test both permitted and denied paths, inspect flow and authorization logs, and revisit the model when architecture changes. The goal is not to label everything inside a perimeter trusted; it is to make each crossing explicit, constrained, and observable.

Learn Trust Boundaries in lessons

3 short lessons on Trust Boundaries in 2 certification courses.

Open the lessons