STIGViewer Support

SLEM 5 must have the packages required for multifactor authentication to be installed.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-261396SLEM-05-612010SV-261396r996610_ruleCCI-001948medium
Description
Using an authentication device, such as a Common Access Card (CAC) or token separate from the information system, ensures that even if the information system is compromised, that compromise will not affect credentials stored on the authentication device. Multifactor solutions that require devices separate from information systems gaining access include, for example, hardware tokens providing time-based or challenge-response authenticators and smart cards such as the U.S. Government Personal Identity Verification (PIV) card and the DOD CAC. A privileged account is defined as an information system account with authorizations of a privileged user. Remote access 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. This requirement only applies to components where this is specific to the function of the device or has the concept of an organizational user (e.g., VPN, proxy capability). This does not apply to authentication for the purpose of configuring the device itself (management).
STIGDate
SUSE Linux Enterprise Micro (SLEM) 5 Security Technical Implementation Guide2026-02-10

Related Frameworks

1 mapping across 2 frameworks
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (12) 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.

IA-2Identification and Authentication (Organizational Users)
1.00
IA-2(1)Multi-factor Authentication to Privileged Accounts
1.00
IA-2(11)Remote Access — Separate Device
1.00
IA-2(12)Acceptance of PIV Credentials
1.00
IA-2(2)Multi-factor Authentication to Non-privileged Accounts
1.00
IA-2(3)Local Access to Privileged Accounts
1.00
IA-2(4)Local Access to Non-privileged Accounts
1.00
IA-2(6)Access to Accounts —separate Device
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-5(2)Public Key-based Authentication
1.00

+2 more (top 10 by confidence shown)

CCI1 mapping

Details

Check Text (C-261396r996610_chk)

Verify SLEM 5 has the packages required for multifactor authentication installed. Check for the presence of the packages required to support multifactor authentication with the following commands: > zypper info pam_pkcs11 | grep -i installed Installed: Yes > zypper info mozilla-nss | grep -i installed Installed: Yes > zypper info mozilla-nss-tools | grep -i installed Installed: Yes > zypper info pcsc-ccid | grep -i installed Installed: Yes > zypper info pcsc-lite | grep -i installed Installed: Yes > zypper info pcsc-tools | grep -i installed Installed: Yes > zypper info opensc | grep -i installed Installed: Yes > zypper info coolkey | grep -i installed Installed: Yes If any of the packages required for multifactor authentication are not installed, this is a finding.

Fix Text (F-65033r996609_fix)

Configure SLEM 5 to implement multifactor authentication by installing the required packages. Install the packages required to support multifactor authentication with the following commands: > sudo transactional-update pkg install pam_pkcs11 > sudo reboot > sudo transactional-update pkg install mozilla-nss > sudo reboot > sudo transactional-update pkg install mozilla-nss-tools > sudo reboot > sudo transactional-update pkg install pcsc-ccid > sudo reboot > sudo transactional-update pkg install pcsc-lite > sudo reboot > sudo transactional-update pkg install pcsc-tools > sudo reboot > sudo transactional-update pkg install opensc > sudo reboot > sudo transactional-update pkg install coolkey > sudo reboot Additional information on the configuration of multifactor authentication on SLEM 5 can be found at https://www.suse.com/communities/blog/configuring-smart-card-authentication-suse-linux-enterprise/.