What changed?
Defense evolved alongside threats. Signatures identify known patterns; heuristics and behavioral analysis add context; sandboxing, patching, backups, endpoint protection, segmentation, and incident response reduce harm.
How it spread / worked conceptually
The pipeline is a harmless museum schematic. It does not inspect visitor files, run samples, scan networks, or make external requests.
Why it mattered
No single technique is sufficient. Resilience comes from layers that prevent, detect, contain, and recover.
Representative historical examples
The historical examples in earlier chapters show why each layer emerged: removable media, executable software, documents, networks, email, remote administration, cloud infrastructure, and connected devices each created new boundaries.
What defenders learned
Practice recovery, keep systems updated, segment where appropriate, protect identities, and rehearse incident response.
What changed next?
Malware evolved alongside computing itself—and defense evolved in response. This concludes the historical route.