OpenControls Logo

STIG Viewer

STIGViewer Support

When invalid inputs are received, DB2 must behave in a predictable and documented manner that reflects organizational and system objectives.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-213733DB2X-00-009300SV-213733r879818_ruleCCI-002754medium
Description
A common vulnerability is unplanned behavior when invalid inputs are received. This requirement guards against adverse or unintended system behavior caused by invalid inputs, where information system responses to the invalid input may be disruptive or cause the system to fail into an unsafe state. The behavior will be derived from the organizational and system requirements and includes, but is not limited to, notification of the appropriate personnel, creating an audit record, and rejecting invalid input. This calls for the review of applications, which will require collaboration with the application developers. It is recognized that in many cases the database administrator (DBA) is organizationally separate from the application developers, and may have limited, if any, access to source code. Nevertheless, protections of this type are so important to the secure operation of databases that they must not be ignored. At a minimum, the DBA must attempt to obtain assurances from the development organization that this issue is addressed, and must document what has been discovered.
STIGDate
IBM DB2 V10.5 LUW Security Technical Implementation Guide2023-06-11

Related Frameworks

1 mapping across 2 frameworks
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (13) 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.

AU-12Audit Record Generation
1.00
AU-3(1)Additional Audit Information
1.00
CM-5(1)Automated Access Enforcement and Audit Records
1.00
CM-6Configuration Settings
1.00
CM-7Least Functionality
1.00
CM-7(2)Prevent Program Execution
1.00
SC-2Separation of System and User Functionality
1.00
SC-23(3)Unique System-generated Session Identifiers
1.00
SC-5Denial-of-service Protection
1.00
SC-8(2)Pre- and Post-transmission Handling
1.00

+3 more (top 10 by confidence shown)

CCI1 mapping
CCI-002754
1.00

Details

Check Text (C-213733r879818_chk)

Review system documentation to determine how input errors are to be handled in general and if any special handling is defined for specific circumstances. Review the source code for database program objects (stored procedures, functions, triggers) and application source code to identify how the system responds to invalid input. If it does not implement the documented behavior, this is a finding.

Fix Text (F-14952r295249_fix)

Revise and deploy the source code for database program objects (stored procedures, functions, triggers) and application source code, to implement the documented behavior.