SY0-701 domain - 22% of the exam

Threats, Vulnerabilities, and Mitigations

Threats, Vulnerabilities, and Mitigations is 22% of the SY0-701 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

72
Practice questions
5
Objectives
14
Easy
44
Medium
14
Hard

Where people go wrong

  • Mismatching a threat actor and its motivation

    The wrong answers attach a motive to the wrong actor. Quiet theft of engineering data with no disruption is espionage by a nation-state, and extortion or hacktivism are the lures. A cryptocurrency ransom demand marks organised crime, defacement with public demands marks hacktivism, and a trusted employee abusing legitimate access is an insider. Visibility is the tell: espionage avoids attention, while hacktivists seek it. Unauthorised access alone does not define espionage, because motive is read from behaviour, stealth or extortion.

    See it in a sample question
  • Naming the wrong delivery vector

    The wrong answers pick a vector that shares a feature with the real one. A text message leading to a fake sign-in page is smishing rather than vishing, and a text that pushes the victim to ring a number is still smishing because the lure arrived by SMS. Tailored email to named partners is spear phishing rather than bulk phishing. Compromising a site the targets visit is a watering hole, and tampering with a vendor update or an embedded third-party script is supply chain. The entry channel sets the label.

    See it in a sample question
  • Calling a vulnerability the wrong type

    Zero-day, end-of-life and misconfiguration are separated by cause, and the wrong answers swap them. A flaw exploited before any vendor fix exists is a zero-day. A platform past vendor support accumulates flaws that will never be patched. An open storage bucket or default password comes from how the system was set up, and no code defect is involved. An n-day has a patch available that is not yet applied. Each calls for a different response: virtual patching, compensating controls or a configuration baseline.

    See it in a sample question
  • Naming a neighbouring flaw for an overflow, injection or race condition

    The wrong answers name a flaw that shares a surface feature with the real one. An unchecked copy of attacker input into a fixed stack array is offered as SQL injection, a race condition or server-side request forgery. A search field concatenated into a query is offered as open redirect or CSRF. A gap between a check and a later action is offered as path traversal or insecure deserialisation. Overflow writes past a buffer, injection lets input be parsed as code, and TOCTOU lets state change between check and use.

    See it in a sample question
  • Crediting one mitigation with another's job

    Hardening, patching, least privilege and segmentation each reduce a different thing, and the wrong answers credit one with another's work. Hardening shrinks the attack surface by removing unneeded services and default accounts, so detective tooling or network zoning does not count as hardening. Patching closes known flaws and cannot stop a zero-day. Least privilege limits what an account can do, and segmentation limits where a compromise can reach. Layered together they cut blast radius, and no single one does.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleThreats, Vulnerabilities, and Mitigationseasy

A regional water utility's SCADA network is breached by an attacker who patiently maintains access for months, exfiltrates engineering diagrams, and tampers with no production processes. Forensics traces the operation to infrastructure linked to a foreign military intelligence unit. Which threat actor category best fits the adversary in this incident?

  • AAn organised cybercrime gang motivated by extorting the utility through a ransomware payout demand.
  • BA hacktivist collective protesting the utility's environmental record through public defacement actions.
  • CA disgruntled insider abusing valid credentials to harvest confidential project files for personal use.
  • DA nation-state actor conducting cyber espionage to map critical infrastructure for future leverage. Correct
Recognise that prolonged stealthy intrusions targeting critical infrastructure for intelligence value typically map to nation-state threat actors. Nation-state actors prioritise persistent access, low-noise operations, and intelligence collection over immediate disruption or financial gain. Stealing engineering diagrams from a SCADA environment supports future targeting and strategic leverage, which is the defining motivation of state-sponsored espionage against critical infrastructure operators.

Why A is wrong: Tempting because utilities are common ransomware targets, but the long dwell time, lack of disruption, and theft of engineering diagrams point to espionage rather than financially motivated extortion.

Why B is wrong: Hacktivists seek visibility and publicity for a cause, so they would deface sites or leak data publicly rather than quietly steal schematics for months.

