Ensure /etc/issue.net is configured
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-ubuntu2004-v300-1-6-3 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Ubuntu2004 V300 1 6 3?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-ubuntu2004-v300-1-6-3)More formats (shields.io, HTML) on the badges page.
---
name: cis-ubuntu2004-v300-1-6-3
description: "Ensure /etc/issue.net is configured"
category: cis-networking
version: "3.0.0"
author: cyberstrike-official
tags: [cis, ubuntu, linux, ubuntu-20.04, banners, issue-net, warning, remote]
cis_id: "1.6.3"
cis_benchmark: "CIS Ubuntu Linux 20.04 LTS Benchmark v3.0.0"
tech_stack: [ubuntu, linux]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 1.6.3 Ensure /etc/issue.net is configured (Automated)
## Profile
- Level 1 - Server
- Level 1 - Workstation
## Description
The contents of the `/etc/issue.net` file are displayed to users prior to login for remote connections from configured services.
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
## 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:
```bash
# cat /etc/issue.net
```
Run the following command and verify no results are returned:
```bash
# grep -E -i "(\\\v|\\\r|\\\m|\\\s|$(grep '^ID=' /etc/os-release | cut -d= -f2 | sed -e 's/"//g'))" /etc/issue.net
```
## Expected Result
- Contents of `/etc/issue.net` should match site policy
- No results should be returned from the grep command (no system information exposed)
## Remediation
### Command Line
Edit the `/etc/issue.net` file with the appropriate contents according to your site policy, remove any instances of `\m`, `\r`, `\s`, `\v` or references to the `OS platform`.
Example:
```bash
# echo "Authorized users only. All activity may be monitored and reported." > /etc/issue.net
```
## References
1. NIST SP 800-53 Rev. 5: CM-6, CM-1, CM-3
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------- | ---- | ---- | ---- |
| v8 | 0.0 Explicitly Not Mapped | | | |
| v7 | 0.0 Explicitly Not Mapped | | | |
MITRE ATT&CK Mappings: T1018, T1018.000, T1082, T1082.000, T1592, T1592.004 | TA0007
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!