SV-270666r1066487: Ubuntu 24.04 LTS must use SSH to protect the confidentiality and integrity of transmitted information. | Canonical Ubuntu 24.04 LTS STIG SCAP Benchmark

Loading benchmark…

Assessment Title

Rule Text

Ubuntu 24.04 LTS must use SSH to protect the confidentiality and integrity of transmitted information.

Description

Discussion Text

Without protection of the transmitted information, confidentiality and integrity may be compromised because unprotected communications can be intercepted and either read or altered. This requirement applies to both internal and external networks and all types of information system components from which information can be transmitted (e.g., servers, mobile devices, notebook computers, printers, copiers, scanners, and facsimile machines). Communication paths outside the physical protection of a controlled boundary are exposed to the possibility of interception and modification. Protecting the confidentiality and integrity of organizational information can be accomplished by physical means (e.g., employing physical distribution systems) or by logical means (e.g., employing cryptographic techniques). If physical means of protection are employed, then logical means (cryptography) do not have to be employed, and vice versa. Satisfies: SRG-OS-000423-GPOS-00187, SRG-OS-000425-GPOS-00189, SRG-OS-000426-GPOS-00190

How this relates to the STIG checklist: STIG vs SCAP benchmark.

IA Controls

NIST SP 800-53

Not mappedCCI-002418Not mappedCCI-002420Not mappedCCI-002422

References

DPMS Target Canonical Ubuntu 24.04 LTS DISA DPMS Target Canonical Ubuntu 24.04 LTS 5673

SCC Automation Reference

The reconstructed evaluation script behind this rule's OVAL check(s) — every module a compound check combines, with this rule's own concrete values and DISA's SCC tool's real per-module mechanism curated from static teardown of SCC releases.

#!/bin/bash
# Reconstructed from oval:mil.disa.stig.ubuntu2404os:def:270666
# Ubuntu 24.04 LTS must use SSH to protect the confidentiality and integrity of transmitted information.
# Per-module read mechanism curated from static teardown of DISA's SCC tool
# (SCAP Compliance Checker) -- see the SCC Automation Reference above.

# ssh.service is active
# systemdunitproperty_object (systemdunitproperty_test)
test_1() {
  (systemctl show -p 'ActiveState' --value 'ssh.service') | grep -qxF 'active'
}
# ssh.service is enabled
# systemdunitproperty_object (systemdunitproperty_test)
test_2() {
  (systemctl show -p 'UnitFileState' --value 'ssh.service') | grep -qxF 'enabled'
}

if ( test_1 && test_2 ); then
  echo "PASS"
else
  echo "FAIL"
fi

Assessment Script Powered by AISandbox-executed

A standalone Shell script to assess this control automatically. Review before running it in your environment.

Syntax-checked and actually executed in an isolated sandbox (not the real system this checks) — confirmed to run without errors.

#!/bin/sh
# OVAL Definition: oval:mil.disa.stig.ubuntu2404os:def:270666


if ! command -v systemctl &> /dev/null; then
  echo "FAIL"
  exit 1
fi

if systemctl is-active --quiet ssh.service; then
  echo_result="PASS"
else
  echo_result="FAIL"
fi
echo "$echo_result"
exit ${echo_result=="PASS"?0:1}

if systemctl is-enabled --quiet ssh.service; then
  echo_result=${echo_result}" PASS"
else
  echo_result=${echo_result}" FAIL"
fi
echo "$echo_result"
exit ${echo_result=="PASS PASS"?0:1}

Remediation

Enable the "ssh" service to start automatically on reboot with the following command: 
 
$ sudo systemctl enable ssh.service 
 
ensure the "ssh" service is running 
 
$ sudo systemctl start ssh.service