STIGQter: STIG Summary: Infoblox 7.x DNS Security Technical Implementation Guide Version: 2 Release: 1 Benchmark Date: 22 Jan 2021:

For zones split between the external and internal sides of a network, the RRs for the external hosts must be separate from the RRs for the internal hosts.

DISA Rule

SV-214208r612370_rule

Vulnerability Number

V-214208

Group Title

SRG-APP-000516-DNS-000091

Rule Version

IDNS-7X-000790

Severity

CAT II

CCI(s)

• CCI-000366 - The organization implements the security configuration settings.

Weight

10

Fix Recommendation

Navigate to Data Management >> DNS >> Zones and review each zone.

Remove any RRs listed in the internal name server configuration (or DNS view) which resolve for external hosts and remove any RRs listed in the external name server configuration which resolve to internal hosts.

For hosts intended to be accessed by both internal and external clients, configure unique IP addresses in each of the internal and external name servers, respective to their location. The perimeter firewall, or other routing device, should handle the Network Address Translation to the true IP address of the destination.

Check Contents

There are two primary configuration options for this requirement.

1. DNS Views allow a single zone to have two different data sets, with the response based on a client match list.

If DNS Views are used and the client match list is validated, this is not a finding.

2. Review the Resource Records (RRs) of each zone which is split between external and internal networks. For those internal hosts which are intended to be accessed by both internal and external users, a different RR should be listed on each of the internal and external name servers, with IP addresses reflective of the external or internal network. Traffic destined for those internal hosts will resolve to the IP address in the external name server and then should be NATd through the perimeter firewall.

If a different Resource Record (RR) is not listed on each of the internal and external name servers, this is a finding.

Vulnerability Number

V-214208

Documentable

False

Rule Version

IDNS-7X-000790

Severity Override Guidance

There are two primary configuration options for this requirement.

1. DNS Views allow a single zone to have two different data sets, with the response based on a client match list.

If DNS Views are used and the client match list is validated, this is not a finding.

2. Review the Resource Records (RRs) of each zone which is split between external and internal networks. For those internal hosts which are intended to be accessed by both internal and external users, a different RR should be listed on each of the internal and external name servers, with IP addresses reflective of the external or internal network. Traffic destined for those internal hosts will resolve to the IP address in the external name server and then should be NATd through the perimeter firewall.

If a different Resource Record (RR) is not listed on each of the internal and external name servers, this is a finding.

Check Content Reference

M

Target Key

3995

Comments