Chapter 7 · Reading 1 of 6
Following a certificate chain
Security+ SY0-801 · Objectives 1.3
A student types the correct portal address on a new laptop and gets a certificate warning. Their old laptop opens the page without complaint. Why would two machines disagree about the identity of the same service? The difference may lie in what each client already trusts.
Symmetric encryption uses a shared key and suits bulk data. Asymmetric cryptography uses a public and private key pair for operations such as signatures and key establishment. A certificate binds a public key to an identity through an issuer's signature. A relying party builds a path to a configured trust anchor and checks constraints, time validity and revocation information as applicable.
What a signature establishes
A hash detects change when compared with a trusted reference. A digital signature also lets a verifier check that a holder of the signing key approved the signed bytes. Protect private keys in controlled key storage, limit their use and plan for rotation. When a key is exposed, replace it and revoke affected certificates. Expiration alone leaves a window of risk.
Follow a certificate request through issuance
The service owner generates a key pair and submits a certificate signing request containing the public key and requested identity information. The issuer validates the request under its policy. The private key stays under the service owner's control. A self-signed root can act as a trust anchor because administrators configure it as trusted. A newly encountered self-signed certificate carries no such prior agreement. Intermediates allow the root to remain tightly protected while subordinate issuers handle routine issuance.
During validation, check the requested hostname against the certificate's permitted names, the relevant usage constraints, the chain to a configured trust anchor, time validity and applicable revocation policy. A wildcard covering one level of hostnames expands the impact of a single exposed private key. Inventory every service that depends on it before rotation. A successful check on one administrative workstation does not prove that older clients trust the same issuing chain.
Diagnose a renewal that broke sign-in
The portal serves a new leaf certificate, but some devices fail validation. Compare their clocks and trust stores and inspect the chain actually served. A workstation with a cached intermediate may succeed while a newly enrolled device fails. Test with a clean client, verify the full service transaction and record the issuer, serial and expiration in inventory. Treat revocation status as a separate check from renewal.
Read the chain as a set of claims
Write the service name, leaf certificate and issuing authority on separate lines. Beside each claim, identify who signed it and why the client accepts that signer. The trust anchor comes from the client’s configured policy. Receiving a certificate over the connection cannot by itself establish that policy. Compare the two laptops’ clocks, software and trust stores, then determine whether a cached intermediate accounts for the difference. A useful diagnosis identifies which check failed. That precision matters when the next person asks what encryption protects after the connection succeeds.
Inspect the three records, then use the evidence to answer the question.
1. Record A
Portal certificate names portal.example
2. Record B
Leaf expires June 30 and issuer expires June 10
3. Record C
Validation date is June 12 in the same year
Apply the reading
What evidence supports your decision in the certificate path viewer exercise?
Compare your reasoning
A valid leaf date cannot repair an expired issuing certificate. Validate the complete chain, intended use and hostname.