Skip to content

Beginner · Security basics · topic 2 of 43 · 30 min

Threats, vulnerabilities and risk

Explanation

A vulnerability is a weakness. A threat is someone or something that could use that weakness to cause harm. Risk is how likely that harm is, multiplied by how bad it would be. Security work is mostly about reducing risk, not removing it completely.

Why these three words matter

People often mix up threat, vulnerability and risk. In a security job, mixing them leads to wrong decisions: you spend money on a scary-sounding problem that is unlikely, and miss a boring one that will really hurt. Each word has a clear meaning.

Asset

An asset is anything of value that you want to protect: customer data, a payment server, a laptop, your company's reputation, even an employee's time. You always start by listing assets, because you cannot protect what you do not know you have.

Vulnerability: the weakness

A vulnerability is a weakness that could be used to cause harm. Examples: an old version of software with a known bug, a password like "admin123", a server port open to the whole internet, or an employee who has never been told about phishing.

Publicly known software vulnerabilities get an ID called a CVE (Common Vulnerabilities and Exposures), for example CVE-2021-44228, the famous Log4j bug. Many also get a CVSS score from 0 to 10 that describes how severe the bug is in general.

Threat: who or what could cause harm

A threat is anything that could take advantage of a vulnerability. A threat actor is the person or group behind it. Threats are not only hackers: a careless employee, a flood in the server room or a power cut are threats too.

  • Cyber criminals: want money, for example through ransomware or UPI fraud.
  • Insiders: employees or contractors who misuse access, on purpose or by mistake.
  • Hacktivists: attack to make a political point.
  • Nation-state groups: well-funded teams that spy or disrupt for a government.
  • Natural and accidental threats: fire, flood, a cable cut, a wrong configuration.

An exploit is the actual method or code that uses a vulnerability. If the vulnerability is an unlocked window, the exploit is climbing through it.

Risk: likelihood times impact

Risk is the chance that a threat uses a vulnerability, combined with how much damage it would do. A simple and widely used way to rate it is to score likelihood and impact from 1 (very low) to 5 (very high) and multiply.

python
likelihood = 4   # phishing emails arrive every week
impact = 5       # one stolen finance password could cost lakhs
risk = likelihood * impact
print("Risk score:", risk, "out of 25")
A simple risk score. Shows Risk score: 20 out of 25.
ScoreRatingTypical action
1–4LowAccept and watch
5–9MediumFix in the normal plan
10–16HighFix soon, report to managers
20–25CriticalAct now

Bands differ between companies; the important thing is that everyone uses the same scale so risks can be compared.

Four ways to treat a risk

  1. Reduce (mitigate): add a control, such as MFA or a patch.
  2. Avoid: stop doing the risky thing, such as switching off an old unused server.
  3. Transfer: share the cost with someone else, such as cyber insurance or an outsourced provider.
  4. Accept: decide the risk is small enough and write down who accepted it and why.
Think of it like this: Your house: the asset is your family and belongings. A broken lock is a vulnerability. A thief in the area is a threat. The risk is high if the lock is broken AND thefts are common AND you keep cash at home. You reduce it by fixing the lock, transfer it with home insurance, or avoid it by keeping cash in the bank.

Common mistakes

  • Calling everything a "threat". "Our old VPN" is a vulnerability; "a ransomware gang" is a threat.
  • Rating risk by fear instead of evidence. Ask how often it really happens and what it would really cost.
  • Treating CVSS as risk. A 9.8 bug on a server nobody can reach may be lower risk for you than a 6.5 bug on your public website.
  • Accepting a risk without writing down who accepted it. Unwritten acceptance is just ignoring it.
Tip: Zero risk does not exist. Your job is to bring risk down to a level the business agrees to, and to know which risks remain.

Need help?

Stuck on a word or an idea? Search this course, or every course, and jump straight to the explanation or a worked question.

Try:

Watch the lesson

Threats, vulnerabilities and risk · 1/7

Vulnerability Threat Risk

Three words decide most security choices: vulnerability, threat and risk.

