Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Files are correct but Inspec isn't parsing right #44

Open
jrmetzger opened this issue Jan 17, 2025 · 0 comments
Open

Files are correct but Inspec isn't parsing right #44

jrmetzger opened this issue Jan 17, 2025 · 0 comments
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed invalid This doesn't seem right

Comments

@jrmetzger
Copy link
Contributor

jrmetzger commented Jan 17, 2025

SV-230423:
  justification: Line is correct, but Inspec not parsing correctly - Successful/unsuccessful uses of the mount command in RHEL 8 must generate an audit record.
  run: false
SV-230466:
  justification: Line is correct, but Inspec not parsing correctly - Successful/unsuccessful modifications to the faillock log file in RHEL 8 must generate an audit record.
  run: false
SV-230345:
  justification: Line is correct, but Inspec not parsing correctly - RHEL 8 must include root when automatically locking an account until the locked account is released by an administrator when three unsuccessful logon attempts occur during a 15-minute time period.'
  run: false
SV-230251:
  justification: Line is correct, but Inspec not parsing correctly - The RHEL 8 SSH server must be configured to use only Message Authentication Codes (MACs) employing FIPS 140-2 validated cryptographic hash algorithms.
  run: false
SV-230228:
  justification: Line is correct, but Inspec not parsing correctly - All RHEL 8 remote access methods must be monitored.
  run: false
SV-237643:
  justification: Only once in /etc/sudoers and /etc/sudoers/* - RHEL 8 must require re-authentication when using the "sudo" command.
  run: false
SV-230484:
  justification: Duplicating the line to check for some reason? - RHEL 8 must securely compare internal information system clocks at least every 24 hours with a server synchronized to an authoritative time source, such as the United States Naval Observatory (USNO) time servers, or a time server designated for the appropriate DoD network (NIPRNet/SIPRNet), and/or the Global Positioning System (GPS).
  run: false
@jrmetzger jrmetzger added bug Something isn't working help wanted Extra attention is needed invalid This doesn't seem right labels Jan 17, 2025
@jrmetzger jrmetzger self-assigned this Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant