Help Desk to Security

Study guide · Domain 2.0 · 22% of the exam

Threats, Vulnerabilities, and Mitigations: the SY0-701 objectives in plain English

Domain 2 is the attack and defense domain: the people and groups who come after your network, the routes they travel to reach it, the weaknesses they exploit when they arrive, the signs their activity leaves behind, and the controls that slow them down or stop them. At 22 percent of the exam it is tied for the second largest domain, which works out to roughly twenty questions on a full exam form, so it deserves a serious share of your study time. If you work a help desk, you already meet most of it on ordinary calls, because the suspicious text a user forwards you, the lockout that does not look like a forgotten password, and the workstation suddenly renaming its files are all Domain 2 showing up in daily form, and learning to name them is most of the work.

2.0

What the objectives cover

2.1 Compare and contrast common threat actors and motivations.

Every attack starts with a person or group, and the exam sorts them by skill and funding. Nation-states have government backing, large budgets, and patience, so they run long espionage campaigns. Organized crime groups work for profit and behave like businesses. Hacktivists act on political or philosophical beliefs and want attention. Insider threats already hold legitimate access, which makes them hard to spot. Unskilled attackers rely on downloaded tools and cause noise more than damage. Shadow IT, meaning systems staff deploy without approval, widens the attack surface. Match the actor to the motivation: espionage, exfiltration, blackmail, financial gain, revenge, service disruption, chaos, or war. Expect matching questions on both.

2.2 Explain common threat vectors and attack surfaces.

Threat vectors are the paths an attack can travel, and the attack surface is the total of all of them. Message-based vectors dominate: email, SMS, and instant messaging carry phishing, smishing, spear phishing aimed at one person, whaling aimed at executives, brand impersonation, typosquatted domains, and watering hole sites that wait for the right visitors. Vishing uses voice calls, and pretexting supplies the invented story that makes any of these believable. Add file-based lures, removable devices, vulnerable software, unsecure networks, open ports and services, default credentials, unmanaged devices, and the supply chain, where a trusted vendor becomes the way in. Influence campaigns work through the same channels.

2.3 Explain various types of vulnerabilities.

A vulnerability is a weakness an attacker can exploit, and this objective groups them by where they live. Application flaws include injection, cross-site scripting, privilege escalation, race conditions, and buffer overflows. Operating system and web-based flaws sit underneath and around those applications. Hardware carries its own risks: outdated firmware, end-of-life gear that no longer gets patches, and legacy systems kept alive for one old program. Mobile devices add sideloading and jailbreaking. Virtualization adds VM escape and resource reuse between guests. Then come cloud-specific issues, supply chain compromises, cryptographic weaknesses, plain misconfiguration, and zero-day flaws nobody has patched yet. Each category has a different owner and a different fix.

2.4 Given a scenario, analyze indicators of malicious activity.

This is the recognition objective: given a scenario, name what the evidence shows. Indicators appear across every attack type, not just malware. Malware itself includes ransomware, trojans, worms, spyware, keyloggers, remote access trojans, logic bombs, rootkits, and fileless malware that lives in memory. Password attacks show up as spraying one password across many accounts or brute force against one account. Application attacks include injection, privilege escalation, API abuse, replay, and pass-the-hash. Physical attacks include lock brute force and RFID cloning. Network attacks include DDoS floods, DNS tampering, on-path interception, and credential replay. Cryptographic attacks include birthday, collision, and downgrade attacks. Learn the sign, not just the name.

2.5 Explain the purpose of mitigation techniques used to secure the enterprise.

Mitigation techniques shrink what an attacker can reach and what they can do after getting in. Segmentation splits the network so one compromise stays contained, and isolation pulls a suspect system away from everything else. Access control lists and permissions decide who can touch what, and least privilege keeps those rights as small as the job allows. Application allow lists run only approved software. Patching removes known flaws, encryption protects data in transit and at rest, and monitoring catches what slips through. Configuration enforcement and hardening finish the job: endpoint protection, host firewalls, disabled ports and protocols, changed default passwords, removed unnecessary software, and clean decommissioning of old systems.

