STIGQter: STIG Summary: Database Security Requirements Guide Version: 3 Release: 1 Benchmark Date: 22 Jan 2021: STIGQter: STIG Summary: Database Security Requirements Guide Version: 3 Release: 1 Benchmark Date: 22 Jan 2021:SV-206575r617447_rule
V-206575
SRG-APP-000251
SRG-APP-000251-DB-000160
CAT II
10
Modify database code to properly validate data before it is put into the database or acted upon by the database.
Modify the database to contain column/field definitions for each column/field in the database.
Modify the database to contain constraints and validity checking on database columns and tables that require them for data integrity.
Review DBMS code (stored procedures, functions, and triggers), application code, settings, column and field definitions, and constraints to determine whether the database is protected against invalid input.
If code exists that allows invalid data to be acted upon or input into the database, this is a finding.
If column/field definitions do not exist in the database, this is a finding.
If columns/fields do not contain constraints and validity checking where required, this is a finding.
Where a column/field is noted in the system documentation as necessarily free-form, even though its name and context suggest that it should be strongly typed and constrained, the absence of these protections is not a finding.
Where a column/field is clearly identified by name, caption or context as Notes, Comments, Description, Text, etc., the absence of these protections is not a finding.
V-206575
False
SRG-APP-000251-DB-000160
Review DBMS code (stored procedures, functions, and triggers), application code, settings, column and field definitions, and constraints to determine whether the database is protected against invalid input.
If code exists that allows invalid data to be acted upon or input into the database, this is a finding.
If column/field definitions do not exist in the database, this is a finding.
If columns/fields do not contain constraints and validity checking where required, this is a finding.
Where a column/field is noted in the system documentation as necessarily free-form, even though its name and context suggest that it should be strongly typed and constrained, the absence of these protections is not a finding.
Where a column/field is clearly identified by name, caption or context as Notes, Comments, Description, Text, etc., the absence of these protections is not a finding.
M
2902