RHEL 8 must be able to initiate directly a session lock for all connection types using smartcard when the smartcard is removed.
An XCCDF Rule
Description
<VulnDiscussion>A session lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not want to log out because of the temporary nature of the absence. The session lock is implemented at the point where session activity can be determined. Rather than be forced to wait for a period of time to expire before the user session can be locked, RHEL 8 needs to provide users with the ability to manually invoke a session lock so users can secure their session if it is necessary to temporarily vacate the immediate physical vicinity. Satisfies: SRG-OS-000028-GPOS-00009, SRG-OS-000030-GPOS-00011</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-230351r792899_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Configure the operating system to enable a user's session lock until that user re-establishes access using established identification and authentication procedures.
Select/Create an authselect profile and incorporate the "with-smartcard-lock-on-removal" feature with the following example:
$ sudo authselect select sssd with-smartcard with-smartcard-lock-on-removal