General Security Concepts: what Security+ tests and how to prepare
The vocabulary domain. It defines the control types, security principles and change-management ideas the other four domains assume you already know, which is why weak scores here tend to drag everything else down.
The list below follows the published exam objectives for SY0-701. Depth matters more than breadth here: the exam asks you to apply these ideas to a scenario, not to recite them.
Control categories — technical, managerial, operational, physical — and control types such as preventive, detective, corrective and compensating.
The CIA triad, non-repudiation, authentication, authorisation and accounting, and gap analysis.
Zero trust as a model: control plane and data plane, policy engine, policy administrator and policy enforcement point.
Physical security measures and deception technology such as honeypots and honeytokens.
Change management as a security process, and the cryptographic building blocks: PKI, encryption levels, key exchange, hashing, digital signatures and certificates.
Common mistakes
Where candidates lose marks
Confusing control category with control type. A question asks for both, and a firewall can be technical and preventive at once — the exam expects you to keep the two axes separate.
Treating compensating controls as a synonym for "backup plan". A compensating control exists because the primary control is not feasible, and the exam tests that distinction directly.
Reciting the zero trust components without knowing which one makes the decision and which one enforces it.
Study this domain first even though it looks like the easiest. Every scenario in Security Operations and Security Architecture is built on this vocabulary, and candidates who skim it here pay for it repeatedly later.
Try three questions. Understand every answer.
Original English practice examples, with answers and explanations available here. No account required. These are independent teaching examples, not official exam questions or exam dumps.
Question 1 of 3 · Threats, vulnerabilities, and mitigations
Answer and explanation
Best answer: Validate and apply the workaround, monitor it, and track the pending patch
A validated compensating control can reduce exposure while the permanent fix is pending. Retain the vulnerability record, residual risk, and a plan to apply and verify the patch.
Why the other choices fit less well
Waiting leaves exposure unchanged, and a hostname change does not block the flaw. A workaround reduces risk without necessarily removing the vulnerability, so closing it as permanently fixed overstates the evidence.
Best answer: Grant approved read-only access to that dataset with a reviewed expiry
Limit permissions to the approved task, resource and duration. Review the expiry and record the grant so access can be removed when the investigation ends.
Why the other choices fit less well
Permanent administrator rights exceed the task. Shared credentials weaken individual accountability. Disabling logs removes evidence without reducing the permissions required.
Best answer: Preserve both records and investigate or repeat the transfer before relying on the copy
The received bytes have not passed the expected integrity check. Preserve the acquisition record and investigate the discrepancy or acquire a verified copy.
Why the other choices fit less well
A filename does not establish byte-level integrity. Replacing the original hash hides the discrepancy. Do not describe the copy as verified until the mismatch is resolved.
Paid question-bank access is a one-time purchase, with no recurring subscription. Official exam registration, vouchers and provider labs are separate from CertSprint practice.
Find out if this domain is your weak one
20 free Security+ questions, no card required. Readiness is reported per domain, so you can see whether General Security Concepts is where your revision should go.
