BIND-9X-000001 - A BIND 9.x server implementation must be running in a chroot(ed) directory structure.

CAT|III

CCI|CCI-001090

Rule-ID|SV-207532r879649_rule

STIG-ID|BIND-9X-000001

STIG-Legacy|SV-86987

STIG-Legacy|V-72363

Vuln-ID|V-207532

BIND-9X-001000 - A BIND 9.x server implementation must be operating on a Current-Stable version as defined by ISC.

CAT|I

CCI|CCI-000366

Rule-ID|SV-207533r879887_rule

STIG-ID|BIND-9X-001000

STIG-Legacy|SV-86989

STIG-Legacy|V-72365

Vuln-ID|V-207533

BIND-9X-001002 - The platform on which the name server software is hosted must only run processes and services needed to support the BIND 9.x implementation.

CAT|II

Rule-ID|SV-207534r879887_rule

STIG-ID|BIND-9X-001002

STIG-Legacy|SV-86991

STIG-Legacy|V-72367

Vuln-ID|V-207534

BIND-9X-001003 - The BIND 9.x server software must run with restricted privileges.

Rule-ID|SV-207535r879887_rule

STIG-ID|BIND-9X-001003

STIG-Legacy|SV-86993

STIG-Legacy|V-72369

Vuln-ID|V-207535

BIND-9X-001004 - The host running a BIND 9.X implementation must implement a set of firewall rules that restrict traffic on the DNS interface.

Rule-ID|SV-207536r879887_rule

STIG-ID|BIND-9X-001004

STIG-Legacy|SV-86995

STIG-Legacy|V-72371

Vuln-ID|V-207536

BIND-9X-001005 - The host running a BIND 9.x implementation must use a dedicated management interface in order to separate management traffic from DNS specific traffic.

Rule-ID|SV-207537r879887_rule

STIG-ID|BIND-9X-001005

STIG-Legacy|SV-86997

STIG-Legacy|V-72373

Vuln-ID|V-207537

BIND-9X-001006 - The host running a BIND 9.x implementation must use an interface that is configured to process only DNS traffic.

Rule-ID|SV-207538r879887_rule

STIG-ID|BIND-9X-001006

STIG-Legacy|SV-86999

STIG-Legacy|V-72375

Vuln-ID|V-207538

BIND-9X-001010 - A BIND 9.x server implementation must be configured to allow DNS administrators to audit all DNS server components, based on selectable event criteria, and produce audit records within all DNS server components that contain information for failed security verification tests, information to establish the outcome and source of the events, any information necessary to determine cause of failure, and any information necessary to return to operations with least disruption to mission processes.

CCI|CCI-000133

CCI|CCI-000134

CCI|CCI-000169

CCI|CCI-001294

CCI|CCI-001665

CCI|CCI-001914

Rule-ID|SV-207539r879559_rule

STIG-ID|BIND-9X-001010

STIG-Legacy|SV-87001

STIG-Legacy|V-72377

Vuln-ID|V-207539

BIND-9X-001017 - The BIND 9.x server implementation must not be configured with a channel to send audit records to null.

CCI|CCI-001348

Rule-ID|SV-207540r879582_rule

STIG-ID|BIND-9X-001017

STIG-Legacy|SV-87003

STIG-Legacy|V-72379

Vuln-ID|V-207540

BIND-9X-001020 - The BIND 9.x server logging configuration must be configured to generate audit records for all DoD-defined auditable events to a local file by enabling triggers for all events with a severity of info, notice, warning, error, and critical for all DNS components.

Rule-ID|SV-207541r879559_rule

STIG-ID|BIND-9X-001020

STIG-Legacy|SV-87005

STIG-Legacy|V-72381

Vuln-ID|V-207541

BIND-9X-001021 - In the event of an error when validating the binding of other DNS servers identity to the BIND 9.x information, when anomalies in the operation of the signed zone transfers are discovered, for the success and failure of start and stop of the name server service or daemon, and for the success and failure of all name server events, a BIND 9.x server implementation must generate a log entry.

CCI|CCI-000172

CCI|CCI-001906

CCI|CCI-002702

Rule-ID|SV-207542r879727_rule

STIG-ID|BIND-9X-001021

STIG-Legacy|SV-87007

STIG-Legacy|V-72383

Vuln-ID|V-207542

BIND-9X-001030 - The print-severity variable for the configuration of BIND 9.x server logs must be configured to produce audit records containing information to establish what type of events occurred.

CCI|CCI-000130

Rule-ID|SV-207543r879563_rule

STIG-ID|BIND-9X-001030

STIG-Legacy|SV-87009

STIG-Legacy|V-72385

Vuln-ID|V-207543

BIND-9X-001031 - The print-time variable for the configuration of BIND 9.x server logs must be configured to establish when (date and time) the events occurred.

CCI|CCI-000131

Rule-ID|SV-207544r879564_rule

STIG-ID|BIND-9X-001031

STIG-Legacy|SV-87011

STIG-Legacy|V-72387

Vuln-ID|V-207544

BIND-9X-001032 - The print-category variable for the configuration of BIND 9.x server logs must be configured to record information indicating which process generated the events.

CCI|CCI-000132

Rule-ID|SV-207545r879565_rule

STIG-ID|BIND-9X-001032

STIG-Legacy|SV-87013

STIG-Legacy|V-72389

Vuln-ID|V-207545

BIND-9X-001040 - The BIND 9.x server implementation must be configured with a channel to send audit records to a remote syslog.

Rule-ID|SV-207546r879582_rule

