A water utility domain still runs unsupported domain controllers. How should the tester prioritize that observation?
Select an answer to reveal the explanation.
Short Explanation
Domain controllers are the identity backbone — if they go soft, the whole building leans. Unsupported DCs mean missing fixes on the servers everyone trusts. Patch and support them first; workstation hygiene alone will not save the directory.
Full Explanation
Domain controllers authenticate and authorize the environment; unsupported or unpatched DCs concentrate systemic risk across the identity plane. Workstation patching does not remediate DC vulnerability classes. Treating DC hygiene as low priority or "offline security" misunderstands directory centrality. Assessments should elevate unsupported DCs as architecture-level findings with broad blast radius.