Remove ftp Package
Removes the insecure clear-text ftp client so credentials and files are never transferred unencrypted.
Checked against what is installed or registered, packages present/absent, account databases.
A mapping is a cross-reference to where each standard places this requirement, anchored and cross-validated, not a claim of equivalence. A passing check is evidence toward these references, how to read it.
Why this rule matters
The ftp client transmits data and authentication credentials in clear text, offering no confidentiality or integrity protection. Anyone able to observe the network can capture usernames, passwords and transferred files. Unless an FTP workflow is genuinely required, removing the client reduces the attack surface and prevents users from inadvertently using an insecure protocol; sftp/scp should be used instead.
What Pavois checks
Pavois asks the package manager via package('ftp') whether the client is installed, giving the effective state of the system rather than parsing dotfiles or scripts that might mention ftp. Only the package database reliably tells you whether the binary is actually present and runnable.
describe package('ftp') do
it { should_not be_installed }
endHow to verify it is applied
On Debian/Ubuntu run dpkg -s ftp (expect package 'ftp' is not installed); on RHEL-family run rpm -q ftp (expect package ftp is not installed). Either result confirms the rule passes.
Inspect & investigate
Verify removal with dpkg -s ftp or rpm -q ftp. Package-management actions are recorded in /var/log/dpkg.log (Debian/Ubuntu) or /var/log/dnf.log / dnf history (RHEL-family).
Remediation
Pavois's harden plan removes the ftp package (resource package, action remove) when you run pavois harden apply. No service is stopped because ftp is a client; only the binary is uninstalled.
Pavois applies this with its own harden engine, the plan below, not a shell script:
| action | remove |
|---|---|
| name | ftp |
| resource | package |
pavois harden plan localwhere the target is local, a user@host SSH alias, or a container , Docs
Impact & precautions
Impact of leaving it installed: clear-text transfers can leak credentials and data. Precaution before removing: confirm no scripts, cron jobs or batch jobs invoke the ftp command; migrate them to sftp/curl/lftp over TLS first. Removing the client is low-risk and does not affect a deliberately run FTP server package.
Standards mapping
| Standard | Reference | Type | Version | Confidence |
|---|---|---|---|---|
| CIS | 2.2.4, 2.2.6, 2.2.1 | direct | per OS, see the benchmark table | high |
| PCI DSS | 2.2.4 | supporting | 4.0.1 | medium |
Each reference is a cross-reference anchored in the upstream benchmark and cross-validated against the SCAP Security Guide and ansible-lockdown, not a claim of equivalence. Direct = a prescriptive, line-level requirement; supporting = an abstract control family (NIST) the check provides evidence toward. How to read a mapping.