CompTIA Security+ ExamStudy Topic

Security Architecture and Trust Boundaries Study Guide

Understand access control, cryptographic purposes, segmentation, secure defaults, and resilient dependencies.

Topic Overview

Draw where identity is established, authorization is evaluated, information moves, and cryptographic keys are used. A successful login does not authorize every action. Network location alone should not substitute for the relevant trust decision.

Match cryptographic tools to objectives. Encryption protects confidentiality within its scope. A signature supports integrity and association with a signing key under appropriate trust assumptions. A hash comparison establishes consistency with its reference, so the reference provenance matters. Key recovery must survive the failures the architecture plans for.

Review common dependencies in resilience designs. Two servers may still depend on one switch or one key store. Segmentation should define and enforce permitted flows, and secure defaults should expose only needed features. Assess deployed configuration as well as the design document.

Common Mistakes to Avoid
  • Treating a valid signature as proof that all signed content is harmless or true.
  • Assuming at-rest encryption protects every network transmission.
  • Counting redundant servers without examining shared failure domains.
  • Granting implicit trust based only on an internal network address.

Checkpoint Quiz

Test your understanding of Security Architecture and Trust Boundaries

These questions are for study practice only and are not official exam questions.

  1. 1. A downloaded file matches a published cryptographic hash, but both file and hash were obtained from the same untrusted attacker-controlled location. What limitation remains?

  2. 2. An organization assigns permissions to job roles such as payroll clerk and auditor, then assigns users to those roles. Which access-control model is illustrated?

  3. 3. A system denies access when an authorization service is unavailable because its documented requirement favors confidentiality over immediate access. What behavior is this?

  4. 4. A platform verifies approved boot components before executing them. Which objective is this control most directly intended to support?

  5. 5. An application uses a certificate whose chain is valid, but the requested server name does not match the identity in the certificate. Why is this significant?

  6. 6. A team uses infrastructure as code and wants to detect unauthorized configuration changes over time. Which comparison is useful?

  7. 7. A password-storage system assigns each password a unique random salt before using an appropriate password-hashing function. What benefit does the salt provide?

  8. 8. A database operator needs read access to one reporting dataset for a temporary assignment. Which grant best follows least privilege?

  9. 9. A design says that being connected to the office network is not sufficient reason to trust an access request. Identity, device state, and authorization must still be evaluated. Which principle is reflected?

  10. 10. Two redundant servers share the same power supply and network switch. What resilience concern remains?

Start Full Practice Test
Study GuideRead the full guide for the CompTIA Security+ ExamPractice TestTake a free, timed practice testFull Exam PrepAll topics, tests, and state pages

Frequently asked questions

Does hashing authenticate a file author?

A hash alone does not establish identity. A trusted reference or appropriate signature and identity validation is needed for stronger provenance.

What does least privilege include?

Limit the resource, allowed operation, and duration to the approved need, then review or remove access when that need changes.

Why does segmentation matter?

It constrains allowed communication across zones and can limit exposure or movement when one component is compromised.

What is a shared failure domain?

It is a dependency or event that can affect multiple supposedly redundant components, such as shared power, networking, storage, or recovery keys.