Study guide · Domain 1.0
General Security Concepts
16% of the exam · 3 exam objectives
Domain 1 is the vocabulary of security: the goals controls serve, how controls are grouped and what they do, how change management keeps changes from creating risk, and how to choose the right cryptography for each need.
A study feature written by ExamDragon, not part of the real exam. Each heading is one of this domain's 3 exam objectives, as CompTIA states it in the SY0-801 objectives.
At a glance
Domain 1.0of the exam, as CompTIA weights it for SY0-801
- Weight
- 16%
- Objectives
- 3
- Key terms
- 10
What this guide covers, objective by objective
1.1Explain security concepts and controls.
- Defense in depth layers controls so that one failure does not expose an asset. The core goals those controls serve are confidentiality (only the right people read data), integrity (data is not changed without authorization) and availability (systems work when needed): CIA.
- AAA is authentication (prove who you are), authorization (what you may do) and accounting (a record of what you did).
- Non-repudiation means a person cannot credibly deny an action, usually through digital signatures and reliable logs.
- Zero Trust removes trust based on network location: every request is checked on identity, device state and policy. Least privilege gives each account only the rights its task needs.
- Control categories say how a control is implemented: technical/logical (systems), managerial/administrative (policies, risk assessments), operational (people doing tasks, such as guards and training) and physical/environmental (locks, fences, lighting).
- Control types say what a control does: preventive stops, deterring discourages, detective finds, corrective repairs, compensating stands in for a missing control, directive tells people what to do.
- The situationAn auditor asks you to classify a door badge reader and the policy that says staff must badge in.
- Step 1Ask how each is implemented: the reader is a device on a door, the policy is a written rule.
- Step 2Assign categories: the reader is physical (and technical), the policy is managerial.
- Step 3Ask what each does: the reader stops entry, the policy tells people what to do.
- Step 4Assign types: the reader is preventive, the policy is directive.
- Where questions turnMixing up category and type, for example calling a security guard detective when the question asks for the category (operational), or calling a fence physical when it asks for the type (preventive or deterring).
- The takeawayCategory answers how a control is implemented; type answers what it does. Classify on both axes separately.
1.2Given a scenario, demonstrate the impact of change management processes on security.
- The change advisory board (CAB) runs the approval process. A change needs a named owner who is accountable and identified stakeholders who are affected.
- Impact analysis shows what a change touches and the risk; test results show it worked in testing; both come before approval.
- A backout plan returns systems to the last known good state; failing forward fixes a failed change by moving ahead when reverting is not practical.
- Maintenance windows place downtime, service restarts and application restarts when the fewest people are affected. Standard operating procedures (SOPs) document routine changes.
- Technical implications to check: allow lists and deny lists that may block new software, restricted activities, downtime, restarts, legacy applications and dependencies.
- After the change, update diagrams, policies and procedures, and keep every revision under version control.
- The situationA team wants to upgrade an operating system on a server that runs a legacy application.
- Step 1Name the owner and the stakeholders, and run an impact analysis that lists the legacy application and its dependencies.
- Step 2Test the upgrade with the legacy application and record the results; write a backout plan using a snapshot.
- Step 3Get CAB approval and carry out the upgrade in the maintenance window, checking allow lists and restarts.
- Step 4Update diagrams and procedures, and commit the new configuration to version control.
- Where questions turnTreating backout planning and failing forward as the same thing: backout reverts to the earlier state, failing forward applies a new fix to the changed state.
- The takeawaySecurity problems from changes usually come from a skipped step: an unseen dependency, no way back, or stale documentation.
1.3Explain the importance of using appropriate cryptographic solutions.
- Public key infrastructure (PKI) binds public keys to identities. The private key stays with its owner; the public key is shared. Key escrow keeps copies of keys with a trusted party for recovery.
- A certificate authority (CA) signs certificates; trust flows from a root of trust. Third-party certificates are trusted publicly; self-signed ones are not. A certificate signing request (CSR) carries the public key to the CA. A wildcard certificate covers every subdomain at one level.
- Revocation is checked with a certificate revocation list (CRL), a full list, or the Online Certificate Status Protocol (OCSP), a real-time check of one certificate.
- Symmetric encryption uses one shared key and is fast; asymmetric uses a key pair and helps with key exchange and signatures. Longer keys for the same algorithm resist brute force better.
- Encryption levels for data at rest: full disk, partition, volume, file, database and record. Data in transit needs transport encryption such as TLS or IPSec.
- Digital signatures use the signer's private key and are verified with the public key. Hashing gives a fixed-length digest that reveals change; salting makes identical passwords hash differently. Obfuscation only makes data harder to read.
- The situationA web shop needs to protect card details typed by customers and the database where orders are stored.
- Step 1For data in transit, use TLS with a certificate from a third-party CA so browsers trust it.
- Step 2Generate the key pair on the server and send a CSR; the private key never leaves the server.
- Step 3For data at rest, use database or record encryption for the order data, and full disk encryption on the server.
- Step 4Store customer passwords as salted hashes, not with reversible encryption.
- Where questions turnConfusing which key signs and which key encrypts: you sign with your own private key, and you encrypt for someone with their public key.
- The takeawayPick the cryptography by the state of the data and the goal: confidentiality in transit, at rest, integrity, or proof of origin.
Key terms
- CIA
- Confidentiality, Integrity, and Availability
- AAA
- Authentication, Authorization, and Accounting
- CAB
- Change Advisory Board
- SOP
- Standard Operating Procedure
- PKI
- Public Key Infrastructure
- CSR
- Certificate Signing Request
- CRL
- Certificate Revocation List
- OCSP
- Online Certificate Status Protocol
- TLS
- Transport Layer Security
- IPSec
- Internet Protocol Security
Show the answer
The log review is a compensating control, because it stands in for the missing one. A backout plan records how to undo a change.
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.
