V-206612
CAT IIThe DBMS must be able to generate audit records when security objects are accessed.
- Ships Affected
- 1
- Total Findings
- 1
- Open
- 0
- Closed
- 1
Check Text
If the DBMS architecture makes it impossible for any user, even with the highest privileges, to directly view or directly modify the contents of its built-in security objects, and if there are no additional, locally-defined security objects in the database(s), this is not a finding.
Review DBMS documentation to verify that audit records can be produced when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.
If the DBMS is not capable of this, this is a finding.
Review the DBMS/database security and audit configurations to verify that audit records are produced when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.
If they are not produced, this is a finding.
Fix Text
Deploy a DBMS capable of producing the required audit records when security objects, such as tables, views, procedures, and functions, are accessed.
Configure the DBMS to produce audit records when security objects, such as tables, views, procedures, and functions, are accessed, to include reads, creations, modifications and deletions of data, and execution of logic.
STIG Reference
- STIG
- Database Security Requirements Guide
- Version
- 4
- Release
- 5
- Rule ID
- SV-206612r961791_rule
All Occurrences
This vulnerability appears on 1 ship(s)
| Ship | Hull # | Source File | Status | Assigned To | Scan Date | Actions |
|---|---|---|---|---|---|---|
| USNS MONTFORD POINT | T-ESD-1 | Montford Point ShipCLIP DB V4R4.ckl | Unassigned | 2026-03-06T12:50:21.809591 | View in Context |