Vulnerability Discussion

Using an authentication device, such as a CAC or token that is 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 card and the DOD Common Access Card.

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).

This requires further clarification from NIST.

Check

Verify that the "pcscd" socket is active with the following command:

$ systemctl status pcscd.socket

pcscd.socket - PC/SC Smart Card Daemon Activation Socket
Loaded: loaded (/usr/lib/systemd/system/pcscd.socket; enabled; preset: enabled)
Active: active (listening) since Thu 2024-04-11 16:03:24 BST; 2 weeks 3 days ago
Triggers: pcscd.service
Listen: /run/pcscd/pcscd.comm (Stream)
CGroup: /system.slice/pcscd.socket

If the pcscd.socket is not active, this is a finding.

Fix

To enable pcscd run the following command:

$ systemctl enable --now pcscd.socket
$ systemctl enable --now pcscd.service

The pcscd service will be enabled when software tries to access the socket.