The Photon operating system must monitor remote access logins.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-258805	SRG-OS-000032-GPOS-00013	PHTN-40-000012	SV-258805r958406_rule	2024-07-11	2

Description
Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best. 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. Automated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).

Description

Remote access services, such as those providing remote access to network devices and information systems, which lack automated monitoring capabilities, increase risk and make remote user access management difficult at best. 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. Automated monitoring of remote access sessions allows organizations to detect cyberattacks and also ensure ongoing compliance with remote access policies by auditing connection activities of remote access capabilities, such as Remote Desktop Protocol (RDP), on a variety of information system components (e.g., servers, workstations, notebook computers, smartphones, and tablets).

ℹ️ Check
If another package is used to offload logs, such as syslog-ng, and is properly configured, this is not applicable. At the command line, run the following command to verify rsyslog is configured to log authentication requests: # grep -E "(^auth.\|^authpriv.\|^daemon.)" /etc/rsyslog.conf Example result: auth.;authpriv.;daemon. /var/log/audit/sshinfo.log If "auth.", "authpriv.", and "daemon.*" are not configured to be logged, this is a finding.

ℹ️ Check

If another package is used to offload logs, such as syslog-ng, and is properly configured, this is not applicable. At the command line, run the following command to verify rsyslog is configured to log authentication requests: # grep -E "(^auth.*|^authpriv.*|^daemon.*)" /etc/rsyslog.conf Example result: auth.*;authpriv.*;daemon.* /var/log/audit/sshinfo.log If "auth.*", "authpriv.*", and "daemon.*" are not configured to be logged, this is a finding.

✔️ Fix
Navigate to and open: /etc/rsyslog.conf Add or update the following line: auth.;authpriv.;daemon.* /var/log/audit/sshinfo.log Note: The path can be substituted for another suitable log destination dedicated to authentication logs. At the command line, run the following command: # systemctl restart rsyslog.service