Cloud concept · Updated

Chain of Trust - A chain of trust is a sequence of cryptographically verified relationships that connects data or an identity to an explicitly trusted anchor.

In short

Trust is established by validating each link back to a trusted starting point rather than accepting an isolated signature or assertion. In DNSSEC, this connects signed DNS answers through parent-zone delegations to a resolver's trust anchor, helping detect forged or modified DNS responses.

Cloud Concepts Hub →

6 key aspects of Chain of Trust

A reliable chain of trust requires an explicit anchor, authenticated links, complete validation, and coordinated lifecycle changes.

01
Explicit trust anchor

Validation must terminate at a key or credential accepted through a trusted process. For public DNSSEC, recursive resolvers normally use the DNS root trust anchor rather than independently trusting every authoritative zone.

02
Authenticated delegation

A parent-zone DS record binds a child zone to its signing key. Signing a zone without establishing this parent link does not create a continuous public DNSSEC chain.

03
Verification of every required link

Resolvers authenticate DNSKEY records and verify signatures over DNS record sets. An isolated valid signature is insufficient when the signing key cannot be connected to a trusted anchor.

04
Distinct validation outcomes

Secure, insecure, and bogus are different states. An unsigned delegation can resolve successfully as insecure, while a broken signed delegation commonly causes SERVFAIL for validating clients.

05
Coordinated key lifecycle

Key rotation, parent DS updates, and signing shutdown must account for DNS caches and TTLs. Removing a key or disabling signing before the corresponding parent trust information expires can interrupt resolution.

06
Authentication rather than encryption

DNSSEC protects the authenticity and integrity of DNS data, including authenticated negative answers. It does not conceal queries, replace TLS, or establish that an application's behavior is safe.

Cloud services for Chain of Trust

Route 53, AWS KMS, and Route 53 Resolver address different parts of the DNSSEC trust process. Route 53 serves signed public DNS data, while KMS protects the private key supporting the zone's key-signing key. The parent-zone operator publishes the matching DS record to connect that zone to the wider DNS hierarchy. Route 53 Resolver independently validates public answers when DNSSEC validation is enabled for a VPC. In hybrid or multi-account environments, engineers must coordinate parent-child delegation, key access, and the recursive resolution path. Signing, publishing the parent DS, and enabling validation are separate configuration tasks; none substitutes for the others.

Amazon Route 53Amazon Route 53

Signs public hosted zones and publishes the DNSSEC records needed to authenticate their data. Completing the chain requires publishing the zone's DS record in its parent, through the registrar or parent-zone operator.

Chain of Trust exam questions

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

SAP-C03

A financial services company operates internal HTTPS applications behind Application Load Balancers in 12 AWS accounts in one AWS Region. Corporate clients trust only the company's existing offline enterprise root CA. Client trust stores cannot be changed. The security team requires that the root CA remain offline except during controlled signing ceremonies and that issuing CA private keys remain in a managed AWS service. Application teams must obtain account-local certificates with automatic renewal and deployment to their load balancers, without building certificate redistribution workflows.

Which solution meets these requirements with the LEAST operational overhead?

Show answerCORRECT ANSWER

Create a subordinate CA in AWS Private CA in the security account. Have the enterprise root CA sign its CSR, and import the signed CA certificate and chain. Share the subordinate CA with the application accounts through AWS Resource Access Manager. Configure the required issuance permissions, and have each application account request private certificates through ACM and associate them with its load balancers.

The externally signed subordinate preserves the existing enterprise root as the trust anchor while AWS Private CA protects and operates the issuing CA's private key. Sharing the CA allows application accounts to request their own ACM private certificates. Eligible ACM-issued private certificates associated with load balancers receive managed renewal and deployment, provided the CA remains available and the required permissions remain in place.

ANS-C01

A company manages the DNSSEC-signed public zone example.com in a networking AWS account. The zone delegates legacy.example.com to a DNSSEC-signed Route 53 public hosted zone in an application account. The delegation has valid NS and DS records, and the public DNSSEC chain currently validates successfully.

