Linux Server Hardening taste — ChatGPT prompt: how to use
Linux Server Hardening taste — a prompt for ChatGPT provides an operations engineering ruleset for hardening Linux servers. It guides base image setup, SSH access policies, and automated configuration via Ansible or cloud-init.
CC0-1.0 ★ 178,201 updated 2026-10-24
Open on GitHubWhat Linux Server Hardening taste does
The prompt establishes Linux host hardening guidelines tagged with confidence scores from 0.65 to 0.95. It dictates building from minimal base images, stripping compilers from production machines, tracking configurations via code, and enforcing key or certificate authentication over SSH without root logins.
The rules cover network perimeter defenses, unprivileged system accounts, systemd sandboxing parameters (ProtectSystem=strict, NoNewPrivileges=yes, PrivateTmp=yes), enforcing SELinux or AppArmor profiles, and shipping logs off-host. Partition mounting relies on noexec, nosuid, and nodev where supported, alongside disk encryption and isolated backup storage. Compromised or drifted servers are marked for total rebuilds rather than manual in-place fixes.
What it helps with
- strip compilers and extra packages from production base images
- enforce SSH key or certificate authentication while disabling root login
- sandbox long-running systemd services with strict isolation directives
- monitor sudoers modifications and privileged commands using
auditd
Example prompts for the agent
- Audit my
sshd_configusing the Linux Server Hardening taste prompt - Draft an Ansible playbook to configure a hardened Debian server
- Add systemd sandboxing options to a production service unit
How to install Linux Server Hardening taste
How to use
Paste the text at the start of a chat or into project instructions
Manually: put the files in place
.claude/commands/prompts.csv.mdQuestions about Linux Server Hardening taste
How to install Linux Server Hardening taste in ChatGPT?
Paste the prompt text directly into a ChatGPT conversation before configuring servers. In Claude Code, add it via the .claude/commands/prompts.csv.md file.
What does Linux Server Hardening taste do?
It guides language models on production Linux security practices. Recommendations include minimal base images, configuration management, strict SSH controls, firewall restrictions, and unprivileged daemon accounts.
Which service isolation settings does the prompt require?
It mandates systemd directives such as ProtectSystem=strict, NoNewPrivileges=yes, and PrivateTmp=yes. Services must run under dedicated unprivileged accounts without login shells.
Source text
prompts.csv · CC0-1.0
# Linux Server Hardening taste of a careful operations engineer - Build servers from a minimal base image and install only the packages a role needs, removing compilers and debugging tools from production hosts. Confidence: 0.85 - Manage every server with configuration as code (Ansible, cloud-init or an image pipeline) and never rely on manual changes that drift. Confidence: 0.90 - Disable SSH password authentication and root login, and allow only key-based or certificate-based logins. Confidence: 0.95 - Prefer short-lived SSH certificates or an identity-aware access proxy over long-lived authorized_keys files copied around. Confidence: 0.75 - Give each engineer a named account with sudo through groups, and never share a common admin user. Confidence: 0.90 - Default the host firewall to deny inbound traffic and open only the ports the service actually listens on. Confidence: 0.90 - Keep SSH and admin interfaces off the public internet, reachable only through a VPN, bastion or private network. Confidence: 0.85 - Enable unattended security updates for the base OS, and schedule reboots so kernel patches actually take effect. Confidence: 0.85 - Run each service as its own unprivileged system user with no login shell. Confidence: 0.90 - Use systemd sandboxing options such as `ProtectSystem=strict`, `NoNewPrivileges=yes` and `PrivateTmp=yes` for every long-running service. Confidence: 0.80 - Keep SELinux or AppArmor in enforcing mode and write a policy exception instead of disabling it when something breaks. Confidence: 0.75 - Ship logs, including auth and audit logs, to a central store so an attacker on the host cannot erase the trail. Confidence: 0.90 - Enable `auditd` rules for privileged commands, changes to sudoers and edits under `/etc`. Confidence: 0.70 - Keep secrets out of files in the repo and on disk where possible; fetch them at runtime from a secrets manager with scoped access. Confidence: 0.85 - Mount `/tmp` and data volumes with `noexec`, `nosuid` and `nodev` wherever the workload allows it. Confidence: 0.65 - Apply sysctl hardening such as disabling IP forwarding and ICMP redirects on hosts that are not routers. Confidence: 0.70 - Rate-limit authentication attempts with fail2ban or the platform equivalent on any exposed login service. Confidence: 0.70 - Encrypt disks at rest and protect backups with separate credentials that the server itself cannot use to delete them. Confidence: 0.85 - Scan hosts regularly against a CIS benchmark or similar baseline and track findings like any other bug. Confidence: 0.75 - Prefer replacing a compromised or drifted server with a freshly built one over trying to clean it in place. Confidence: 0.90 - Keep accurate time with NTP or chrony on every host so logs, certificates and tokens line up. Confidence: 0.80
© f · CC0-1.0 · f/prompts.chat