The validity period for the RRSIGs covering the DS RR for a zones delegated children must be no less than two days and no more than one week.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
| V-265989 | F5BI-DN-300030 | SV-265989r1024498_rule | CCI-001179 | medium |
| Description | ||||
| The best way for a zone administrator to minimize the impact of a key compromise is by limiting the validity period of RRSIGs in the zone and in the parent zone. This strategy limits the time during which an attacker can take advantage of a compromised key to forge responses. An attacker that has compromised a ZSK can use that key only during the KSK's signature validity interval. An attacker that has compromised a KSK can use that key for only as long as the signature interval of the RRSIG covering the DS RR in the delegating parent. These validity periods must be short, which will require frequent resigning. To prevent the impact of a compromised KSK, a delegating parent must set the signature validity period for RRSIGs covering DS RRs in the range of a few days to one week. This resigning does not require frequent rollover of the parent's ZSK, but scheduled ZSK rollover must still be performed at regular intervals. | ||||
| STIG | Date | |||
| F5 BIG-IP TMOS DNS Security Technical Implementation Guide | 2024-09-09 | |||
Related Frameworks
1 mapping across 3 frameworks
Related Frameworks
SCF0 mappings
No source states a mapping between these directly.
Also reachable in 3 hops (1) 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.
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
- SCF Secure Traceability Relationship Mapping (STRM)2026.2intersects
NIST 800-530 mappings
No source states a mapping between these directly.
Also reachable in 2 hops (1) 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.
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
- DISA CCI List2025-01-23equal to(normalised)
CCI1 mapping
CCI-001179
1.00
- DISA STIG Benchmark (XCCDF)V1R1intersects(normalised)
Details
Check Text (C-265989r1024498_chk)
KSK validity period
From the BIG-IP GUI:
1. DNS.
2. Delivery.
3. Keys.
4. DNSSEC Key List.
5. Click the Name of the KSK.
6. Verify the "Signature Validity Period" is between two and seven days.
ZSK validity period
From the BIG-IP GUI:
1. DNS.
2. Delivery.
3. Keys.
4. DNSSEC Key List.
5. Click the name of the ZSK.
6. Verify the "Signature Validity Period" is between two and seven days.
If the BIG-IP appliance is not configured with a validity period for the RRSIGs covering a zones DNSKEY RRSet of no less than two days and no more than one week, this is a finding.
Fix Text (F-69815r1024497_fix)
KSK validity period
From the BIG-IP GUI:
1. DNS.
2. Delivery.
3. Keys.
4. DNSSEC Key List.
5. Click the Name of the KSK.
6. Configure the "Signature Validity Period" to two and seven days.
7. Click "Update".
ZSK validity period
From the BIG-IP GUI:
1. DNS.
2. Delivery.
3. Keys.
4. DNSSEC Key List.
5. Click the Name of the ZSK.
6. Configure the "Signature Validity Period" to two and seven days.
7. Click "Update".