Default SSH Service State in Kali Linux Installation

The goal is to evaluate whether the current default of leaving the SSH service disabled after installation remains appropriate for all Kali Linux use cases, particularly headless or automated deployments where remote access is expected.

This evaluation must balance the documented hardening recommendation that prevents accidental public exposure against the operational need for immediate SSH availability in controlled environments, considering that the openssh‑server binaries are already present and functional.

What are the risks and benefits of changing the default to enabled for specific installation profiles? How would such a change align with or deviate from the existing hardening guide? Should the metapackage provide a conditional enable based on the selected installation mode?