Help Desk to Security

Study guide · Domain 1.0 · 12% of the exam

General Security Concepts: the SY0-701 objectives in plain English

Domain 1 is the foundation of CompTIA Security+. It covers the language of security controls, core ideas like the CIA triad and Zero Trust, how changes are managed safely, and how cryptography protects data. At 12 percent of the exam, it is not the largest domain, but its vocabulary appears in questions everywhere else, so learning it first makes the rest of the exam easier to read, whether the topic is a firewall rule, a certificate warning, or a change ticket that went sideways overnight.

1.0

What the objectives cover

1.1 Compare and contrast various types of security controls.

Security controls fall into four categories. Technical controls run in systems, like firewalls and encryption. Managerial controls are oversight, like policies and risk assessments. Operational controls are day to day work by people, like account reviews. Physical controls protect places, like locks and cameras. Controls also have types. A preventive control stops an event, like blocking a malicious connection. A deterrent discourages attempts, like a warning banner. A detective control finds events, like a SIEM alert. A corrective control restores systems, like rebuilding after infection. A compensating control substitutes when the main control cannot work. A directive control tells people what to do, like a policy.

1.2 Summarize fundamental security concepts.

You will use these ideas in every other domain. The CIA triad means protecting confidentiality, integrity, and availability. Non-repudiation means a person cannot credibly deny an action, often because it was signed or logged. AAA covers authentication, who you are, authorization, what you can access, and accounting, a record of what you did. Zero Trust assumes no user or device is trusted by default. Its policy engine makes access decisions, the policy administrator sets up the session, and the policy enforcement point allows or blocks traffic. Physical security uses bollards, fencing, and sensors. Deception tools include honeypots, honeynets, honeyfiles, and honeytokens that lure attackers.

1.3 Explain the importance of change management processes and the impact to security.

Change management keeps a helpful fix from becoming an outage or a security hole. Every change needs an approval process, a clear owner who is responsible for it, and input from stakeholders who will be affected. Impact analysis asks what could break, who uses the system, and what security controls change. You record test results before release, prepare a backout plan to undo the change, and schedule work inside a maintenance window. Good documentation explains what changed and why, and version control tracks which version is current so you can prove it later during an audit or incident review and show who approved it.

1.4 Explain the importance of using appropriate cryptographic solutions.

Cryptography protects data when other controls fail. Public key infrastructure uses certificate authorities to issue certificates after you submit a certificate signing request. A wildcard certificate covers subdomains, and trust starts at a root of trust. Encryption works at full-disk, partition, file, volume, database, and record levels, plus in transport. Key exchange lets strangers share secrets safely, and longer keys are harder to brute force. Hashing creates a fingerprint, salting adds random data before hashing passwords, and key stretching makes guessing slower. Digital signatures prove origin and integrity. Blockchain links records so changes show. Key escrow and management control recovery, while TPM and HSM hardware protect keys.

EX

Worked example

Domain 1: General Security ConceptsControl categories1-01

A network engineer configures a firewall to block all outbound connections to a list of known malicious IP addresses before any connection is established. Which control category does this BEST represent?

Correct answer: B. Preventive

A preventive control stops an unwanted event before it happens. Blocking the connection attempt in advance prevents the traffic from ever reaching the malicious destination.

Why the other options are wrong

AZ

Acronyms in this domain

AcronymWhat it means
AAAAuthentication, Authorization, and Accounting framework for access control
CIAConfidentiality, Integrity, and Availability, the core security triad
PKIPublic Key Infrastructure, the system for digital certificates
CACertificate Authority, the trusted issuer of digital certificates
CSRCertificate Signing Request, sent to a CA for a certificate
CRLCertificate Revocation List, the list of invalid certificates
OCSPOnline Certificate Status Protocol, used to check certificate status
TPMTrusted Platform Module, a chip that stores cryptographic keys
HSMHardware Security Module, a device that protects cryptographic keys
AESAdvanced Encryption Standard, a symmetric encryption algorithm
SHASecure Hash Algorithm, a family of hashing functions
PEPPolicy Enforcement Point, the point that allows or blocks access
MFAMultifactor Authentication, sign in using two or more factor types
FDEFull Disk Encryption, encryption that covers an entire drive
HD