Why C is wrong: An insider scenario is plausible at utilities, but forensics here points to external foreign infrastructure rather than a current employee acting from within the network.

Why D is correct: Long-term stealthy access, theft of engineering data, and attribution to a foreign military intelligence unit are hallmarks of nation-state espionage against critical infrastructure.

Free sampleThreats, Vulnerabilities, and Mitigationsmedium

An attacker targeting a small group of geologists at a mining company discovers that they all consult the same niche industry blog every morning to read overnight commodity commentary. The attacker compromises the blog and adds a malicious script that profiles visitors and delivers an exploit only to browsers identifying as the company's standard build. Which threat vector best matches this technique?

  • AA drive-by spear phishing campaign that emails tailored links to each geologist so they click through to the malicious blog directly from their inbox.
  • BA typosquatting attack registering a near-identical domain name to the blog so that staff who mistype the address are redirected to an attacker-controlled clone.
  • CA supply chain attack against the analytics provider that the blog embeds so that the malicious payload is delivered to every blog visitor without the blog owner's knowledge.
  • DA watering hole attack that compromises a site the target group visits and selectively exploits visitors matching the intended victim profile. Correct
Recognise selective exploitation of visitors to a shared trusted website as a watering hole attack. Watering hole attacks exploit predictable browsing habits of a target community: rather than mailing each victim, the attacker poisons a site the victims trust and visit anyway, often filtering exploit delivery by user agent, IP range, or referrer so that only intended targets are affected and detection is delayed.

Why A is wrong: Tailored emails sound plausible as a delivery mechanism, but the scenario describes passive exploitation of a habitual site visit rather than email-borne links sent to individuals.

Why B is wrong: Typosquatting targets misspellings of a legitimate domain, but here the attacker compromised the genuine blog rather than registering a confusable domain to catch typos.

Why C is wrong: A third-party script supply chain compromise is a real risk, but the stem says the blog itself was compromised and the payload was tuned to a specific browser fingerprint, which is the watering hole pattern.

Why D is correct: Compromising a frequently visited third-party site and conditionally exploiting only matching visitors is the canonical pattern of a watering hole attack against a defined target community.

Free sampleThreats, Vulnerabilities, and Mitigationsmedium

A managed hosting provider learns at 09:00 that a critical remote code execution flaw in a widely used web framework is being actively exploited in the wild. No vendor patch is available, the issue has no CVE entry yet, and proof of concept exploit code is already circulating on social media. Which vulnerability category best fits this situation, and which short term mitigation should the provider deploy first while a vendor fix is awaited?

  • ALegacy end of life software; isolate the affected hosts on a dedicated VLAN and schedule a long term migration to a supported framework.
  • BZero day vulnerability; deploy targeted virtual patching rules at the web application firewall and tighten egress filtering on the affected hosts until the vendor patch is available. Correct
  • CMisconfiguration; run a configuration baseline scan against every web host and reset any host that deviates from the hardened template.
  • DCryptographic weakness; force all customers onto TLS 1.3 with modern cipher suites and revoke any certificates issued before the vulnerability disclosure window.
Recognise a zero day situation from the absence of a vendor patch and apply compensating controls such as virtual patching and egress restriction. A zero day is a vulnerability that defenders learn about with zero days of vendor remediation lead time, often because exploitation precedes disclosure. The risk cannot be removed until the vendor ships a fix, so defenders rely on compensating controls that block known exploit patterns at upstream choke points and limit the blast radius of any successful compromise, then patch promptly once a fix exists.

Why A is wrong: End of life software describes products no longer receiving vendor support at all; the framework here is current and the vendor is expected to ship a fix, so isolating only legacy systems misses the broader attack surface for a fresh in the wild flaw.

Why B is correct: A flaw under active exploitation before a vendor fix exists is the defining shape of a zero day; virtual patching at the web application firewall blocks the known exploit pattern, and constrained egress reduces the value of any callback an attacker manages to land while the vendor produces an official patch.

Why C is wrong: Misconfiguration covers settings that depart from a hardened baseline, such as default passwords or open admin interfaces; the described defect is in the framework code itself and exists on hosts that already match the hardened baseline.

