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

Rule descriptions not up-to-date with the latest STIG #12088

Closed
0intro opened this issue Jun 24, 2024 · 1 comment · Fixed by #12373
Closed

Rule descriptions not up-to-date with the latest STIG #12088

0intro opened this issue Jun 24, 2024 · 1 comment · Fixed by #12373

Comments

@0intro
Copy link
Contributor

0intro commented Jun 24, 2024

Description of problem:

The rule descriptions are not up-to-date with the latest STIG.

For example, after the update of the RHEL 9 STIG, the policy/stig/shared.yml description of the sysctl_kernel_yama_ptrace_scope rule was updated:

But the vuln_discussion section is duplicated. The first one is the previous one and the new one appears at the end of the file.

vuldiscussion: |-
    Unrestricted usage of ptrace allows compromised binaries to run ptrace on another processes of the user. Like this, the attacker can steal
    sensitive information from the target processes (e.g. SSH sessions, web browser, etc) without any additional assistance from the user (i.e. without resorting to phishing).

[...]

vuln_discussion: |-
    Unrestricted usage of ptrace allows compromised binaries to run ptrace on other processes of the user. Like this, the attacker can steal sensitive information from the target processes (e.g., SSH sessions, web browser, etc.) without any additional assistance from the user (i.e., without resorting to phishing).

And the rule.yml description was not updated:

rationale: |
    Unrestricted usage of ptrace allows compromised binaries to run ptrace
    on another processes of the user. Like this, the attacker can steal
    sensitive information from the target processes (e.g. SSH sessions, web browser, ...)
    without any additional assistance from the user (i.e. without resorting to phishing).

SCAP Security Guide Version:

master branch as of 2024-06-24 (644de12).

@Mab879
Copy link
Member

Mab879 commented Jun 26, 2024

Thanks for opening this issue.

We have a script to update the policy files ./utils/import_disa_stig.py .

It's basic and requires manual review but it helps a lot.

We usually don't update the description or rationale due to DISA's changes.

I will make a note to update these files once DISA releases a new version. Which should be in late July.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants