Ansible on Rocky Linux 9.5: SELinux Targeted Policy Hardening Complete Guide

Rocky Linux 9.5 (Linux 5.14) reached general availability on 2024-11-19 and is supported with RHEL 9.5. CIQ-backed RHEL rebuild; Peridot build system. This guide shows how to automate selinux targeted policy hardening on Rocky Linux 9.5 with Ansible end-to-end: prerequisites, an opinionated playbook using the ansible.posix.selinux 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 SELinux Targeted Policy Hardening on Rocky Linux 9.5

Rocky Linux 9.5 is a workhorse for production Linux. Hand-rolling shell scripts for selinux targeted policy hardening drifts within weeks. Ansible's ansible.posix.selinux module gives you idempotent state management, dry-run with --check, and rollback via inventory.

See also: Ansible on AlmaLinux 9.5: SELinux Targeted Policy Hardening Complete Guide

Prerequisites

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

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

SELinux Targeted Policy Hardening playbook

Inventory

[rocky-linux-9-5]
host01.example.com
[rocky-linux-9-5:vars]
ansible_connection=ssh
ansible_user=ansible
ansible_become=true
ansible_become_method=sudo

Playbook

---
- name: Harden SELinux targeted on Rocky Linux 9.5
  hosts: rocky-linux-9-5
  tasks:
    - name: Enforce targeted policy
      ansible.posix.selinux:
        policy: targeted
        state: enforcing
    - name: Disable risky booleans
      ansible.posix.seboolean:
        name: '{{ item }}'
        state: false
        persistent: true
      loop: [httpd_can_sendmail, ftpd_full_access, samba_export_all_rw]
    - name: Enable httpd → network for reverse proxies
      ansible.posix.seboolean:
        name: httpd_can_network_connect
        state: true
        persistent: true

See also: Ansible on Oracle Linux 9.5: SELinux Targeted Policy Hardening Complete Guide

Validation

ansible-playbook -i inventory/rocky-linux-9-5.ini selinux-targeted-policy-hardening.yml --check --diff
ansible-playbook -i inventory/rocky-linux-9-5.ini selinux-targeted-policy-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 Red Hat Enterprise Linux 8.10: SELinux Targeted Policy Hardening Complete Guide

FAQ

Q. Which ansible-core release should I use with Rocky Linux 9.5? 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.posix.selinux 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 selinux targeted policy 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 • configuring WinRM for Ansible • Ansible 13 breaking-changes reference • configuring Ansible connection variables

Conclusion

Rocky Linux 9.5 (Linux 5.14) is a first-class Ansible target for selinux targeted policy hardening. Standardize on ansible-core 2.18 LTS plus the ansible.posix 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.