Malware is any software written to damage, disrupt, or gain unauthorized access to systems and data. NIST SP 800-83 Rev. 1 describes it as a program covertly inserted into another program to destroy data, run destructive or intrusive programs, or otherwise compromise the confidentiality, integrity, or availability of the victim’s data, applications, or operating system.
The label covers a wide family. Viruses attach to legitimate files, worms copy themselves across networks, trojans hide inside something that looks useful, Ransomware encrypts or steals data for extortion, spyware quietly watches, and rootkits hide an attacker’s presence on a machine. Logic bombs, keyloggers, botnet agents, and cryptominers round out the list.
How does malware work?
Most infections follow the same arc. Malware arrives through a delivery vector, most often a phishing attachment or link, a drive-by download, an infected removable drive, a compromised software update, or direct exploitation of an unpatched service. It then executes, establishes persistence so it survives a reboot, contacts a command-and-control server for instructions, and carries out its payload, whether that’s encryption, theft, or spreading to the next host.
Modern samples rarely fit one neat box. They blend techniques, pack or encrypt their own code to slip past signature scanners, and increasingly run fileless, living in memory and abusing built-in tools like PowerShell and WMI. MITRE ATT&CK catalogs these behaviors technique by technique, and that behavioral view is why defenders have moved from pure signature matching toward Endpoint Detection and Response, which watches what processes do rather than what their files look like.
What is the difference between a virus, a worm, and a trojan?
| Type | Needs a host file? | Spreads on its own? | Key trait |
|---|---|---|---|
| Virus | Yes | No, needs a user or program to run the host | Infects other files |
| Worm | No | Yes, across networks | Self-propagating |
| Trojan | No, it is the disguised program | No | Tricks the user into running it |
| Rootkit | No | No | Hides itself and other malware, often at kernel or firmware level |
The exam leans hard on the virus versus worm distinction. If the scenario says the code spread from machine to machine with no user action, it’s a worm. A rootkit is about concealment, not spread, which is why the usual remedy is to rebuild the system from known-good media instead of trying to clean it.
What is an example of malware?
WannaCry is the textbook case because it was both ransomware and a worm. CISA alert TA17-132A records its discovery on May 12, 2017, and describes how it spread through the EternalBlue exploit against SMBv1 on ports 139 and 445. Microsoft had released the MS17-010 patch on March 14, 2017, two months earlier. Organizations that had patched, or had blocked SMB at their network edge, were largely spared. Those that hadn’t saw infections jump from host to host within hours.
The lesson for a manager is that the cheapest control, timely patching, would have stopped most of the damage, and that network segmentation limits how far a worm can travel when a patch is missed.
How is malware tested on the CISSP exam?
Malware appears mainly in Domain 7: Security Operations, which carries 13 percent of the exam. Objective 7.7 lists anti-malware, sandboxing, and allowlisting among detection and prevention measures, objective 7.8 covers patch and vulnerability management, and objective 7.6 covers incident handling once an infection is found. Ransomware is also named under cryptanalytic attacks in objective 3.7, and Domain 8 covers prevention through secure coding.
Expect two kinds of judgment questions. First, the incident response order. After detecting malware on a host, the priority is containment, such as isolating it from the network, before eradication. Wiping the machine first destroys evidence and does nothing about other infected hosts. Second, layered defense. No single product stops malware, so the best answer usually combines patching, email filtering, application allowlisting, EDR, least privilege, segmentation, offline backups, and user awareness. An answer that relies on antivirus alone is almost always the weaker choice.
CISA tracks active threats at StopRansomware.gov. NIST’s handling guidance is SP 800-83 Rev. 1, Guide to Malware Incident Prevention and Handling.
Related terms: Endpoint Detection and Response, Ransomware, Sandboxing