Mitigation techniques for SY0-701

Exam objectiveExplain the purpose of mitigation techniques used to secure the enterprise

The short answer

What objective 2.5 asks you to know

Objective 2.5 covers the defender's toolkit for reducing the likelihood and impact of the attacks and vulnerabilities in the rest of Domain 2.

Limiting reach. Segmentation divides a network into zones that talk under rules, and isolation separates a system with little or no connectivity, so a compromise stays in one place. Access control decides who may do what: an access control list (ACL) is the list of rules and permissions are the individual rights in it. An application allow list permits only approved software to run, and least privilege limits the rights and actions an account holds.

Lifecycle. Patching changes software to remove a known flaw. Configuration enforcement keeps settings matching the approved baseline without changing the code. Decommissioning retires a system cleanly, covering access, inventory, and secure data destruction.

Protection, detection, and hardening. Encryption keeps stolen data unreadable as long as the keys stay protected, and monitoring reveals problems early enough to respond. Hardening shrinks a system's attack surface by removing what it does not need and securing the rest: encryption, endpoint protection, a host-based firewall, a host-based intrusion prevention system (HIPS), disabling unneeded ports and protocols, changing default passwords, and removing unnecessary software.

Exam questions describe a weakness or incident and ask for the mitigation that addresses it most directly: isolate an unsupported system, disable unnecessary services, and use an allow list against unknown executables.

Written by Knotch · reviewed Nov 15, 2026 · 5 study articles behind this page

Practice the rest

This page is the map. Knotch is where you drill it until it sticks.

  • 5step-by-step lessons with predict-and-reveal and look-alike duels
  • 36exam-style questions with a rationale for every wrong answer
  • 1review queue that brings back what you missed
Start practicing freeFree to start. No card needed.
Tell them apart

Pairs people mix up

  • Segmentation vs. Isolation

    Segmentation divides the network into zones that can still talk under rules. Isolation separates a system with little or no connectivity at all.

  • Patching vs. Configuration enforcement

    Patching changes the software to remove a known flaw. Configuration enforcement changes nothing about the code and keeps settings matching the standard.

  • Least privilege vs. Need to know

    Least privilege limits the rights and actions an account holds. Need to know limits which information a person may see.

  • Host-based firewall vs. Network firewall

    A host-based firewall decides what one device accepts or sends, and protects it even on an untrusted network. A network firewall sits at the edge or between segments and enforces one policy for the systems behind it.

The full set of look-alike pairs for this objective is inside Knotch.

Know these cold

Key terms

Application allow list
An approve-only control that lets only software matching its approval rules run, so it can block unknown malware that a deny list would miss.
Least privilege
The principle of giving an account only the rights and actions it needs; privilege creep is the problem that breaks it.
Segmentation
Dividing a network into controlled zones that can still talk under rules, to keep a compromise in one place.
Hardening
Shrinking a system's attack surface by removing what it does not need and securing what remains.
HIPS
A host-based intrusion prevention system that monitors processes, files, and system calls and blocks activity matching attack behavior, unlike a HIDS, which only alerts.
Configuration enforcement
Keeping a system's settings matching the approved baseline, such as resetting a disabled firewall back to on, without changing the code.
Try one

Sample question

Question 2.5-001 · medium

An employee downloads an installer from a website and runs it. It is a previously unseen malware sample that no antivirus product detects yet. The security team wants a control that would have stopped it from running.

Which mitigation is BEST?

  1. A. A longer password policy for the employee
  2. B. A router ACL that blocks the website the installer came from
  3. C. An application deny list of known malicious programs
  4. D. An application allow list that permits only approved software to run
Show the answer and why
Answer: D, An application allow list that permits only approved software to run

An enforced allow list blocks software that matches no approval rule, so this unknown installer would not run.

An allow list is approve-only, which makes it stronger than a deny list against unknown malware, as long as its approval rules are narrow; a broad rule, such as trusting a whole folder, can let unknown files through. It needs upkeep when approved software changes.

Why not A: Passwords do not control which programs a user can run.

Why not B: Malware can arrive by many routes; a single ACL entry does not stop unapproved software from running.

Why not C: A deny list blocks only software already known to be bad, so a new sample is not blocked.

Quick answers

Common questions on this objective

What is the difference between an allow list and a deny list?

An allow list is approve-only, so software that matches no approval rule is blocked, including unknown malware, although broad rules and abuse of allowed programs remain risks. A deny list is block-only, so it stops only software already known to be bad.

What is the difference between hardening and patching?

Hardening reduces what a system exposes. Patching fixes flaws in what remains.

How do you mitigate a system that can no longer be patched?

Isolate it or place it in its own segment and allow only the connections it needs. Segmentation and isolation compensate for a system the vendor no longer supports.

Know it. Now spot it in a scenario.

Start practicing free