A municipal Windows host still runs a legacy file-sharing protocol required by one application. How should risk be framed?
Select an answer to reveal the explanation.
Short Explanation
Keeping an old file-sharing protocol for one app is like leaving a rickety bridge up because one truck still uses it. Maybe you need it for now—but say so, add guardrails, and plan the upgrade. Required doesn’t mean risk-free.
Full Explanation
Legacy protocols often lack modern authentication and encryption features and broaden the set of known attack techniques available to adversaries. Business dependency explains presence but does not erase exposure. Professional reporting acknowledges the constraint, notes compensating controls such as segmentation and monitoring, and recommends migration timelines. Treating necessity as zero risk leaves the municipality without a clear remediation narrative.