Threat & Vulnerability Characteristics

Security+ SY0-801 · Threats, Vulnerabilities, and Attacks

By Abu Anns · Last updated 20 November 2026Exam version: SY0-801

Threats, vulnerabilities, and risk: the three terms

Objective 2.1 is new in SY0-801, and it tests the vocabulary that the rest of Domain 2 is built on. A threat is anything that could cause harm to an organization: a person, a group, an event, or a circumstance with the potential to exploit a weakness. A vulnerability is a weakness in a system, a process, or a person that a threat could exploit. Risk is what happens when the two meet an asset of value: the potential for loss when a threat exploits a vulnerability. The three terms are not interchangeable, and the exam tests the distinction directly. An unpatched web server is a vulnerability. A ransomware group actively targeting your industry is a threat. The risk is the chance that the group finds and exploits your unpatched server, and the damage that would follow. A vulnerability with no threat behind it is still worth fixing, but it is not an urgent risk; a threat with no vulnerability to exploit cannot hurt you. Risk exists only where a threat, a vulnerability, and something worth protecting all come together.

Threats and vulnerabilities are each described by their characteristics. A threat is characterized by capability (the skill, tools, and resources the actor has), intent (what the actor wants and how motivated they are), and opportunity (whether the actor has a path to the target). A nation-state actor has high capability, high intent, and usually finds opportunity; an unskilled attacker may have intent but little capability. A vulnerability is characterized by exploitability (how easy it is to exploit: can it be done remotely, does it need credentials, does it need a user to click something?), exposure (how reachable the weakness is: internet-facing or isolated?), and impact (what happens if it is exploited: data theft, system takeover, denial of service?). The same vulnerability can be a minor issue in one environment and a crisis in another, depending on these characteristics — which is why the exam tests judgment about context, not just memorized definitions.

Where threat intelligence comes from

Threat intelligence is information about the threats an organization faces: who is attacking, what methods they use, and what signs to look for. It comes from many sources, and the exam expects you to know the main ones. Open-source intelligence (OSINT) is information gathered from publicly available sources: news reports, social media, public records, breach databases, and code repositories. Attackers use OSINT to research their targets, and defenders use it to learn what attackers know. Commercial threat feeds deliver indicators of compromise (IoCs) — malicious IP addresses, domains, and file hashes — that a SIEM can use to flag traffic to known-bad destinations. Information Sharing and Analysis Centers (ISACs) let organizations in the same industry warn each other about attacks they have seen: a bank that is attacked today can warn every other bank tomorrow. Vendor advisories and government alerts (such as those from CISA, the US Cybersecurity and Infrastructure Security Agency) publish warnings about actively exploited vulnerabilities and ongoing campaigns. And internal sources matter too: an organization's own logs, incident history, and honeypots tell it what is actually being tried against its own systems.

Threat intelligence is often described in four levels. Strategic intelligence is high-level and long-term — trends in who is attacking your sector and why — and it is written for executives making decisions about where to invest. Tactical intelligence describes how attackers operate: their tactics, techniques, and procedures (TTPs), which defenders use to prioritize controls. Operational intelligence covers specific campaigns: which group is running them, who they are targeting, and what they are after. Technical intelligence is the raw detail — the indicators of compromise that tools consume. The exam does not test these levels in depth, but it does test the practical point: intelligence is only useful if it changes a decision. A threat feed that reports a vulnerability you have is being actively exploited moves that vulnerability to the top of the patching queue, whatever its score says.

How vulnerabilities are tracked and scored

