Release readiness checklist
Check whether a scoped change is ready to ship and what still needs verification.
5,186,122 AI resources indexedWorking toward the world’s largest AI resource index.
Ensure nftables loopback traffic is configured
---
name: cis-ubuntu1804-v220-3-4-2-6-d52864fae953
description: "Ensure nftables loopback traffic is configured"
category: cis-networking
version: "2.2.0"
author: cyberstrike-official
tags: [cis, ubuntu, linux, ubuntu-18.04, networking, firewall, nftables]
cis_id: "3.4.2.6"
cis_benchmark: "CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0"
tech_stack: [ubuntu, linux]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0 - Control 3.4.2.6
## Description
Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network.
## Rationale
Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.
## Impact
None.
## Audit Procedure
### Command Line
Run the following commands to verify that the loopback interface is configured:
Run the following command to verify the loopback interface is configured to accept network traffic:
```bash
nft list ruleset | awk '/hook input/,/}/' | grep 'iif "lo" accept'
```
Example output:
```
iif "lo" accept
```
Run the following command to verify network traffic from an IPv4 loopback interface is configured to drop:
```bash
nft list ruleset | awk '/hook input/,/}/' | grep 'ip saddr'
```
Example output:
```
ip saddr 127.0.0.0/8 counter packets 0 bytes 0 drop
```
-IF- IPv6 is enabled on the system:
Run the following command to verify network traffic from an IPv6 loopback interface is configured to drop:
```bash
nft list ruleset | awk '/hook input/,/}/' | grep 'ip6 saddr'
```
Example output:
```
ip6 saddr ::1 counter packets 0 bytes 0 drop
```
## Expected Result
The loopback interface should accept traffic, and traffic from 127.0.0.0/8 (and ::1 for IPv6) should be dropped.
## Remediation
### Command Line
Run the following commands to implement the loopback rules:
```bash
nft add rule inet filter input iif lo accept
nft add rule inet filter input ip saddr 127.0.0.0/8 counter drop
```
-IF- IPv6 is enabled on the system:
Run the following command to implement the IPv6 loopback rule:
```bash
nft add rule inet filter input ip6 saddr ::1 counter drop
```
## Default Value
No loopback rules are configured by default.
## References
1. NIST SP 800-53 Rev. 5: CA-9, SC-7
2. CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0
## CIS Controls
Version 8
4.4 Implement and Manage a Firewall on Servers - Implement and manage a firewall on servers, where supported.
4.5 Implement and Manage a Firewall on End-User Devices - Implement and manage a host-based firewall or port-filtering tool on end-user devices.
Version 7
9.4 Apply Host-based Firewalls or Port Filtering - Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed.
## Profile Applicability
- Level 1 - Server
- Level 1 - Workstation
## Assessment Status
Automated
---
name: cis-ubuntu1804-v220-3-4-2-6-d52864fae953
description: "Ensure nftables loopback traffic is configured"
category: cis-networking
version: "2.2.0"
author: cyberstrike-official
tags: [cis, ubuntu, linux, ubuntu-18.04, networking, firewall, nftables]
cis_id: "3.4.2.6"
cis_benchmark: "CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0"
tech_stack: [ubuntu, linux]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0 - Control 3.4.2.6
## Description
Configure the loopback interface to accept traffic. Configure all other interfaces to deny traffic to the loopback network.
## Rationale
Loopback traffic is generated between processes on machine and is typically critical to operation of the system. The loopback interface is the only place that loopback network traffic should be seen, all other interfaces should ignore traffic on this network as an anti-spoofing measure.
## Impact
None.
## Audit Procedure
### Command Line
Run the following commands to verify that the loopback interface is configured:
Run the following command to verify the loopback interface is configured to accept network traffic:
```bash
nft list ruleset | awk '/hook input/,/}/' | grep 'iif "lo" accept'
```
Example output:
```
iif "lo" accept
```
Run the following command to verify network traffic from an IPv4 loopback interface is configured to drop:
```bash
nft list ruleset | awk '/hook input/,/}/' | grep 'ip saddr'
```
Example output:
```
ip saddr 127.0.0.0/8 counter packets 0 bytes 0 drop
```
-IF- IPv6 is enabled on the system:
Run the following command to verify network traffic from an IPv6 loopback interface is configured to drop:
```bash
nft list ruleset | awk '/hook input/,/}/' | grep 'ip6 saddr'
```
Example output:
```
ip6 saddr ::1 counter packets 0 bytes 0 drop
```
## Expected Result
The loopback interface should accept traffic, and traffic from 127.0.0.0/8 (and ::1 for IPv6) should be dropped.
## Remediation
### Command Line
Run the following commands to implement the loopback rules:
```bash
nft add rule inet filter input iif lo accept
nft add rule inet filter input ip saddr 127.0.0.0/8 counter drop
```
-IF- IPv6 is enabled on the system:
Run the following command to implement the IPv6 loopback rule:
```bash
nft add rule inet filter input ip6 saddr ::1 counter drop
```
## Default Value
No loopback rules are configured by default.
## References
1. NIST SP 800-53 Rev. 5: CA-9, SC-7
2. CIS Ubuntu Linux 18.04 LTS Benchmark v2.2.0
## CIS Controls
Version 8
4.4 Implement and Manage a Firewall on Servers - Implement and manage a firewall on servers, where supported.
4.5 Implement and Manage a Firewall on End-User Devices - Implement and manage a host-based firewall or port-filtering tool on end-user devices.
Version 7
9.4 Apply Host-based Firewalls or Port Filtering - Apply host-based firewalls or port filtering tools on end systems, with a default-deny rule that drops all traffic except those services and ports that are explicitly allowed.
## Profile Applicability
- Level 1 - Server
- Level 1 - Workstation
## Assessment Status
Automated
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.