Why D is wrong: Cryptographic weakness involves flaws in algorithms, protocols, or key management; pushing TLS 1.3 does not address a remote code execution defect in the application framework regardless of which cipher suites are negotiated.

Free sampleThreats, Vulnerabilities, and Mitigationsmedium

A developer is reviewing a C network daemon that copies an incoming packet field into a fixed 256 byte stack array without checking the field length. During a code review, the team agrees the input is fully attacker controlled and the function lacks any bounds checking. Which vulnerability class most directly describes this defect, and which mitigation should the team prioritise in the next sprint?

  • ARace condition; serialise access to the array with a mutex around the copy operation in the daemon.
  • BSQL injection; switch the daemon to parameterised database queries and add an allow list of valid characters at the network boundary.
  • CServer side request forgery; restrict the daemon's outbound network access using egress filtering and a metadata service block list.
  • DStack based buffer overflow; replace the unsafe copy with a length checked routine and enable stack canaries plus non executable stack protections. Correct
Recognise a classic stack based buffer overflow pattern in unmanaged code and pair it with bounds checking plus runtime memory protections. When an unchecked length attacker controlled value is copied into a fixed size stack buffer, adjacent stack data including saved return addresses can be overwritten, allowing control flow hijack. The mitigation is layered: replace unsafe copy primitives with bounded equivalents, then rely on compiler and platform defences such as stack canaries, address space layout randomisation, and non executable stacks to make residual flaws much harder to exploit.

Why A is wrong: Race conditions arise when two threads or processes interleave on shared state in a way that violates assumptions; a single threaded copy of an oversized field is not a timing flaw, and a mutex does nothing to stop a long input from overrunning a fixed buffer.

Why B is wrong: SQL injection requires user input to flow into a query interpreter, which is not the situation described; parameterised queries are good practice for database code paths but do not stop memory corruption in a packet parser.

Why C is wrong: Server side request forgery involves tricking a server into making attacker chosen outbound requests, which has nothing to do with copying packet bytes into a stack array; egress filtering will not protect a vulnerable memory copy.

Why D is correct: Writing an unbounded attacker controlled field into a fixed sized stack array is the textbook stack buffer overflow pattern; bounded copy functions, stack canaries, ASLR, and non executable memory together raise the cost of exploitation and address the underlying defect.

Free sampleThreats, Vulnerabilities, and Mitigationsmedium

Which statement most accurately defines system hardening as a mitigation technique?

  • AReducing the attack surface of a system by disabling unneeded services, removing default accounts, and applying a secure baseline configuration. Correct
  • BInstalling endpoint detection and response agents on every host so that suspicious process behaviour generates alerts for the security operations team.
  • CWrapping legacy operating systems in a network microsegment so that only a defined jump host can reach their management interfaces over the network.
  • DEncrypting the boot volume of a workstation with a platform managed key so that data at rest is protected if the device is lost or stolen.
Define hardening as the practice of reducing attack surface through baseline configuration and removal of unneeded functionality. Hardening focuses on the configuration of the host itself. The control disables or removes services, ports, accounts, and features that the workload does not need, then applies a documented secure baseline derived from a recognised benchmark. The smaller the running attack surface, the fewer paths an attacker has to exploit, irrespective of any monitoring, encryption, or network containment around the host.

Why A is correct: This is the textbook definition: hardening shrinks the attack surface by removing functionality the workload does not require and aligning the remaining configuration with a secure baseline.

Why B is wrong: EDR is a detective and responsive control layered on top of a system, whereas hardening is a configuration discipline that reduces what an attacker can interact with in the first place.

Why C is wrong: Microsegmenting an exposed host is a containment strategy, not hardening of the host itself, and it leaves the underlying configuration weaknesses in place behind the policy boundary.

Why D is wrong: Full disk encryption protects data at rest but does not reduce the attack surface presented by a running system, which is what hardening addresses.

Other domains in this exam

See also the SY0-701 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by CompTIA. Original, blueprint-aligned practice material only.