OpenControls Logo

STIG Viewer

STIGViewer Support

The IBM RACF SSH daemon must be configured to use a FIPS 140-3-compliant cryptographic algorithm to protect confidential information and remote access sessions.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-223807RACF-SH-000020SV-223807r1212322_ruleCCI-000068high
Description
Use of weak or untested encryption algorithms undermines the purposes of using encryption to protect data. Cryptographic modules must adhere to the higher standards approved by the federal government since this provides assurance they have been tested and validated. Remote access (e.g., RDP) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include, for example, dial-up, broadband, and wireless. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash.
STIGDate
IBM z/OS RACF Security Technical Implementation Guide2026-06-03

Related Frameworks

2 mappings across 4 frameworks
SCF0 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.

NET-14.2Protection of Confidentiality / Integrity Using Encryption
1.00
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (34) 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-17(1)Monitoring and Control
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
CM-6Configuration Settings
1.00
CM-6(1)Automated Management, Application, and Verification
1.00
CM-7Least Functionality
1.00
CM-7(1)Periodic Review
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-2(9)Network Access to Non-privileged Accounts — Replay Resistant
1.00
IA-3Device Identification and Authentication
1.00

+24 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.1.13
1.00
CCI2 mappings
CCI-000068
1.00
CCI-001453
1.00

Details

Check Text (C-223807r1212322_chk)

Locate the SSH daemon configuration file, which may be found in the /etc/ssh/ directory. Alternately: From the UNIX System Services ISPF Shell, navigate to ribbon select tools. Select option 1 - Work with Processes. If SSH Daemon is not active, this is not a finding. Examine the SSH daemon configuration file: sshd_config If there are no "Ciphers" lines, or the ciphers list contains any cipher not starting with "aes", this is a finding. If the MACs line is not configured to "hmac-sha1" or greater, this is a finding. Examine the z/OS-specific sshd server systemwide configuration: zos_sshd_config If any of the following is untrue, this is a finding. FIPSMODE=YES CiphersSource=ICSF MACsSource=ICSF

Fix Text (F-25468r1212321_fix)

Edit the SSH daemon configuration and remove any ciphers not starting with "aes". If necessary, add a "Ciphers" line using FIPS 140-3-compliant algorithms. Configure for message authentication to MACs "hmac-sha1" or greater. Edit the z/OS-specific sshd server systemwide configuration file configuration as follows: FIPSMODE=YES CiphersSource=ICSF MACsSource=ICSF