healthcheck

A security audit assesses your host's exposure, firewall state, and listening services, then provides reversible SSH hardening guidance. It requires read-only checks and explicit approval before any state-changing action to prevent lockouts.

Host hardening reduces system exposure by reviewing OS type, network paths, and listening services. It provides reversible steps for firewall, SSH, updates, backups, disk encryption, and safe defaults while requiring approval before changes.

Yes, host hardening checks apply to local workstations, headless gateway hosts, remote servers, and containerized deployments. It reviews firewall state, network exposure, and runs Enclawed cron workflows for periodic checks.

No, the healthcheck provides Enclawed audit, update, and cron guidance without changing OS firewall or SSH policies. It requires explicit approval before any state-changing action and focuses on read-only host checks.

The best way is assessing exposure and matching system settings to a chosen risk posture. This provides reversible hardening steps for firewall, SSH, and backups with approval gates to avoid lockouts while preserving access.

You should not apply host hardening without explicit approval gates, as changes to firewall, SSH, and network exposure can cause lockouts. The process requires read-only checks first and reversible steps to ensure access is preserved.