server-security

Auditing Linux server security configuration drift requires comparing current firewall, Docker, and systemd states against an expected baseline. This skill runs a read-only checks script to detect exposure and hardening gaps, producing a severity-ranked report highlighting true regressions.

Checking Docker container hardening and systemd security on a production server involves running read-only audits to detect misconfigurations. This skill inspects service states, container isolation, and host hardening, generating a staged remediation workflow with safe options first.

Baseline drift detection for server security audits works by comparing live system checks against an expected-state reference and an accepted-risks list. This isolates true regressions from known accepted issues, ensuring the final severity-ranked report focuses only on new hardening gaps.

You can audit Cloudflare Access enforcement and Tailscale SSH hygiene on an Ubuntu server using bundled read-only checks. The skill validates tunnel health, firewall ports, and SSH key configurations, returning findings in a severity-ranked report for immediate action.

You need root access via sudo to perform a comprehensive server security audit, as the checks inspect systemd, firewall rules, and Docker states. The guided remediation workflow applies approved fixes one at a time with impact reasoning and verification.

The limitation of read-only server security audits is that they identify configuration drift and exposure but do not automatically apply changes. Remediation requires explicit approval through a guided workflow that applies fixes one at a time with impact reasoning and verification.