Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 4 · Reading 7 of 12

Rootkits

Security+ SY0-801 · Objectives 4.8

One tool says a workstation is idle. An independently managed network sensor continues to record traffic from it. Before deciding which one to believe, identify how each observation was collected and which parts of the system it depends on.

A rootkit is a type of malicious software designed to grant unauthorized access to a computer or network and maintain persistent, hidden control over the system. Rootkits are particularly dangerous because they can conceal their presence and the activities of other malicious software, making them difficult to detect and remove.

Types of Rootkits

  • Kernel-Mode Rootkits: Operates at the kernel level of the operating system, giving them the highest level of control. They can intercept and modify system calls, making them very difficult to detect and remove. Kernel-mode rootkits are typically the most dangerous and sophisticated.
  • User-Mode Rootkits: Targets applications and processes running at the user level. While they are easier to detect than kernel-mode rootkits, they can still be very effective at hiding malicious activities.
  • Bootkits: Targets the boot process of a computer, infecting the master boot record (MBR) or the Unified Extensible Firmware Interface (UEFI). They load before the operating system, allowing them to evade detection by most security software.
  • Firmware Rootkits: Resides in the firmware of hardware devices, such as network cards, hard drives, or the BIOS/UEFI. Firmware rootkits are extremely difficult to detect and remove because they are embedded in the hardware itself.
  • Hypervisor Rootkits (Virtualized Rootkits): Runs beneath the operating system by exploiting hardware virtualization features. They can intercept and manipulate the operating system and its processes from a lower layer, making detection and removal very challenging.

Anti-Cheat: A Rootkit Installed

Anti-cheat systems are designed to prevent cheating in online games by detecting and blocking unauthorized modifications or exploits. However, some of these systems operate in a manner similar to rootkits, which has raised concerns about privacy and security among users. Developers must ensure these systems are secure, transparent, and respectful of user privacy to maintain trust and protect against potential abuses.

Choosing a trustworthy observation point

A compromised operating system can misreport its own state. Compare local observations with independent network records, a known-good boot environment or a protected image collected under procedure. Preserve the original and document collection limits. Recovery may require rebuilding trust from firmware through the operating system.

Finding an independent point of comparison

Two local utilities can agree because both ask the same operating system for their information. Their agreement may add little assurance if that operating system is the object of the investigation. A protected network record, a known-good startup environment and a verified baseline provide different perspectives. Check clock alignment, device identity and normal background services first. An address that belonged to another device yesterday can produce an apparent contradiction without any tampering.

For a confirmed compromise, think through the layers involved in rebuilding trust. Restoring an application alone cannot resolve an unauthorized change below the operating system. Conversely, invasive recovery needs evidence proportionate to its cost and disruption. Give the incident lead a documented reason for the chosen recovery boundary.

Paired visibility traces

Inspect the three records, then use the evidence to answer the question.

1. Local view

The host reports its running processes.

Host utility reports no active connection

2. External view

A collector records network activity.

Independent network sensor records traffic from WS8

3. Trusted view

An offline inspection provides another baseline.

Trusted offline image is available for comparison

Apply the reading

Why might a clean process list provide weak reassurance on a machine suspected of deep compromise?

Compare your reasoning

The reporting mechanism may itself be affected. Seek independent evidence such as centrally collected telemetry or a trusted offline inspection.