Study guide · Domain 3.0
Security Architecture
19% of the exam · 4 exam objectives
Security Architecture (19% of the exam) covers how architecture models change security, how to arrange infrastructure and access to protect it, how to protect data in every state and role, and how resilience and recovery keep services running.
A study feature written by ExamDragon, not part of the real exam. Each heading is one of this domain's 4 exam objectives, as CompTIA states it in the SY0-801 objectives.
At a glance
Domain 3.0of the exam, as CompTIA weights it for SY0-801
- Weight
- 19%
- Objectives
- 4
- Key terms
- 10
What this guide covers, objective by objective
- 3.1Compare and contrast security implications of different architecture models.
- 3.2Given a scenario, manage the security architecture to best protect the infrastructure.
- 3.3Summarize concepts and strategies used to protect data.
- 3.4Explain the importance of resilience and recovery in security architecture.
3.1Compare and contrast security implications of different architecture models.
- Cloud deployment models: public (any customer), private (one organization), community (a group with shared needs) and hybrid (a mix). Multicloud means using more than one provider; serverless leaves servers to the provider while the customer still secures code, data and permissions.
- Infrastructure as Code (IaC) defines infrastructure in reviewed, versioned files, so environments are consistent, drift is reduced and rebuilding is faster.
- Operational technology (OT) runs physical processes: availability and safety come first, systems are long lived and patches are tested and scheduled with operators.
- Segmentation: logical segmentation (such as VLANs) separates traffic by configuration on shared equipment; physical segmentation uses separate equipment; an air-gapped network has no connection at all.
- Microservices split an application into small services that talk over the network: independent scaling, but more interfaces to authenticate and monitor. On-premises infrastructure keeps every layer, and every responsibility, with the organization.
- Technical considerations: availability, resilience, proprietary vs. open source, usability, responsibility, compute, power requirements and ease of recovery.
- Business considerations: data sovereignty (the law where data is stored applies), data classification, cost, ownership, environmental requirements, scalability and risk.
- The situationA company wants to move a customer portal to the cloud but must keep customer records in its home country.
- Step 1Name the constraint: the law of the country where data is stored applies, which is data sovereignty.
- Step 2Limit provider and region choices to ones that keep the data in that country.
- Step 3Check responsibility: under the chosen model, list what the provider secures and what the company still secures.
- Where questions turnTreating multicloud and hybrid as the same thing. Hybrid mixes deployment models (such as private and public); multicloud uses more than one provider.
- The takeawayBusiness considerations such as sovereignty can rule out an architecture before any technical comparison begins.
3.2Given a scenario, manage the security architecture to best protect the infrastructure.
- Infrastructure considerations: device placement follows security zones (for example a screened subnet for public servers), keep the attack surface small, and use diversity so one flaw does not affect every layer.
- Zero Trust architecture never trusts network location: every request is checked against user authentication, device management (health and inventory) and application access control.
- Secure communication and access: VPNs and tunneling protect remote access over untrusted networks; end-to-end encrypted messaging, secure file transfer and out-of-band management (a separate path for administering devices) each protect a specific need.
- Security Service Edge (SSE) delivers security services such as web filtering, cloud access security and zero trust network access from the cloud, close to users.
- User management and access follow least privilege: only the access the current role needs, reviewed regularly.
- Identity management: Group Managed Service Accounts (gMSAs) have passwords the domain generates and rotates; least privilege access accounts separate daily work from admin work; privilege creep is access that builds up as people change roles.
- Failure modes: fail closed blocks traffic when a control fails (security first); fail open lets traffic pass (availability first).
- The situationA user with valid multifactor sign-in connects from a laptop with antivirus out of date and asks for the finance application.
- Step 1Check the user: authenticated, so one signal passes.
- Step 2Check the device: health fails, so trust is not granted.
- Step 3Apply application access control: deny or limit access until the device is fixed.
- Where questions turnChoosing a control because the device or user is 'inside the network'. Zero Trust gives no trust for location, and a screened subnet is for public facing systems, not internal ones.
- The takeawayIn Zero Trust every signal counts; passing one check never grants access by itself.
3.3Summarize concepts and strategies used to protect data.
- Data types: structured data fits a fixed schema (tables); unstructured data does not (email, documents, images). Data states: at rest (stored), in transit (moving), in use (being processed).
- Classifications include public, sensitive, confidential, restricted, critical, secret and top secret; the label decides the protection.
- Methods: encryption (reversible with a key), hashing (one way), masking (partial display), tokenization (stand-in value, real value in a vault), filtering, data transpose, deidentification (identifiers removed) and obfuscation (made hard to read).
- Roles: the data owner is accountable and decides classification and access; the custodian implements controls; the steward looks after quality and use; the operator works with the data; the controller decides why and how personal data is processed; a subprocessor is a third party engaged by a processor.
- Handling: protect endpoints, mark and label data, use geofencing to tie access to a place, and control data location and placement.
- Life cycle: creation, management, distribution, retention, disposal. Compliance areas: standards, health data, personal information, financial, child or minor data, intellectual property and legal data.
- The situationA call centre needs to confirm card holders, and the payment system must not hold real card numbers.
- Step 1Agents need to see part of the number: use masking to show the last four digits.
- Step 2The payment system needs to refer to cards without holding them: use tokenization, with numbers in a vault.
- Step 3Card data at rest in the vault stays encrypted.
- Where questions turnMixing up hashing and encryption. Hashing cannot be reversed; encryption can be with the key. Also mixing owner and custodian: the owner decides, the custodian carries out.
- The takeawayPick the method from the need: partial view, stand-in value, one-way check or reversible secrecy.
3.4Explain the importance of resilience and recovery in security architecture.
- Sites: hot (ready with current data, fastest, costliest), warm (equipment ready, data to load), cold (space and power only, slowest). Environmental factors such as location and climate matter in choosing them.
- Platform diversity (vendor platform, hardware, virtualization) stops one flaw or failure from taking everything down.
- Redundancy: load balancing spreads requests, clustering lets servers share work or take over, autoscaling adds and removes capacity, high availability removes single points of failure, and multicloud systems spread risk across providers.
- Power: a UPS bridges short outages until a generator starts; a redundant power supply protects against a failed supply unit; a surge protector guards against spikes.
- Backups need the right retention, immutability (cannot be altered for a set period), scope and regular restoration testing. Testing a recovery plan ranges from simulation to parallel processing to full failover.
- Disaster recovery restores IT after a disruption; business continuity keeps the business running; capacity planning makes sure people, technology and infrastructure can meet demand.
- Metrics: RTO (how long service may be down), RPO (how much data may be lost), MTTR (average repair time), MTBF (average time between failures).
- The situationThe business says a system may be down for at most four hours and may lose at most one hour of data.
- Step 1Four hours is the RTO, so the recovery site and procedure must restore service within it.
- Step 2One hour is the RPO, so backups or replication must run at least hourly.
- Step 3Prove both with a test, such as parallel processing or a failover, and a restoration test.
- Where questions turnSwapping RTO and RPO. RTO is about time down; RPO is about data lost, measured back from the failure.
- The takeawayRTO drives the site and process; RPO drives how often data is copied.
Key terms
- IaC
- Infrastructure as Code
- OT
- Operational Technology
- VPN
- Virtual Private Network
- SSE
- Security Service Edge
- gMSA
- Group Managed Service Account
- UPS
- Uninterruptible Power Supply
- RTO
- Recovery Time Objective
- RPO
- Recovery Point Objective
- MTTR
- Mean Time to Repair
- MTBF
- Mean Time Between Failures
Show the answer
The RPO is 30 minutes and the RTO is 15 minutes. A 15 minute RTO calls for a hot site, since a warm site needs data loaded and a cold site needs equipment installed.
Built to CompTIA's Security+ SY0-801 V8 exam objectives. The explanations, worked examples and traps are ExamDragon's own. Every source this path is built on.
