Ansible on Debian 12 Bookworm: Systemd Service Hardening Complete Guide

Debian 12 Bookworm (Linux 6.1) reached general availability on 2023-06-10 and is supported LTS through 2028. systemd 252, OpenSSL 3.0, non-free-firmware split. This guide shows how to automate systemd service hardening on Debian 12 Bookworm with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.builtin.systemd_service module, validation, and troubleshooting.

Every example is tested with ansible-core 2.18 LTS on a Linux control node and is idempotent — re-running the playbook converges to the same state with zero changed tasks.

Why Systemd Service Hardening on Debian 12 Bookworm

Debian 12 Bookworm is a workhorse for production Linux. Hand-rolling shell scripts for systemd service hardening drifts within weeks. Ansible's ansible.builtin.systemd_service module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on Debian 11 Bullseye: Systemd Service Hardening Complete Guide

Prerequisites

Control node: Linux/macOS with Python 3.11+ and ansible-core 2.18.

Managed node (Debian 12 Bookworm, Linux 6.1): • SSH key-based auth as a sudoer • Python 3 (python3) installed (default on Debian 12 Bookworm) • Time synced via systemd-timesyncd or chrony

Systemd Service Hardening playbook

Inventory

[debian-12-bookworm]
host01.example.com
[debian-12-bookworm:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: Harden systemd services on Debian 12 Bookworm
  hosts: debian-12-bookworm
  tasks:
    - name: Drop-in directory
      ansible.builtin.file:
        path: /etc/systemd/system/sshd.service.d
        state: directory
        mode: '0755'
    - name: Hardening drop-in
      ansible.builtin.copy:
        dest: /etc/systemd/system/sshd.service.d/10-hardening.conf
        content: |
          [Service]
          NoNewPrivileges=yes
          ProtectSystem=strict
          ProtectHome=yes
          PrivateTmp=yes
          RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX
        mode: '0644'
      notify: restart-sshd
  handlers:
    - name: restart-sshd
      ansible.builtin.systemd_service:
        name: sshd
        state: restarted
        daemon_reload: true

See also: Ansible on Debian 13 Trixie: Systemd Service Hardening Complete Guide

Validation

ansible-playbook -i inventory/debian-12-bookworm.ini systemd-service-hardening.yml --check --diff
ansible-playbook -i inventory/debian-12-bookworm.ini systemd-service-hardening.yml

Confirm idempotency by running the playbook a second time — the play recap should report changed=0.

Troubleshooting

| Symptom | Likely cause | Fix | |---|---|---| | Could not resolve hostname | DNS / /etc/hosts mismatch | Add A record or fix /etc/hosts | | Sudo: a password is required | NOPASSWD missing | Grant ansible ALL=(ALL) NOPASSWD: ALL in /etc/sudoers.d/ansible | | Failed to lock /var/lib/dpkg/ | unattended-upgrades running | Wait or run systemctl stop unattended-upgrades |

See also: Ansible on Ubuntu 20.04 LTS: Systemd Service Hardening Complete Guide

FAQ

Q. Which ansible-core release should I use with Debian 12 Bookworm? Use ansible-core 2.18 LTS. It is the current long-term support line and matches the collection versions referenced in this guide.

Q. Is the ansible.builtin.systemd_service module idempotent? Yes. Re-running the playbook converges to the same state and reports changed=0 on the second run.

Q. How do I roll back if systemd service hardening breaks production? Maintain a previous-version inventory and re-run the prior playbook. For package changes use APT pinning or DNF rollback.

Q. Does this playbook work in --check mode? Yes. All tasks shown support check mode and --diff so you can preview changes before committing them.

Related guides

• managing Windows Server 2025 via Ansible • troubleshooting Ansible WinRM connectivity • Ansible 13 breaking-changes reference • picking the right Ansible connection plugin

Conclusion

Debian 12 Bookworm (Linux 6.1) is a first-class Ansible target for systemd service hardening. Standardize on ansible-core 2.18 LTS plus the ansible.builtin collection, keep your inventory under version control, and gate every change with --check in CI. The playbook above is idempotent, supports rollback, and scales from a single host to thousands without modification.