logind_session_timeout is misaligned with DISA #12561
Labels
blocked
Issue that can't be fixed in content.
productization-issue
Issue found in upstream stabilization process.
RHEL8
Red Hat Enterprise Linux 8 product related.
STIG
STIG Benchmark related.
Comments
jan-cerny
added
productization-issue
jan-cerny
added a commit
to jan-cerny/contest
that referenced
this issue
Nov 1, 2024
|
Since we can't do anything should this have the "blocked" label? |
comps
pushed a commit
to RHSecurityCompliance/contest
that referenced
this issue
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem:
The rule logind_session_timeout is misaligned with DISA. It passes with ComplianceAsCode but fails with DISA content.
The problem seems to be that the DISA's prose to set the timeout to 10 minutes, which means to set
StopIdleSessionSecoption to 600, and our content sets this to 600 but the DISA's OVAL checks that theStopIdleSessionSecoption is set to 900.We have discovered this problem in upstream productization.
Details:
This content is not aligned with content from DISA
The misalignment affects these profiles:
RHEL 8 STIG
The misalignment affects these rules:
logind_session_timeout
Outcome:
SCAP Security Guide Version:
current upstream master as of 2024-11-01 as of 3b29795
External Content's Version:
V2R1
The text was updated successfully, but these errors were encountered: