OpenControls Logo

STIG Viewer

STIGViewer Support

The DNS server must install security-relevant software updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, STIGs).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-278970SRG-APP-000456-DNS-000070SV-278970r1137679_ruleCCI-002605high
Description
Security flaws with software applications are discovered daily. Vendors are constantly updating and patching their products to address newly discovered security vulnerabilities. Organizations (including any contractor to the organization) are required to promptly install security-relevant software updates (e.g., patches, service packs, and hot fixes). Flaws discovered during security assessments, continuous monitoring, incident response activities, or information system error handling must also be addressed expeditiously. Organization-defined time periods for updating security-relevant software may vary based on a variety of factors including, for example, the security category of the information system or the criticality of the update (i.e., severity of the vulnerability related to the discovered flaw). This requirement will apply to software patch management solutions used to install patches across the enclave and also to applications themselves that are not part of that patch management solution. For example, many browsers provide the capability to install their own patch software. Patch criticality, as well as system criticality will vary. Therefore, the tactical situations regarding the patch management process will also vary. This means that the time period used must be a configurable parameter. Time frames for application of security-relevant software updates may be dependent upon the Information Assurance Vulnerability Management (IAVM) process. The application will be configured to check for and install security-relevant software updates within an identified time period from the availability of the update. The specific time period will be defined by an authoritative source (e.g. IAVM, CTOs, DTMs, and STIGs).
STIGDate
Domain Name System (DNS) Security Requirements Guide2025-12-19

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (24) 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.

BCD-05Contingency Plan Root Cause Analysis (RCA) & Lessons Learned
1.00
CPL-03Control Conformity Monitoring
1.00
CPL-03.2Functional Review Of Security, Compliance & Resilience Controls
1.00
GOV-05Measures of Performance
1.00
IAO-02Assessments
1.00
IAO-02.4Security Assessment Report (SAR)
1.00
IAO-05Capabilities Deficiency Tracking
1.00
IRO-13Root Cause Analysis (RCA) & Lessons Learned
1.00
MNT-01Maintenance Operations
1.00
MNT-02Controlled Maintenance
1.00

+14 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (17) 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-2(4)Automated Audit Actions
1.00
AC-6(9)Log Use of Privileged Functions
1.00
AU-10Non-repudiation
1.00
AU-12Audit Record Generation
1.00
AU-14(1)System Start-up
1.00
AU-3Content of Audit Records
1.00
AU-3(1)Additional Audit Information
1.00
AU-4(1)Transfer to Alternate Storage
1.00
AU-5(2)Real-time Alerts
1.00
AU-9Protection of Audit Information
1.00

+7 more (top 10 by confidence shown)

NIST 800-1710 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.

3.14.1
1.00
3.14.2
1.00
3.14.3
1.00
CCI1 mapping
CCI-002605
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (6) 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.

ID.IM-01
1.00
ID.IM-02
1.00
ID.IM-03
1.00
PR.PS-02
1.00
ID.RA-01
0.50
ID.RA-08
0.50

Who does this work

16 NICE work roles and 10 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-278970r1137679_chk)

Verify the DNS server installs security-relevant software updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, STIGs). If the DNS server does not install security-relevant software updates within 30 days unless the time period is directed by an authoritative source, this is a finding.

Fix Text (F-83423r1137678_fix)

Install security-relevant software updates on the DNS server within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, STIGs).