SY0-501 · Question #118
A security administrator has found a hash m the environment known to belong to malware. The administrator then finds this file to be in the preupdate area of the OS, which indicates it was pushed…
The correct answer is B. The file was infected when the patch manager downloaded it. This question tests the ability to analyze patch management integrity and identify the point of compromise in a software supply chain attack.
Question
A security administrator has found a hash m the environment known to belong to malware. The administrator then finds this file to be in the preupdate area of the OS, which indicates it was pushed from the central patch system. The administrator pulls a report from the patch management system with the following output:
Given the above outputs, which of the following MOST likely happened?
Options
- AThe file was corrupted after it left the patch system
- BThe file was infected when the patch manager downloaded it.
- CThe file was not approved in the application whitelist system
- DThe fee was embedded with a logic bomb to evade detection
How the community answered
(56 responses)- A7% (4)
- B75% (42)
- C14% (8)
- D4% (2)
Why each option
This question tests the ability to analyze patch management integrity and identify the point of compromise in a software supply chain attack.
File corruption after leaving the patch system would typically result in a hash mismatch with the original patch, not a match with a known malware hash, making intentional malware infection a more accurate conclusion.
When the patch management system downloads updates from an external source, if the file is already malicious at that stage, it indicates the compromise occurred during or before the download process - a classic supply chain attack. The fact that the hash matches known malware and the file originated from the central patch system means the malicious file entered the environment through the patch manager's download process, before any internal distribution occurred.
An application whitelist system would block execution of an unapproved file but would not explain why the file's hash matches known malware, nor would it account for how the malicious file entered via the patch system.
A logic bomb is a payload that triggers under specific conditions and is a separate concept from how the file entered the environment; the scenario describes a file already identified by hash as malware, not behavior-based evasion.
Concept tested: Supply chain compromise via patch management system
Source: https://www.cisa.gov/topics/cyber-threats-and-advisories/threats/supply-chain-compromise
Topics
Community Discussion
No community discussion yet for this question.