OpenControls Logo

STIG Viewer

STIGViewer Support

SLEM 5 must use SSH to protect the confidentiality and integrity of transmitted information.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-261328SLEM-05-255015SV-261328r996453_ruleCCI-002418high
Description
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, logical means (cryptography) do not have to be employed, and vice versa.
STIGDate
SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide2025-05-08

Related Frameworks

4 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (7) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CRY-01Use of Cryptographic Controls
1.00
CRY-03Transmission Confidentiality
1.00
CRY-04Transmission Integrity
1.00
DCH-01Data Protection
1.00
CRY-01.1Alternate Physical Protection
0.50
CRY-01.3Pre/Post Transmission Handling
0.50
DCH-10Media Use
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (44) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-10Concurrent Session Control
1.00
AC-17(1)Monitoring and Control
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-3Access Enforcement
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00

+34 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.13.8
1.00
CCI4 mappings
CCI-002418
1.00
CCI-002420
1.00
CCI-002421
1.00
CCI-002422
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

PR.DS-02
1.00
PR.DS-01
0.50
PR.DS-10
0.50

Who does this work

8 NICE work roles and 7 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-261328r996453_chk)

Verify "sshd.service" is enabled and active by using the following command: > systemctl status sshd.service | grep -i active Active: active (running) since Wed 2023-11-29 09:49:45 MST; 2 months 23 days ago If "openssh.service" is not active, this is a finding.

Fix Text (F-64965r996452_fix)

Enable "openssh.service" to start automatically on reboot with the following command: > sudo systemctl enable sshd.service For the changes to take effect immediately, start the service with the following command: > sudo systemctl restart sshd.service