STIGViewer Support

AlmaLinux OS 9 must implement DOD-approved encryption in the bind package.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283456ALMA-09-043140SV-283456r1188512_ruleCCI-002422high
Description
Without cryptographic integrity protections, information can be altered by unauthorized users without detection. Cryptographic mechanisms used for protecting the integrity of information include, for example, signed hash functions using asymmetric cryptography enabling distribution of the public key to verify the hash information while maintaining the confidentiality of the secret key used to generate the hash. AlmaLinux OS 9 incorporates systemwide crypto policies by default. The employed algorithms can be viewed in the /etc/crypto-policies/back-ends/ directory.
STIGDate
Cloud Linux AlmaLinux OS 9 Security Technical Implementation Guide2026-02-27

Related Frameworks

1 mapping across 4 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CRY-01Use of Cryptographic Controls
0.50
CRY-01.3Pre/Post Transmission Handling
0.50
DCH-10Media Use
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (29) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AC-17(1)Monitoring and Control
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-3Access Enforcement
1.00
AU-10(1)Association of Identities
1.00
AU-10(2)Validate Binding of Information Producer Identity
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
IA-2(8)Access to Accounts — Replay Resistant
1.00
IA-2(9)Network Access to Non-privileged Accounts — Replay Resistant
1.00
IA-5(1)Password-based Authentication
1.00

+19 more (top 10 by confidence shown)

CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Details

Check Text (C-283456r1188512_chk)

Note: If the "bind" package is not installed, this requirement is Not Applicable. Verify that BIND uses the system crypto policy with the following command: $ grep include /etc/named.conf include "/etc/crypto-policies/back-ends/bind.config"; If BIND is installed and the BIND config file does not contain the "/etc/crypto-policies/back-ends/bind.config" directive, or the line is commented out, this is a finding.

Fix Text (F-87926r1188511_fix)

Configure BIND to use the systemwide crypto policy. Add the following line to the "options" section in "/etc/named.conf": include "/etc/crypto-policies/back-ends/bind.config";