Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 38 ยท Getting Started

Attacker Mindset and Core Terminology

Learn the vocabulary of penetration testing: vulnerability, threat, exploit, payload, risk, attack surface, CIA triad and the kill chain, plus how attackers think.

Every field has a vocabulary, and in security the words are used loosely in the news but precisely in a report. A vulnerability is not a threat, and neither is a risk. Getting the terms right makes your findings credible. This lesson also introduces the mindset that separates a tester from a tool operator: curiosity about how things are supposed to work, and about what happens when someone does the unexpected.

The words you will use every day

Term Meaning Example
Asset Something worth protecting Customer database
Vulnerability A weakness that could be misused Unpatched web server
Threat Something or someone that could cause harm Criminal group, malicious insider
Exploit Code or a technique that uses a vulnerability A crafted request that triggers a bug
Payload What runs or happens after the exploit works A command that proves access
Attack vector The path used to reach the weakness Phishing email, exposed port
Attack surface All points where an attacker could try to get in Every public page, port and employee inbox
Risk Likelihood times impact of a threat using a vulnerability A high-likelihood, high-impact flaw on the main site
Control A measure that reduces risk Firewall, MFA, patching
Zero-day A flaw unknown to the vendor No patch exists yet

A useful sentence ties them together: a threat uses an exploit against a vulnerability to harm an asset, and risk is how likely and how costly that is.

How the words connect

Threat Someone with motive and means.
Vulnerability The weakness they use.
Asset What is harmed.
Risk Likelihood times impact.

Fix risk by cutting any link in the chain.

1 / 2

The CIA triad

Security goals are summarized as three properties.

  • Confidentiality: only authorized people can read the data. A leaked customer list breaks it.
  • Integrity: data and systems are not changed without permission. A tampered invoice breaks it.
  • Availability: systems work when needed. Ransomware and floods break it.

Every finding in a report should name which property is affected. It also helps rank severity: a flaw that exposes passwords hits confidentiality; one that lets an attacker alter prices hits integrity.

The attack chain

Attackers rarely win with one step. Models such as the Lockheed Martin Cyber Kill Chain and the MITRE ATT&CK framework describe stages like reconnaissance, initial access, execution, persistence, privilege escalation, lateral movement and impact. As a tester you follow a simplified path. You will often chain small weaknesses: an information leak reveals a username, a weak password gives a foothold, a misconfigured service gives admin rights.

This is why low-severity findings matter. Two "low" issues can combine into a "critical" one.

How attackers think

Defenders ask "does it work?" Attackers ask "what else does it do?" A few habits to cultivate:

  1. Question assumptions. The developer assumed the user only enters a number. What if they enter text, a very long string, or nothing?
  2. Follow the trust. Every system trusts something: a cookie, a header, an internal network, a vendor. Where is that trust too generous?
  3. Look at the edges. Forgotten test servers, old APIs, backup files, admin pages and error messages leak a lot.
  4. Take the easy path. Real attackers choose weak passwords, phishing and unpatched software before clever exploits. So should your prioritization.
  5. Think in chains. Ask "if I had this, what would I do next?"

A tester also keeps a defender's mindset: how would this have been detected, and how is it fixed? That second half turns a clever trick into a useful report.

Attack surface in practice

Imagine a small company. The surface includes the public website, the mail server, a VPN login, staff email addresses on LinkedIn, a test server someone forgot, a mobile app, and the people who answer phones. Reducing the surface (closing ports, deleting unused hosts, removing old accounts) is one of the cheapest defenses.

Stand-in: compute a simple risk score

Risk is often scored with a likelihood and impact on a 1 to 5 scale. The first example multiplies them and maps the result to a label. This is a simplified teaching model, not any official standard.

Python Likelihood times impact

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The second example tags findings with the CIA property they affect and counts them. In a real report this kind of summary helps managers see the shape of the risk.

Python Which CIA property is affected?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Notice that the last issue stays "unclassified". Keyword matching is crude, and a tester would read it and decide. Stand-ins like this show the idea; judgment finishes the job.

Ethical mindset

Curiosity is a strength, but it must be channeled. A good tester is patient, careful with other people's data, and comfortable saying "I do not know yet". Many testers keep a personal rule: if I would not be comfortable explaining my action to the client's CEO, I do not do it. See Legal and Ethics.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which term describes a weakness that could be misused?

    A vulnerability is the weakness. The threat is the actor, the exploit is the technique and the payload is what runs.
  2. 2. An attacker alters the prices in a shop database. Which CIA property is broken?

    Unauthorized modification is an integrity failure.
  3. 3. Why can two low-severity findings still matter?

    Attack chains combine small weaknesses, such as an information leak plus a weak password.
  4. 4. Risk is best described as

    Risk weighs how likely harm is and how bad it would be.

Summary

  • Know the vocabulary: asset, vulnerability, threat, exploit, payload, attack vector, attack surface, risk, control.
  • The CIA triad (confidentiality, integrity, availability) names what a finding harms.
  • Attacks are chains; small weaknesses combine.
  • The attacker mindset questions assumptions, follows trust, checks the edges and takes the easy path.
  • Stay ethical: curiosity within authorization.

Next: Scoping a Penetration Test