Where the help desk meets this domain

You already work with Domain 1 controls every shift, even if nobody labels them that way. When you reset a password and verify a caller identity, you are handling authentication, the first part of AAA in objective 1.2. When you check whether a user should have access to a shared folder before granting it, that is authorization. When you log the ticket, the time, and what you changed, that is accounting, and it also supports non-repudiation because the record shows who did what. Enrolling users in MFA, handing out hardware tokens, and helping them approve sign in prompts are daily examples of preventive technical controls from objective 1.1. So are the warning banners users see at login, which are deterrent and directive at the same time. If you work in an office, you also see physical controls from objective 1.2 every day: badges, cameras, locked server rooms, visitor sign in sheets, and the bollards outside the building. Recognizing the exam term for work you already do makes the questions feel less abstract, and it gives you a concrete story to attach to each definition when you study at night after a long shift. You see the same pattern when you disable an account for a departing employee the moment HR notifies you, because that quick action protects confidentiality and availability at the same time.

Change and cryptography show up at the help desk too. Objective 1.3 is the reason you cannot just reboot a production server or push a patch without a ticket: the change needs an owner, approval, testing, and a backout plan in case it breaks something. When a change goes wrong, the help desk is usually the first place users call, and good documentation and version control are what let you answer what changed, when it changed, and who approved it. Objective 1.4 appears when you set up BitLocker or another full disk encryption tool on a laptop, install a certificate so a user can reach a secure site, or explain why a browser warns about an expired certificate. You may also reimage machines, restore files from backup, unlock encrypted drives, and check TPM status during setup. Those tasks map directly to corrective controls, key management, and hardware backed key storage. For the exam, practice translating your tickets into this vocabulary: name the control category, the control type, and the objective behind each task you handled that week, and Domain 1 questions become pattern matching instead of memorization. That habit also helps in interviews, because you can explain your daily work using the same terms a security team uses. Over a few weeks, that list becomes a personal review sheet built from real work, which is easier to remember than a glossary.

!

Traps to watch for

The most common trap in Domain 1 is timing. A control that alerts after something happens is detective even if the alert is instant. A SIEM that fires in one second, a camera that notifies you the moment motion is seen, and an account lockout message sent right after failed logins all report events that already occurred. They do not stop the event, so they are not preventive. Preventive means the action is blocked before it succeeds, like a firewall dropping a connection or MFA stopping a sign in with a stolen password. Read the verb in the question: block, deny, and prevent point one way, while alert, log, detect, and record point the other. The exam also mixes categories and types on purpose, so a firewall is a technical control by category and a preventive control by type, and a question will specify which view it wants only in the wording of the stem or the answer choices. Questions love to describe speed, detail, or automation to push you toward preventive, but none of that changes the order of events.

Two more traps catch experienced techs. First, compensating controls only count when the primary control cannot be implemented. Extra monitoring around a system that could easily use MFA is not a compensating control, it is just extra monitoring. The question must show a real limit, like a legacy application that cannot support MFA, and a substitute that reduces the same risk, such as a hardened jump host with session recording and restricted source addresses. Second, Zero Trust is an architecture approach, not a product you buy. A vendor tool can act as a policy enforcement point, but no single purchase gives you Zero Trust. The model is about verifying identity and context for every access decision, using a policy engine to decide and a policy administrator to set up the connection, and assuming the network is already hostile. If an answer choice treats Zero Trust as a box, a license, or a single feature you turn on, it is wrong, no matter how confident the wording sounds.

Now try it. The 5 free sample questions for Domain 1 are in practice mode, with full explanations.

Practice Domain 1 questions
All guidesDomain 2 guide