Security+ acronyms grouped by exam domain
Learn them by domain, not alphabetically
Security+ questions reuse about a hundred acronyms, and the exam rarely spells them out. The practical way to learn them is to attach each one to the domain where it is used, because the domain tells you the context the question is set in. This guide groups the acronyms that appear in the SY0-801 objectives by the five domains. The decision rule: when two acronyms look alike, work out which stage of the work each belongs to (finding, scoring, fixing, reporting) before reading the options.
Two notes on sources. CompTIA’s objectives name the acronyms but do not define them, so the expansions below are the standard industry meanings, explained in this guide’s own words. And the V8 objectives (SY0-801) are the reference here. V8 launches on November 17, 2026, and until then the live exam is SY0-701, which overlaps heavily but is not identical. Check the SY0-801 vs SY0-701 comparison if you are booked before the switch.
Domain 1: general security concepts (16%)
| Acronym | Meaning | Memory hook |
|---|---|---|
| CIA | Confidentiality, integrity, availability | What every control protects |
| AAA | Authentication, authorization, accounting | Prove who, allow what, record it; see AAA explained |
| CAB | Change advisory board | The group that approves changes |
| SOP | Standard operating procedure | The written routine |
| PKI | Public key infrastructure | CAs, certificates and keys together |
| CRL / OCSP | Certificate revocation list / Online Certificate Status Protocol | A downloaded list versus a live per-certificate query |
| CSR | Certificate signing request | What you send a CA to get a certificate |
CRL and OCSP are the classic pair: both answer “is this certificate still valid?”, but a CRL is a published list the client downloads, while OCSP asks about one certificate. Cryptography basics covers the surrounding material.
Domain 2: threats, vulnerabilities and attacks (24%)
| Acronym | Meaning | Stage |
|---|---|---|
| APT | Advanced persistent threat | A patient, well-resourced actor |
| IoC | Indicator of compromise | Evidence an attack happened |
| DoS / DDoS | Denial of service / distributed denial of service | One source versus many |
| CVE | Common Vulnerabilities and Exposures | An ID for one specific flaw |
| CWE | Common Weakness Enumeration | A category of weakness, such as a coding error type |
| CVSS | Common Vulnerability Scoring System | A severity score |
| NVD | National Vulnerability Database | The national vulnerability database run by NIST |
| TOC / TOU | Time of check / time of use | The two moments in a race condition |
| LLM | Large language model | Appears in attack surface and AI threat objectives |
| OT / IoT | Operational technology / Internet of Things | Industrial systems versus connected devices |
The trio CVE, CWE and CVSS is worth saying aloud: the CVE is the flaw, the CWE is the kind of mistake behind it, and the CVSS is how bad it is. Vulnerability management and CVSS goes further, and common attack types covers the attacks themselves.
Domain 3: security architecture (19%)
| Acronym | Meaning | Note |
|---|---|---|
| IaC | Infrastructure as code | Infrastructure defined in files |
| SSE | Security Service Edge | Cloud-delivered security services for remote access |
| gMSA | Group managed service account | A service account whose password the directory manages |
| UPS / RPS | Uninterruptible power supply / redundant power supply | Battery versus second supply |
| RTO | Recovery time objective | How long you can be down |
| RPO | Recovery point objective | How much data loss you can accept |
| MTTR / MTBF | Mean time to repair (or recover) / mean time between failures | Repair speed versus reliability |
RTO is a duration of downtime; RPO is a point in time that sets the amount of data loss. Questions give you a backup schedule and ask which one it determines: the schedule fixes RPO, not RTO.
Domain 4: security operations (27%)
| Acronym | Meaning | Note |
|---|---|---|
| SIEM | Security information and event management | Collects and correlates logs |
| SOAR | Security orchestration, automation and response | Runs playbooks on alerts |
| SOC | Security operations center | The team |
| EDR / XDR | Endpoint detection and response / extended detection and response | One layer versus many |
| NIDS / NIPS | Network intrusion detection / prevention system | Alerts versus blocks |
| HIDS / HIPS / WIPS | Host-based and wireless equivalents | Where the sensor sits |
| WAF | Web application firewall | Layer 7 for web traffic |
| UTM | Unified threat management | Several functions in one appliance |
| SPF / DKIM / DMARC | Sender Policy Framework / DomainKeys Identified Mail / Domain-based Message Authentication, Reporting and Conformance | Allowed senders / signature / policy over both |
| MDM | Mobile device management | Controls phones and tablets |
| CSPM | Cloud security posture management | Finds cloud misconfigurations |
| SCAP | Security Content Automation Protocol | Standard way to automate compliance checks |
| MFA / OTP | Multifactor authentication / one-time password | More than one factor |
| SAML / LDAP / OAuth | Federation assertions / directory protocol / delegated authorization | See SSO, SAML and OAuth |
Detection versus prevention is the usual trap: the IDS variants alert, the IPS variants sit inline and block. SIEM vs SOAR vs XDR separates the tooling acronyms, and the incident response lifecycle places them in the process.
Domain 5: program management and oversight (14%)
| Acronym | Meaning | Note |
|---|---|---|
| SLE | Single loss expectancy | Loss from one event |
| ARO | Annualized rate of occurrence | Events per year |
| ALE | Annualized loss expectancy | SLE times ARO |
| BIA | Business impact analysis | What matters most when things stop |
| SLA / SLO | Service-level agreement / objective | The contract versus the target |
| MOU / MOA | Memorandum of understanding / agreement | Intent versus a firmer commitment |
| NDA / MSA / SOW | Non-disclosure agreement / master service agreement / statement of work | Secrecy, framework terms, specific work |
| RFP / RFI / RFQ | Request for proposal / information / quote | Solutions, facts, prices |
| AUP / BYOD | Acceptable use policy / bring your own device | Common policy names |
| BEC | Business email compromise | An impersonation fraud |
Worked example: ALE
A file server is worth 200,000 and a failure would destroy 25% of that value, so SLE = 200,000 x 0.25 = 50,000. If such a failure is expected every two years, ARO = 0.5, and ALE = 50,000 x 0.5 = 25,000 per year. A control that costs less than that yearly figure and removes the risk is economically justified. The method is covered in qualitative vs quantitative risk.
Which exams test this
| Exam | How the topic appears | Where on this site |
|---|---|---|
| SY0-801 | All five domains use these acronyms; the objectives name them throughout. SY0-801 is the reference. V8 launches Nov 17, 2026; SY0-701 is bookable until then | Cheat sheet, domain guides |
| N10-009 | Its own acronym list, which overlaps (DHCP, LACP, DLP, UTM). Minor for this guide | Network security guide |
| CY0-001 | Own list including GRC and SCA. Minor for this guide | GRC guide |
How questions use acronyms
Questions rarely ask “what does X stand for”. They place the acronym in a scenario and offer its look-alikes as distractors. The constraint words are the stage and the scope: “inline” or “blocks” points to prevention, “alerts” to detection; “maximum tolerable data loss” points to RPO, “time to restore service” to RTO; “score” points to CVSS, “identifier” to CVE. When you meet an unknown acronym, expand it letter by letter and ask what job the words describe.
Question 1. A company wants receiving mail servers to reject messages that claim its domain but are not sent by approved servers, and to receive reports about such attempts. Which record type sets that policy by building on SPF and DKIM results?
- A. SPF
- B. DKIM
- C. BIMI
- D. DMARC
Show answer
Answer: D
DMARC lets the domain owner publish a policy for messages that fail SPF or DKIM alignment and request reports. SPF only lists authorized sending servers. DKIM only adds a cryptographic signature to messages. BIMI displays a brand logo in supporting mail clients and does not enforce a policy.
Question 2. Nightly backups run at 02:00. A disk fails at 17:00 and the team restores the 02:00 backup within three hours. Which statement is correct?
- A. The three-hour restore shows the RPO was three hours
- B. The data lost since 02:00 shows the effective RPO was about 15 hours
- C. The result shows the MTBF was 15 hours
- D. The result shows the ALE was three hours
Show answer
Answer: B
Restoring the 02:00 backup loses everything written since then, so the backup schedule produced a data-loss window of 15 hours, which is what an RPO limits. The three hours to restore relate to RTO. MTBF measures time between failures, and ALE is a yearly financial figure, so neither describes this outcome.