ISO 27001 demands more than just moving data from one server to another. It demands documented controls, encryption in transit, integrity checks, and a traceable chain of custody. Rsync can be a strong foundation, but without the right safeguards and process, it can sink your compliance.
To align rsync with ISO 27001 requirements, you start with encryption. Wrap every rsync transfer in SSH, using strong ciphers and disabling outdated protocols. Set explicit --chmod flags to enforce permissions. Require key-based authentication and store private keys in a hardened location. Every piece matters, because an unsecured transfer path is an instant audit failure.
Logging is next. ISO 27001 is obsessed with evidence. Default rsync logs are minimal, so configure verbose modes and redirect output to append-only log files. Pair them with centralized logging so no local breach can wipe your records. Include transfer size, source, destination, user, and timestamp.
Access control is non-negotiable. Limit rsync accounts to the absolute minimum privileges. Create system users that can only access the needed directories. On the remote side, set --rsync-path="sudo -u restricted_rsync_user rsync" to enforce least privilege at the transport layer.