The Infoblox system must notify the ISSO and ISSM in the event of failed security verification tests.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-233927	SRG-APP-000275-DNS-000040	IDNS-8X-800001	SV-233927r961185_rule	2025-03-11	1

Description
Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes but is not limited to establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. If personnel are not notified of failed security verification tests, they will not be able to take corrective action, and the unsecure condition(s) will remain. Notifications provided by information systems include messages to local computer consoles and/or hardware indications, such as lights. The Infoblox system must be configured to generate audit records whenever a self-test fails.

Description

Security function is defined as the hardware, software, and/or firmware of the information system responsible for enforcing the system security policy and supporting the isolation of code and data on which the protection is based. Security functionality includes but is not limited to establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. If personnel are not notified of failed security verification tests, they will not be able to take corrective action, and the unsecure condition(s) will remain. Notifications provided by information systems include messages to local computer consoles and/or hardware indications, such as lights. The Infoblox system must be configured to generate audit records whenever a self-test fails.

ℹ️ Check
Infoblox systems are capable of providing notifications via remote SYSLOG, SNMP, and SMTP. 1. Navigate to Grid >> Grid Manager >> Grid Properties, or System >> System Manager >> System Properties if using a stand-alone configuration. 2. Select the Monitoring tab. 3. Verify that "Log to External Syslog Servers" is enabled and an External Syslog Server is configured. 4. When complete, click "Cancel" to exit the "Properties" screen. If no external notifications are enabled, this is a finding.

ℹ️ Check

Infoblox systems are capable of providing notifications via remote SYSLOG, SNMP, and SMTP. 1. Navigate to Grid >> Grid Manager >> Grid Properties, or System >> System Manager >> System Properties if using a stand-alone configuration. 2. Select the Monitoring tab. 3. Verify that "Log to External Syslog Servers" is enabled and an External Syslog Server is configured. 4. When complete, click "Cancel" to exit the "Properties" screen. If no external notifications are enabled, this is a finding.

✔️ Fix
1. Navigate to Grid >> Grid Manager >> Grid Properties, or System >> System Manager >> System Properties if using a stand-alone configuration. 2. Select the Monitoring tab. 3. Enable "Log to External Syslog Servers" using the check box. 4. Configure an "External Syslog Server". 5. When complete, click "Save & Close" to save the changes and exit the "Properties" screen. 6. Perform a service restart if necessary. 7. Review the SYSLOG data on the remote SYSLOG server to validate operation.

✔️ Fix

1. Navigate to Grid >> Grid Manager >> Grid Properties, or System >> System Manager >> System Properties if using a stand-alone configuration. 2. Select the Monitoring tab. 3. Enable "Log to External Syslog Servers" using the check box. 4. Configure an "External Syslog Server". 5. When complete, click "Save & Close" to save the changes and exit the "Properties" screen. 6. Perform a service restart if necessary. 7. Review the SYSLOG data on the remote SYSLOG server to validate operation.