The security industry tracks vulnerabilities through shared databases so that everyone can talk about the same flaw with the same name. A CVE (Common Vulnerabilities and Exposures) entry gives each publicly known vulnerability a unique identifier, such as CVE-2024-12345, with a brief description. The National Vulnerability Database (NVD), maintained by the US National Institute of Standards and Technology (NIST), enriches CVE entries with severity scores, affected products, and references. CWE (Common Weakness Enumeration) is a catalog of the underlying weakness types — such as improper input validation or insecure default settings — that cause vulnerabilities. The distinction matters: a CVE is a specific instance of a flaw in a specific product, while a CWE is the general category of weakness it belongs to. One CWE (say, SQL injection) can have thousands of CVEs. When a scanner reports a finding, it usually cites the CVE identifier and the CVSS score so the team can look up the details and prioritize the fix. The vulnerabilities guide covers CVE, CWE, and CVSS in more detail; this guide focuses on what the scoring means for prioritization.

CVSS (Common Vulnerability Scoring System) rates each vulnerability from 0.0 to 10.0 based on its characteristics: how the vulnerability can be exploited (over the network or only with local access), how complex the attack is, whether the attacker needs credentials or user interaction, and what the impact is on confidentiality, integrity, and availability. The ratings are: None (0.0), Low (0.1–3.9), Medium (4.0–6.9), High (7.0–8.9), and Critical (9.0–10.0). The exam tests these bands directly. But CVSS measures the severity of the vulnerability itself, not the risk to your organization — a Critical score on a system nobody can reach is less urgent than a High score on an internet-facing server holding customer data. That gap between severity and risk is the central idea of this objective.

Putting it together: assessing and prioritizing

Assessing a threat means judging its likelihood (how probable is an attack?) and its impact (how bad would it be?), and the usual tool is a risk matrix that plots likelihood against impact so the highest risks stand out. Likelihood depends on the threat's capability, intent, and opportunity, and on whether the vulnerability is actually exploitable in your environment: a vulnerability with a public exploit that anyone can download is far more likely to be used than one that requires custom tooling and insider knowledge. Impact depends on what the vulnerable system holds and does: a database of customer records matters more than a test server. The exam tests this combination constantly, and the correct answer is usually the one that weighs both factors rather than looking at either one alone.

In practice, prioritization combines several signals. CVSS score gives the severity. Exploit availability tells you whether exploitation is theoretical or already happening — a vulnerability with a public exploit, or one that threat intelligence says is being actively exploited, jumps the queue. Exposure tells you whether an attacker can reach it. Asset value tells you what is at stake. And threat intelligence tells you whether anyone is actually coming for you. The exam's classic scenario gives you two or three vulnerabilities and asks which to patch first: the answer is almost never simply "the highest CVSS score" — it is the one that combines a serious score with real exposure and a real threat. Threat modeling is the structured version of this thinking: identify what you are protecting, who would want it, how they would try to get it, and which weaknesses they would use, then prioritize your defenses against the most likely and most damaging paths. You do not need to memorize a threat modeling framework for this exam, but you should understand the idea: defense starts by understanding the threat, not by buying tools.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company's web server has a known unpatched flaw, and a criminal group is actively exploiting that same flaw against other companies in the same industry. The server holds the company's customer database. Which statement correctly uses the terms threat, vulnerability, and risk?

Report an error

Q2.A bank wants early warning when other banks are attacked, so it joins an industry group where member banks share details of attacks they have seen. What type of threat intelligence source is this?

Report an error

Q3.A vulnerability is assigned a CVSS score of 4.2. How is this vulnerability classified?

Report an error

Q4.A security team reads a vendor advisory that references CVE-2026-11873. What does the CVE identifier tell the team?

Report an error

Q5.A threat actor has advanced tools and a strong motive to attack a company, but the company's systems are air-gapped with no network path from the outside. Which element of the threat is missing?

Report an error

Q6.A security analyst wants to find every known instance of SQL injection flaws across many different products, grouped by the underlying weakness type. Which resource organizes weaknesses by type?

Report an error

Q7.An attacker planning a phishing campaign researches a company's executives on social media, reads the company's public job postings to learn which software it uses, and checks public breach databases for employee email addresses. What is this information-gathering method called?

Report an error

Q8.A security team studies how a particular ransomware group operates: the phishing lures it uses, the tools it runs once inside, and the way it moves through a network. What is this description of the group's methods called?

Report an error