A transit engagement finds both Linux and Windows local privilege escalations. How should reporting best help different system owners?
Select an answer to reveal the explanation.
Short Explanation
Linux and Windows teams fix different things with different playbooks. Split the write-ups so each owner sees their root causes and fixes—not one blurry 'you got owned' paragraph.
Full Explanation
Clear reporting separates operating-system contexts because root causes and remediations differ: capabilities, sudo, and cron patterns on Linux versus services, tokens, and patch classes on Windows. Owners can act faster when findings map to their platforms with concrete hardening guidance. Bundling everything into a single vague elevation note slows remediation and muddies residual risk. Professional CPTS-style delivery keeps evidence organized by audience.