Chapter 4 · Reading 2 of 12
Viruses
Security+ SY0-801 · Objectives 2.5
A software update changes hundreds of files in an evening. A virus can change files too. If you arrived at the advising office the following morning, the number of changed files alone would tell you little about which event took place.
A virus replicates by infecting a host object. Classify it first by where its replicating code resides. The action that gives that code control can be an ordinary program launch, document processing or the boot process. An explicit click by a user is only one possible trigger.
File infector or boot-sector virus?
A file infector modifies a host file, commonly an executable, so that launching the infected program can run the viral code. Compare the same product, version and architecture against a trusted signed release. A changed executable warrants investigation. To support a virus classification, seek evidence that other host files were infected. A single modified executable could also be an unauthorized replacement or a legitimate local build.
A boot-sector virus infects boot code on a storage medium. On legacy systems that may be a volume boot sector or the boot code in the master boot record (MBR). Execution can begin when the machine boots from that medium, before the ordinary operating system loads. A boot-starting service and an altered UEFI executable are different artifacts. Identify the actual startup mechanism before describing an incident as a boot-sector infection.
Classify the evidence on separate axes
A macro virus uses a host such as a document or template. A resident virus stays active in memory after initial execution. Polymorphism describes changes in viral representation between infections. These labels answer different questions and can coexist. A worm can propagate independently across systems. Seeing the same file on a shared drive only establishes that it was distributed.
Suppose a lab workstation fails its startup integrity check after a maintenance window. Compare the boot configuration and boot-area evidence with the approved change. Separately verify suspect application files against trusted releases. Preserve the original observations before repair. Document which object changed, whether it executed and what evidence supports replication. An unverified update or damaged disk remains a plausible alternative until the evidence distinguishes it.
Compare two workstations
Suppose the two machines run the same approved scheduling release. One file on the first machine differs from the signed release. On the second machine, the application files match but a startup integrity check reports an unexpected change. Preserve those as separate observations. On the first machine, investigate the executable and whether other host objects changed after it ran. On the second, identify which boot component was measured and whether a maintenance event accounts for it. A conclusion that fits the first machine may have no bearing on the second. For both, the next question from the advising desk will concern access to appointments. A classification should help you explain that impact.
Inspect the three records, then use the evidence to answer the question.
1. Changed file
A file differs from the known release.
Signed catalog lists hash A for build 10
2. Trusted baseline
Compare the version and release history.
Host X / build 10 / hash B
3. Host evidence
Check what actually ran and changed.
Host Y / build 10 / hash A
Apply the reading
Why compare a suspected file with a trusted release before declaring an infection?
Compare your reasoning
A difference establishes a change. A trusted baseline, release history, and endpoint observations help explain what changed and why.