Security+ acronyms grouped by exam domain

Updated October 9, 2026

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%)

AcronymMeaningMemory hook
CIAConfidentiality, integrity, availabilityWhat every control protects
AAAAuthentication, authorization, accountingProve who, allow what, record it; see AAA explained
CABChange advisory boardThe group that approves changes
SOPStandard operating procedureThe written routine
PKIPublic key infrastructureCAs, certificates and keys together
CRL / OCSPCertificate revocation list / Online Certificate Status ProtocolA downloaded list versus a live per-certificate query
CSRCertificate signing requestWhat 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%)

AcronymMeaningStage
APTAdvanced persistent threatA patient, well-resourced actor
IoCIndicator of compromiseEvidence an attack happened
DoS / DDoSDenial of service / distributed denial of serviceOne source versus many
CVECommon Vulnerabilities and ExposuresAn ID for one specific flaw
CWECommon Weakness EnumerationA category of weakness, such as a coding error type
CVSSCommon Vulnerability Scoring SystemA severity score
NVDNational Vulnerability DatabaseThe national vulnerability database run by NIST
TOC / TOUTime of check / time of useThe two moments in a race condition
LLMLarge language modelAppears in attack surface and AI threat objectives
OT / IoTOperational technology / Internet of ThingsIndustrial 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%)

AcronymMeaningNote
IaCInfrastructure as codeInfrastructure defined in files
SSESecurity Service EdgeCloud-delivered security services for remote access
gMSAGroup managed service accountA service account whose password the directory manages
UPS / RPSUninterruptible power supply / redundant power supplyBattery versus second supply
RTORecovery time objectiveHow long you can be down
RPORecovery point objectiveHow much data loss you can accept
MTTR / MTBFMean time to repair (or recover) / mean time between failuresRepair 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%)

AcronymMeaningNote
SIEMSecurity information and event managementCollects and correlates logs
SOARSecurity orchestration, automation and responseRuns playbooks on alerts
SOCSecurity operations centerThe team
EDR / XDREndpoint detection and response / extended detection and responseOne layer versus many
NIDS / NIPSNetwork intrusion detection / prevention systemAlerts versus blocks
HIDS / HIPS / WIPSHost-based and wireless equivalentsWhere the sensor sits
WAFWeb application firewallLayer 7 for web traffic
UTMUnified threat managementSeveral functions in one appliance
SPF / DKIM / DMARCSender Policy Framework / DomainKeys Identified Mail / Domain-based Message Authentication, Reporting and ConformanceAllowed senders / signature / policy over both
MDMMobile device managementControls phones and tablets
CSPMCloud security posture managementFinds cloud misconfigurations
SCAPSecurity Content Automation ProtocolStandard way to automate compliance checks
MFA / OTPMultifactor authentication / one-time passwordMore than one factor
SAML / LDAP / OAuthFederation assertions / directory protocol / delegated authorizationSee 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%)

AcronymMeaningNote
SLESingle loss expectancyLoss from one event
AROAnnualized rate of occurrenceEvents per year
ALEAnnualized loss expectancySLE times ARO
BIABusiness impact analysisWhat matters most when things stop
SLA / SLOService-level agreement / objectiveThe contract versus the target
MOU / MOAMemorandum of understanding / agreementIntent versus a firmer commitment
NDA / MSA / SOWNon-disclosure agreement / master service agreement / statement of workSecrecy, framework terms, specific work
RFP / RFI / RFQRequest for proposal / information / quoteSolutions, facts, prices
AUP / BYODAcceptable use policy / bring your own deviceCommon policy names
BECBusiness email compromiseAn 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

ExamHow the topic appearsWhere on this site
SY0-801All 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 thenCheat sheet, domain guides
N10-009Its own acronym list, which overlaps (DHCP, LACP, DLP, UTM). Minor for this guideNetwork security guide
CY0-001Own list including GRC and SCA. Minor for this guideGRC 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.

Go deeper