Why is it critical to have separate sensor update policies for Windows/Mac/*nix?

Question

Options

• AThere may be special considerations for each OS
• BTo assist with testing and tracking sensor rollouts
• CThe network protocols are different for each host OS
• DIt is an auditing requirement

• A
  91% (30)
• B
  6% (2)
• D
  3% (1)

Explanation

Separate sensor update policies per OS exist because each operating system has unique kernel architectures, file system structures, driver models, and security subsystems that can interact differently with security sensor software - a sensor update that is stable on Windows may cause kernel panics or service disruptions on Linux. Option A is correct because these OS-specific technical considerations (compatibility testing, staged rollout by platform, dependency requirements) make a unified policy risky and impractical.

Option B is a tempting partial truth - separate policies do aid tracking and rollout visibility - but that is a secondary benefit, not the primary reason; the underlying driver is OS compatibility, not test management. Option C is incorrect because network protocols used to deliver sensor updates are generally the same (HTTPS/TLS) regardless of host OS. Option D is incorrect because this is an operational/engineering best practice, not an audit or compliance mandate.

Memory tip: Think "different engines need different oil" - each OS runs on a fundamentally different "engine," so a one-size-fits-all update policy risks breaking the sensor on platforms it wasn't validated for.

No community discussion yet for this question.