A county SOC reports that a full TCP connect scan across all ports saturated a fragile SCADA historian VLAN that was mistakenly treated as fair game. What is the soundest lesson for scan aggressiveness?
Select an answer to reveal the explanation.
Short Explanation
A fragile historian is a glass shelf, not a punching bag. Turn down timing and technique when RoE and system sensitivity say so — finishing every port fast is useless if you knock the shelf over. Louder is not automatically better.
Full Explanation
Scan aggressiveness must respect authorized scope, timing constraints, and the operational sensitivity of targets. Full TCP connect sweeps on all ports can overwhelm fragile OT or SCADA-adjacent systems even when the tester intends only enumeration. Fragility considerations belong in planning, not after damage. Traceroute visibility alone never expands authorization.