STIG-ID|BIND-9X-001040

STIG-Legacy|SV-87015

STIG-Legacy|V-72391

Vuln-ID|V-207546

BIND-9X-001041 - The BIND 9.x server implementation must be configured with a channel to send audit records to a local file.

Rule-ID|SV-207547r879582_rule

STIG-ID|BIND-9X-001041

STIG-Legacy|SV-87017

STIG-Legacy|V-72393

Vuln-ID|V-207547

BIND-9X-001042 - The BIND 9.x server implementation must maintain at least 3 file versions of the local log file.

Rule-ID|SV-207548r879582_rule

STIG-ID|BIND-9X-001042

STIG-Legacy|SV-87019

STIG-Legacy|V-72395

Vuln-ID|V-207548

BIND-9X-001050 - The BIND 9.x secondary name server must limit the number of zones requested from a single master name server.

CCI|CCI-000054

Rule-ID|SV-207549r879511_rule

STIG-ID|BIND-9X-001050

STIG-Legacy|SV-87021

STIG-Legacy|V-72397

Vuln-ID|V-207549

BIND-9X-001051 - The BIND 9.x secondary name server must limit the total number of zones the name server can request at any one time.

Rule-ID|SV-207550r879511_rule

STIG-ID|BIND-9X-001051

STIG-Legacy|SV-87023

STIG-Legacy|V-72399

Vuln-ID|V-207550

BIND-9X-001052 - The BIND 9.x server implementation must limit the number of concurrent session client connections to the number of allowed dynamic update clients.

Rule-ID|SV-207551r879511_rule

STIG-ID|BIND-9X-001052

STIG-Legacy|SV-87025

STIG-Legacy|V-72401

Vuln-ID|V-207551

BIND-9X-001053 - The BIND 9.x server implementation must be configured to use only approved ports and protocols.

CCI|CCI-000382

Rule-ID|SV-207552r879588_rule

STIG-ID|BIND-9X-001053

STIG-Legacy|SV-87027

STIG-Legacy|V-72403

Vuln-ID|V-207552

BIND-9X-001054 - A BIND 9.x server implementation must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks.

CCI|CCI-001095

Rule-ID|SV-207553r879651_rule

STIG-ID|BIND-9X-001054

STIG-Legacy|SV-87029

STIG-Legacy|V-72405

Vuln-ID|V-207553

BIND-9X-001055 - A BIND 9.x server implementation must prohibit recursion on authoritative name servers.

CCI|CCI-001094

Rule-ID|SV-207554r879650_rule

STIG-ID|BIND-9X-001055

STIG-Legacy|SV-87031

STIG-Legacy|V-72407

Vuln-ID|V-207554

BIND-9X-001057 - The master servers in a BIND 9.x implementation must notify authorized secondary name servers when zone files are updated.

Rule-ID|SV-207555r879887_rule

STIG-ID|BIND-9X-001057

STIG-Legacy|SV-87033

STIG-Legacy|V-72409

Vuln-ID|V-207555

BIND-9X-001058 - The secondary name servers in a BIND 9.x implementation must be configured to initiate zone update notifications to other authoritative zone name servers.

Rule-ID|SV-207556r879887_rule

STIG-ID|BIND-9X-001058

STIG-Legacy|SV-87035

STIG-Legacy|V-72411

Vuln-ID|V-207556

BIND-9X-001059 - On the BIND 9.x server the platform on which the name server software is hosted must be configured to send outgoing DNS messages from a random port.

Rule-ID|SV-207557r879887_rule

STIG-ID|BIND-9X-001059

STIG-Legacy|SV-87043

STIG-Legacy|V-72419

Vuln-ID|V-207557

BIND-9X-001060 - A BIND 9.x caching name server must implement DNSSEC validation to check all DNS queries for invalid input.

CCI|CCI-002754

Rule-ID|SV-207558r879818_rule

STIG-ID|BIND-9X-001060

STIG-Legacy|SV-87045

STIG-Legacy|V-72421

Vuln-ID|V-207558

BIND-9X-001070 - A BIND 9.x master name server must limit the number of concurrent zone transfers between authorized secondary name servers.

Rule-ID|SV-207559r879511_rule

STIG-ID|BIND-9X-001070

STIG-Legacy|SV-87047

STIG-Legacy|V-72423

Vuln-ID|V-207559

BIND-9X-001080 - A BIND 9.x implementation configured as a caching name server must restrict recursive queries to only the IP addresses and IP address ranges of known supported clients.

Rule-ID|SV-207560r879650_rule

STIG-ID|BIND-9X-001080

STIG-Legacy|SV-87049

STIG-Legacy|V-72425

Vuln-ID|V-207560

BIND-9X-001100 - The BIND 9.x server implementation must uniquely identify and authenticate the other DNS server before responding to a server-to-server transaction, zone transfer and/or dynamic update request using cryptographically based bidirectional authentication to protect the integrity of the information in transit.

CCI|CCI-000778

CCI|CCI-001958

CCI|CCI-001967

Detections

Analytics

DISA BIND 9.x STIG v2r3

Warning! Audit Deprecated

Audit Details

File Details

Audit Changelog

Revision 1.2

Miscellaneous

Revision 1.1

Miscellaneous

Detections

Analytics

DISA BIND 9.x STIG v2r3 Download File

Warning! Audit Deprecated

Audit Details

File Details

Audit Changelog

Revision 1.2

Miscellaneous

Revision 1.1

Miscellaneous

DISA BIND 9.x STIG v2r3