EX

Worked example

Domain 2: Threats, Vulnerabilities, and MitigationsThreat actors: nation-state2-01

A defense contractor discovers intruders in its research network. The attackers used custom malware, stayed hidden for over a year, and only copied design documents. They made no attempt to steal money or demand payment. Which threat actor is MOST likely responsible?

Correct answer: A. Nation-state actors

Nation-state actors are highly funded, patient, and focused on espionage. Long dwell time, custom tools, and theft of research rather than money all point to a state-sponsored group.

Why the other options are wrong

AZ

Acronyms in this domain

AcronymWhat it means
DDoSDistributed Denial of Service
XSSCross-Site Scripting
RATRemote Access Trojan
ACLAccess Control List
HIPSHost-Based Intrusion Prevention System
IDSIntrusion Detection System
IPSIntrusion Prevention System
EOLEnd of Life
VMVirtual Machine
APIApplication Programming Interface
RFIDRadio Frequency Identification
SMSShort Message Service
DNSDomain Name System
VPNVirtual Private Network
HD

Where the help desk meets this domain

Most Domain 2 tickets start as ordinary calls, and your first job is to sort them the way the objectives do. A user reports that files have new extensions and will not open, which is a 2.4 indicator of ransomware, and the message that delivered it arrived through a 2.2 vector, usually a phishing email or a smishing text with a delivery story attached. A caller who cannot sign in after a string of failed attempts may be watching a password spraying attack work through a list of accounts, theirs included. The user who found a USB drive in the parking lot and plugged it in has just tested your removable device policy. The manager who approved a login prompt she never requested has handed an attacker a live session. None of these callers uses exam language, so you translate: who is behind it, how did it get in, and what weakness let it work.

Your side of the response is 2.5 work, and it starts before anyone says the word incident. You escalate with the indicators written down, the exact file extensions, the message headers, the times of the failed sign ins, instead of a guess about what probably happened. You isolate the machine from the network instead of rebooting it, because a reboot can destroy the evidence that shows how far the attack spread. You reset credentials differently for a user who forgot a password and an account that shows signs of attack, and you say so on the ticket. The quiet work counts too: pushing patches, removing software nobody uses, changing the default password on every new printer and router, and flagging the ancient server in the corner that cannot be patched at all. That is the mitigation list from 2.5, done as routine help desk work. When you write tickets that way, you are already answering Domain 2 questions, just with a real user waiting on the answer.

!

Traps to watch for

The cleanest trap in this domain is the channel swap. The same credential lure is phishing when it arrives by email, smishing when it arrives by text message, and vishing when it arrives as a voice call, and the exam changes only the channel between questions. The story is identical each time: a delivery problem, a locked account, a refund waiting. The fake page collecting the password is identical too. What the question is really testing is whether you name the delivery method described in the scenario in front of you, not the one from the last question you answered. So read for the channel first. If the scenario says the user received a text, the answer lives in text message vocabulary no matter how familiar the lure feels. The same habit protects you on brand impersonation and typosquatting questions, where the channel is a lookalike site rather than a message.

The second trap is mixing up the three sorting questions this domain asks. Threat actor, objective 2.1, asks who is attacking and what they want. Threat vector, objective 2.2, asks how the attack traveled to reach the target. Vulnerability, objective 2.3, asks what weakness made the attack possible. A single scenario usually contains all three at once: a criminal group, a phishing email, and an unpatched server can share one short paragraph. The wrong answer choices are rarely nonsense. Each one usually answers one of the other two questions correctly, which is why they look tempting. When two choices both feel right, reread the question stem and find which of the three it actually asked about, then pick the choice that answers that question and ignore the rest. Keep who, how, and what weakness in separate columns in your notes and the sorting becomes automatic.

Now try it. The 5 free sample questions for Domain 2 are in practice mode, with full explanations.

Practice Domain 2 questions
Domain 1 guideAll guidesDomain 3 guide