Remove chrony_set_nts from STIG profiles#14613
Merged
Mab879 merged 1 commit intoComplianceAsCode:masterfrom Apr 3, 2026
Merged
Remove chrony_set_nts from STIG profiles#14613Mab879 merged 1 commit intoComplianceAsCode:masterfrom
Mab879 merged 1 commit intoComplianceAsCode:masterfrom
Conversation
matusmarhefka
added
RHEL
Network Time Security (NTS) is not compatible with systems running in FIPS mode. Enabling NTS on a system in FIPS mode causes chronyd service to abort with a fatal error. This is because NTS uses algorithms (specifically SIV cipher) that are not approved by NIST and are not compliant with FIPS. This is in direct conflict with STIG requiring FIPS mode: https://www.stigaview.com/products/rhel9/v2r7/RHEL-09-671010/ https://www.stigaview.com/products/rhel10/v1r1/RHEL-10-000500/ and therefore rule `chrony_set_nts` should be removed from STIG profiles. For more details see: * https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/configuring_basic_system_settings/configuring-time-synchronization_configuring-basic-system-settings#assembly_overview-of-network-time-security-in-chrony_configuring-time-synchronization * https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/configuring_time_synchronization/overview-of-network-time-security-nts-in-chrony * https://access.redhat.com/solutions/7053784 Resolves ComplianceAsCode#14563
matusmarhefka
force-pushed
the
chrony_nts_stig
branch
from
61249e9 to
013cbbe
Compare
matusmarhefka
requested review from
a team,
Mab879,
jan-cerny and
vojtapolasek
as code owners
Mab879
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Network Time Security (NTS) is not compatible with systems running in FIPS mode. Enabling NTS on a system in FIPS mode causes chronyd service to abort with a fatal error. This is because NTS uses algorithms (specifically SIV cipher) that are not approved by NIST and are not compliant with FIPS.
This is in direct conflict with STIG requiring FIPS mode: https://www.stigaview.com/products/rhel9/v2r7/RHEL-09-671010/ https://www.stigaview.com/products/rhel10/v1r1/RHEL-10-000500/ and therefore rule
chrony_set_ntsshould be removed from STIG profiles.For more details see:
Resolves #14563