Skip to content

Update OL09-00-000242 STIG ID status as pending #14799

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.

Sign up for GitHub

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

Merged
Mab879 merged 1 commit into from
Jun 15, 2026
+8 −4
Merged

Update OL09-00-000242 STIG ID status as pending #14799

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions controls/stig_ol9.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
- id: OL09-00-000001
levels:
- medium
title: The OL 9 operating system must implement cryptographic mechanisms to prevent unauthorized

Check failure on line 26 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

26:100 [line-length] line too long (102 > 99 characters)
modification of all information at rest.
rules:
- encrypt_partitions
Expand All @@ -40,7 +40,7 @@
- id: OL09-00-000015
levels:
- medium
title: OL 9 vendor packaged system security patches and updates must be installed and up to date.

Check failure on line 43 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

43:100 [line-length] line too long (103 > 99 characters)
rules:
- security_patches_up_to_date
status: automated
Expand All @@ -48,7 +48,7 @@
- id: OL09-00-000090
levels:
- medium
title: OL 9 must display the Standard Mandatory DOD Notice and Consent Banner before granting local

Check failure on line 51 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

51:100 [line-length] line too long (105 > 99 characters)
or remote access to the system via a command line user logon.
rules:
- banner_etc_issue
Expand All @@ -69,7 +69,7 @@
- low
title: OL 9 must enable the hardware random number generator entropy gatherer service.
related_rules:
- service_rngd_enabled # This rule is causing test failures, See https://github.com/ComplianceAsCode/content/pull/10153

Check failure on line 72 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

72:100 [line-length] line too long (130 > 99 characters)
status: pending

- id: OL09-00-002400
Expand Down Expand Up @@ -123,7 +123,7 @@
- id: OL09-00-000050
levels:
- high
title: OL 9 must require a unique superusers name upon booting into single-user and maintenance

Check failure on line 126 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

126:100 [line-length] line too long (101 > 99 characters)
modes.
rules:
- grub2_admin_username
Expand Down Expand Up @@ -220,7 +220,7 @@
- id: OL09-00-002401
levels:
- medium
title: OL 9 must enable kernel parameters to enforce discretionary access control on hardlinks.

Check failure on line 223 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

223:100 [line-length] line too long (101 > 99 characters)
rules:
- sysctl_fs_protected_hardlinks
status: automated
Expand All @@ -228,7 +228,7 @@
- id: OL09-00-002402
levels:
- medium
title: OL 9 must enable kernel parameters to enforce discretionary access control on symlinks.

Check failure on line 231 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

231:100 [line-length] line too long (100 > 99 characters)
rules:
- sysctl_fs_protected_symlinks
status: automated
Expand Down Expand Up @@ -284,7 +284,7 @@
- id: OL09-00-002423
levels:
- medium
title: OL 9 must implement address space layout randomization (ASLR) to protect its memory from

Check failure on line 287 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

287:100 [line-length] line too long (101 > 99 characters)
unauthorized code execution.
rules:
- sysctl_kernel_randomize_va_space
Expand Down Expand Up @@ -365,7 +365,7 @@
- id: OL09-00-000497
levels:
- high
title: OL 9 must check the GPG signature of software packages originating from external software

Check failure on line 368 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

368:100 [line-length] line too long (102 > 99 characters)
repositories before installation.
rules:
- ensure_gpgcheck_globally_activated
Expand All @@ -374,7 +374,7 @@
- id: OL09-00-000496
levels:
- high
title: OL 9 must check the GPG signature of locally installed software packages before installation.

Check failure on line 377 in controls/stig_ol9.yml

View workflow job for this annotation

GitHub Actions / Yaml Lint on Changed yaml files 

377:100 [line-length] line too long (106 > 99 characters)
rules:
- ensure_gpgcheck_local_packages
status: automated
Expand Down Expand Up @@ -3800,10 +3800,14 @@
levels:
- high
title: OL 9 crypto policy must not be overridden.
rules:
- fips_crypto_policy_symlinks
- fips_crypto_policy_symlinks.severity=high
status: automated
notes: Rules for this control are intentionally not implemented. Checking whether files under /etc/crypto-policies/back-ends/
are symlinks is not an appropriate way to verify the consistency of the system's cryptographic settings.
The suggested fix mentioned in the STIG does not fully satisfy its own requirements, as it also symlinks the nss.config file.
Furthermore, running sudo 'update-crypto-policies --set FIPS' is not a reliable way to ensure FIPS compliance. Customers should
refer to the official Oracle Linux Documentation and use the 'fips=1' kernel option during system installation to ensure the system is
in FIPS mode.
More information https://docs.oracle.com/en/operating-systems/oracle-linux/9/security/configuring_fips_mode.html
status: pending

- id: OL09-00-000241
levels:
Expand Down
Loading