← Browse

@cyberstrikeus/cis-ubuntu1604-v200-1-7-2

B

Ensure local login warning banner is configured properly

skillclaude

Install

agr install @cyberstrikeus/cis-ubuntu1604-v200-1-7-2 --target claude

Writes 1 file into .claude/skills/, pinned to git-277fd933.

  • .claude/skills/cis-ubuntu1604-v200-1-7-2/SKILL.md

Document


name: cis-ubuntu1604-v200-1-7-2 description: "Ensure local login warning banner is configured properly" category: cis-iam version: "2.0.0" author: cyberstrike-official tags: [cis, ubuntu, linux, ubuntu-16.04, issue, banner, warning, login, local] cis_id: "1.7.2" cis_benchmark: "CIS Ubuntu Linux 16.04 LTS Benchmark v2.0.0" tech_stack: [ubuntu, linux] cwe_ids: [] chains_with: [] prerequisites: [] severity_boost: {}

CIS Ubuntu Linux 16.04 LTS Benchmark v2.0.0 - 1.7.2

Profile Applicability

  • Level 1 - Server
  • Level 1 - Workstation

Description

The contents of the /etc/issue file are displayed to users prior to login for local terminals.

Unix-based systems have typically displayed information about the OS release and patch level upon logging in to the system. This information can be useful to developers who are developing software for a particular OS platform. If mingetty(8) supports the following options, they display operating system information: \m - machine architecture \r - operating system release \s - operating system name \v - operating system version - or the operating system's name

Rationale

Warning messages inform users who are attempting to login to the system of their legal status regarding the system and must include the name of the organization that owns the system and any monitoring policies that are in place. Displaying OS and patch level information in login banners also has the side effect of providing detailed system information to attackers attempting to target specific exploits of a system. Authorized users can easily get this information by running the uname -a command once they have logged in.

Audit Procedure

Command Line

Run the following command and verify that the contents match site policy:

cat /etc/issue

Run the following command and verify no results are returned:

grep -E -i "(\\v|\\r|\\m|\\s|$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed -e 's/"//g'))" /etc/issue

Expected Result

The /etc/issue file should contain an appropriate warning banner without OS information references.

Remediation

Command Line

Edit the /etc/issue file with the appropriate contents according to your site policy, remove any instances of \m, \r, \s, \v or references to the OS platform:

echo "Authorized uses only. All activity may be monitored and reported." > /etc/issue

Default Value

Not applicable.

References

None.

CIS Controls

Controls VersionControl
v75.1 Establish Secure Configurations

Assessment Status

Automated

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicensecopyleft/unknown — index-and-link only

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-277fd93397902026-07-31