Prefer a video by a teacher? Find free videos on “threat vs vulnerability vs risk explained cybersecurity” on YouTube ↗

In real life: A small CA firm in Pune

A chartered accountant firm keeps clients' PAN and bank details on a shared office PC (asset). The PC runs an old, unpatched Windows version and everyone uses one shared password (vulnerabilities). Ransomware gangs actively target small firms, especially during tax season (threat). Likelihood 4, impact 5: risk 20, critical. The firm reduces it by updating Windows, giving each person their own login with MFA on email, and keeping an offline backup. It transfers part of the remaining risk with cyber insurance.

python
risks = {"Old Windows PC": (4, 5), "Shared password": (4, 4), "Office flood": (1, 4)}
for name, (likelihood, impact) in risks.items():
    print(name, "→", likelihood * impact)
Shows 20, 16 and 4: fix the old PC first.

Practice (0/3 done)

Task 1 · Question

A company server runs software with a known, unpatched bug. What is the unpatched bug?

Task 2 · Code · Python

Write risk_score(likelihood, impact) that returns likelihood × impact, and raises ValueError if either value is not between 1 and 5. Then write risk_level(score) that returns "Low" for 1–4, "Medium" for 5–9, "High" for 10–16 and "Critical" for 17 and above.

Task 3 · Practice

Write a mini risk list for your own home or hostel computer: three assets, one vulnerability and one threat for each, a likelihood and impact score (1–5), the risk score, and one treatment (reduce, avoid, transfer or accept).

Quick quiz

Question 1

1.Which is a threat, not a vulnerability?

Question 2

2.Likelihood 3 and impact 4 gives a risk score of…

Question 3

3.Buying cyber insurance is which risk treatment?

Question 4

4.What is a CVE?

Question 5

5.Why is a CVSS score alone not your risk?

Read more (free)

Before this, learn

This topic builds on these. If something here feels new, open them first.

Open a question to see the answer and why. The first ones are this topic's own quiz, so try the quiz above before you peek.

Which is a threat, not a vulnerability?

Answer: A ransomware gang targeting hospitals

The gang is who could cause harm. The others are weaknesses.

Likelihood 3 and impact 4 gives a risk score of…

Answer: 12

The simple model multiplies: 3 × 4 = 12.

Buying cyber insurance is which risk treatment?

Answer: Transfer

Insurance moves part of the financial impact to someone else: transfer.

What is a CVE?

Answer: A public ID for a known software vulnerability

CVE IDs like CVE-2021-44228 name publicly known vulnerabilities so everyone talks about the same bug.

Why is a CVSS score alone not your risk?

Answer: It ignores whether the system is exposed and how important it is to you

CVSS rates the bug in general; your risk also depends on exposure and the value of the asset.

Where would you confirm a CVE and its score?Related

Answer: The NVD and vendor advisories

Cross-check the NVD and vendor advisories.

From CVE and CVSS: naming and scoring weaknesses

A logged-in user changes /api/orders/1005 to /api/orders/1006 and sees a stranger's order. Which risk is this?Related

Answer: Broken access control

The server did not check that the order belongs to this user. That is broken access control.

From The OWASP Top 10: the most common web risks

Residual risk is…Related

Answer: Risk left after controls are applied

What remains after treatment, which management must accept.

From GRC and risk management

A vulnerability has no fixed version yet. What is a sensible way to let the pipeline continue?Related

Answer: Add an exception with an owner, a reason and an expiry date

An expiring exception is recorded, owned and reviewed again, so it does not become permanent by accident.

From DevSecOps: shifting security left

Pass the quiz (60% or more) or mark this topic as done when you are ready.

Your progress is saved on this device only.

Next steps

  1. 3 more topics in “Security basics” before its exam: Passwords and multi-factor authentication, Phishing and social engineering, Ethics and the law: permission first.
  2. Module 1 exam: Security basics · 13 questions · 20 min, without help. 5 topics of this module still to finish first.
  3. Then the next module, Networking for security. 43 topics left in the course before the final exam.

← Previous: What cyber security protects: the CIA triad