The company must permanently stop signing legacy.example.com while retaining its hosted zone, application records, and existing name servers. Security policy permits the child zone to become unsigned, but example.com must remain signed. Resolution must continue without DNSSEC validation failures for internet clients, including clients whose recursive resolvers have cached delegation records. The company does not control those resolvers.

Which procedure meets these requirements?

Show answerCORRECT ANSWER

Remove the DS record for legacy.example.com from example.com. Confirm that the parent authoritative servers no longer serve it, and wait for previously cached DS records to expire. Then deactivate the child zone's KSK and disable signing for the child hosted zone.

The parent's DS record establishes that the child must validate. Removing it while the child remains correctly signed allows cached DS records to remain usable until they expire. After those cached records expire, validators can authenticate the absence of a DS record and treat the child as an insecure, unsigned delegation. The parent can remain signed, and the existing NS delegation does not need to change.

Practice Chain of Trust in a full exam

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

Start a free practice exam

What is Chain of Trust

3 min read

A chain of trust allows a system to accept information from an unfamiliar source because each relationship leading to that source can be verified. The chain starts at a trust anchor: a public key or other credential accepted through a trusted process outside the chain itself. Every subsequent link must satisfy the relevant cryptographic and policy checks. Cloud engineers encounter this pattern in DNSSEC, TLS certificate validation, software signing, and verified boot, although each uses different records and validation rules.

For DNSSEC, a validating recursive resolver normally starts with a DNS root trust anchor. The root zone authenticates the delegation signer, or DS, record for a signed top-level domain. That domain authenticates the DS record for a signed child zone, such as example.com. Each DS record identifies a child-zone signing key through a cryptographic digest of its DNSKEY record. The resolver checks this relationship, validates the child zone's DNSKEY record set, and then uses authenticated keys to verify signatures over the requested DNS record set.

DNSSEC uses DNSKEY records to publish public keys and RRSIG records to carry signatures. In the common split-key model, a key-signing key, or KSK, signs the DNSKEY record set, while a zone-signing key, or ZSK, signs other authoritative record sets. NSEC or NSEC3 records provide authenticated denial of existence. Simply publishing a DNSKEY or signing records does not establish a publicly verifiable chain: the parent must publish the correct DS record, and the resolver must perform validation.

For example, when enabling DNSSEC signing for a public hosted zone, first establish signing and confirm that the zone serves the expected DNSKEY and signatures. Then publish the corresponding DS record through the registrar or the operator of the parent zone. For a delegated subdomain owned by another account, publish its DS record in the parent zone. Account boundaries do not change the DNSSEC hierarchy; parent and child operators must coordinate the delegation.

Amazon Route 53 illustrates the separation between signing and validation. It can sign public hosted zones, using a customer-managed asymmetric AWS KMS key for the KSK while managing the ZSK itself. The KMS key must be in US East (N. Virginia), use ECC_NIST_P256, and have SIGN_VERIFY usage. Separately, Route 53 Resolver can validate DNSSEC for public DNS lookups from a VPC when validation is enabled. Public hosted-zone signing does not enable resolver validation, and Route 53 private hosted zones do not support DNSSEC signing.

A validating resolver distinguishes secure answers, insecure answers without an authenticated signed delegation, and bogus answers that fail required validation. A missing DS record generally leaves the child insecure rather than proving that it is signed. By contrast, a stale DS record pointing to a retired key can make an otherwise reachable domain bogus, commonly producing SERVFAIL. During troubleshooting, inspect the parent DS, child DNSKEY, signatures, signature validity periods, and resolver behavior rather than assuming that a DNS timeout or SERVFAIL means the authoritative server is unavailable.

The main trade-offs are operational complexity, larger DNS responses, and stricter failure behavior. Key rollovers and disabling signing require carefully ordered changes that account for TTLs and cached data. Hybrid forwarding and centralized multi-account DNS also require identifying which resolver validates each query path; forwarding alone does not establish trust. DNSSEC authenticates DNS data and detects unauthorized modification, but it does not encrypt queries, guarantee availability, or prove that the destination application is trustworthy. HTTPS remains necessary for transport confidentiality and server authentication.

Learn Chain of Trust in lessons

1 short lesson on Chain of Trust in 1 certification course.

Open the lessons