Chapters0/54 ▾
0 of 54 lessons finished
- 1.Architecture & Log Sources0/5
- 2.Indicators of Malicious Activity0/5
- 3.Investigation Tools & Threat Hunting0/5
- 4.Process Improvement, Automation & AI0/5
- 5.Vulnerability Scanning Methods0/5
- 6.Analyzing Scan Output0/5
- 7.Prioritization, Mitigation & Controls0/5
- 8.Attack Frameworks & the Response Process0/5
- 9.Incident Response Techniques0/5
- 10.Vulnerability Reporting & Communication0/5
- 11.Incident Reporting & Metrics0/4
Chapter 5 · Lesson 4 of 5
Passive scanning, fragile devices and scan scheduling
1 min read
Active scanning sends probes and waits for answers. Passive scanning analyzes a mirrored copy of existing traffic to fingerprint devices, protocols and firmware without adding a single packet. That makes passive observation the accepted method for operational technology such as programmable logic controllers that may fault on unexpected traffic.
Its limitation is coverage: a device that stays silent during the capture window never appears, and versions can only be inferred from what the protocol reveals. Turning down the intensity of an active scan lowers the risk but does not remove it, and an authenticated scan still sends traffic the device may not expect.
Medical devices under regulatory approval are a similar case. When the hospital may not change their software and past port scans crashed them, the vulnerability picture is built from passive identification plus the vendor's advisories and component inventory, and the remaining risk is handled with strict segmentation and monitoring. Dropping the devices from the program only creates a blind spot.
Scheduling and performance are the other operational levers. If a daytime authenticated scan saturated a hypervisor and broke a trading application, the answer is an agreed low-activity window, caps on concurrent hosts and checks per host, and splitting the estate into batches so all of it is still covered each cycle.
Dropping credentials reduces accuracy rather than load, and scanning once a year abandons coverage.
Check yourself
1. On a plant network, the vendor documents that the programmable logic controllers may fault when they receive unexpected traffic, and the contract forbids active probing of them. The analyst must still obtain vulnerability information about these devices. Which approach fits, and what is its limitation?
2. A hospital's infusion pumps and imaging consoles are vendor-maintained, carry regulatory approval that forbids the hospital from altering their software, and have crashed during past port scans. Clinical engineering still owes the security committee a vulnerability picture for them. Which approach is appropriate?
Facts checked 2026-11-15 · Sources: CompTIA: CySA+ (CS0-004) certification and exam objectives, NIST SP 800-115: Technical Guide to Information Security Testing and Assessment
CompTIA CySA+ cheat sheet: every key fact on one page →