Verify Group Ownership of System Login Banner
Ensures /etc/issue (local login banner) is group-owned by GID 0 (root).
Checked against a path’s metadata, mode, owner, group, SUID/SGID.
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
/etc/issue is the pre-login banner shown on local/console logins; many organizations are legally required to display approved use-notification text. If the file is group-owned by a non-root group (GID ≠ 0), unprivileged users could tamper with the banner, removing or altering the mandated legal warning. Group ownership by root ensures only root can change it.
What Pavois checks
Pavois asks the file resource for the resolved numeric gid of /etc/issue and requires it to be 0. The check is skipped if the file is absent. Reading the file's effective group ownership directly (the kernel-resolved gid) is exact and avoids name-resolution ambiguity.
only_if { file('/etc/issue').exist? }
describe file('/etc/issue') do
its('gid') { should eq 0 }
endHow to verify it is applied
Run stat -c '%G %g' /etc/issue. Expected: group root and gid 0. ls -l /etc/issue shows the group in the owner column.
Inspect & investigate
- Inspect ownership:
stat -c '%U %G %a' /etc/issueorls -l /etc/issue. - View the banner content:
cat /etc/issue. - If auditd watches the file, changes appear in
/var/log/audit/audit.log.
Remediation
No automated remediation is shipped for this rule. Fix it manually with chgrp 0 /etc/issue (or chgrp root /etc/issue) to restore root group ownership, then re-run the scan.
Pavois applies this with its own harden engine, the plan below, not a shell script:
| group | root |
|---|---|
| path | /etc/issue |
| resource | file |
pavois harden plan localwhere the target is local, a user@host SSH alias, or a container , Docs
Impact & precautions
Wrong group ownership lets unprivileged users edit the mandated login banner, a compliance and legal-notice gap rather than a direct breach. The chgrp fix is trivial and safe; it does not change the banner text, only who may modify the file.
Standards mapping
| Standard | Reference | Type | Version | Confidence |
|---|---|---|---|---|
| CIS | 1.6.5, 1.7.5 | direct | per OS, see the benchmark table | high |
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.